JSON Pointer Extract
Extract up to 100 RFC6901-style JSON pointer paths from one structured value with explicit found/missing results.
1 credit per call · $0.001 USDC with x402
Sample input
{
"value": {
"user": {
"name": "Ada",
"id": 7
}
},
"paths": [
"/user/name",
"/user/id"
]
}Worked sample output
{
"ok": true,
"mode": "json_pointer_extract",
"results": [
{
"path": "/user/name",
"found": true,
"value": "Ada"
},
{
"path": "/user/id",
"found": true,
"value": 7
}
],
"found_count": 2
}Worked example using published sample data only. Own-data execution is paid.
Connect in curl
Set BOUNTY_API_KEY privately after your payment is verified. Change the retry key for each new logical request.
curl 'https://bounty-engineer-x402-prod.onrender.com/v1/prepaid/json-pointer-extract' \
-H "Authorization: Bearer $BOUNTY_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: workflow-request-001' \
-H 'X-Max-Credits: 1' \
--data '{"value":{"user":{"name":"Ada","id":7}},"paths":["/user/name","/user/id"]}'Connect in n8n
Download the inactive n8n template. Import it, configure the private Header Auth credential, inspect the sample and run it manually. A new execution creates a new billable request; there is no automatic schedule.
Use an HTTP POST to https://bounty-engineer-x402-prod.onrender.com/v1/prepaid/json-pointer-extract. Send JSON and these headers; store the Bearer token as a private credential.
{
"method": "POST",
"headers": {
"Authorization": "Bearer YOUR_PRIVATE_API_KEY",
"Content-Type": "application/json",
"Idempotency-Key": "UNIQUE_PER_LOGICAL_REQUEST",
"X-Max-Credits": "1"
},
"body": {
"value": {
"user": {
"name": "Ada",
"id": 7
}
},
"paths": [
"/user/name",
"/user/id"
]
}
}Reuse a retry key only for the same input. Failed execution returns reserved credits. Full integration and recovery guide · Machine-readable recipe