# G-Forge Extract JSON Pointer

> G-Forge Extract JSON Pointer is a paid API for AI agents from api.getretold.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-26).

Resolves an RFC 6901 JSON Pointer expression against a supplied JSON document to extract a single precise value from any depth of nesting.

## Facts

- Endpoint: POST https://api.getretold.com/services/agent-auto-launch-pointer/invoke?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/g-forge-extract-json-pointer-83553089
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_r6IkR8VXAB5scgrhc-yhi

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability g-forge-extract-json-pointer-83553089 -d '<json body>'
```

Example prompt: From this API response JSON, extract the value at the pointer /orders/0/shipping/address — just give me that one field.

## When to prefer this

Use this endpoint when you need to extract exactly one value from a known location in a nested JSON document using a precise RFC 6901 pointer expression, especially when you want to avoid writing custom parsing code or when the path includes array indexes or keys requiring RFC 6901 escape handling (~ and /).

## Known failure modes

- Pointer path does not exist in the document — returns a missing-path error
- Invalid RFC 6901 escape sequences in the pointer — returns a parse error
- URI-fragment notation (starting with #) is not accepted — returns an error
- Malformed JSON document supplied — returns a parse or validation error
- Empty pointer string resolves to the root document (valid behavior, not an error)

## How this service works

Get one precise value from a nested API response. Resolve an RFC 6901 JSON Pointer against supplied JSON, including array indexes and escaped keys. Missing paths and invalid escapes return errors. Supports the empty root pointer; URI-fragment notation is not accepted.

## Output

Returns the single value resolved at the specified RFC 6901 JSON Pointer path within the supplied document. The value can be any JSON type (string, number, boolean, object, array, or null). Returns an error if the pointer path is missing, malformed, or uses URI-fragment notation (#).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "value": {
   "type": "object",
   "required": [
    "document",
    "pointer"
   ],
   "properties": {
    "pointer": {
     "type": "string"
    },
    "document": {}
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/g-forge-extract-json-pointer-83553089/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.getretold.com](https://www.zero.xyz/host/api.getretold.com/llms.txt)