[Staging] 17711 Extract Correct
JSON repair: extracts structured JSON from messy text or LLM output, optionally validating and auto-correcting it against a JSON Schema
The wallet the 402 directs payment to. Its full payment record is on the merchant page.
Asset 0x036CbD53842c5426634e7929541eC2318f3dCF7e
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service; most of the catalog is unregistered.
Recent payments · which agents last used it
Every indexed settlement paid to this service’s wallet, newest first. The index does not record which endpoint a payment was for, so if this wallet serves more than one endpoint, the rows include payments for the others. Paged up to the newest 5,000; the full history is on the merchant page.
| Payer Payee | Chain | Amount | x402 | Route | Age | Txn hash |
|---|---|---|---|---|---|---|
| 0x3416…6592[Staging] 17711 Extract Correct | Base Sepolia | $0.001 | 100% | payAI | 39d ago | 0x5f4307…9af582 |
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying: a price here is a claim, not a quote.
Pay 0.001 USDC on Base Sepolia to 0x6a4b…6c23b. The signed payment is good for 2 minutes.
- Paid to
- 0x6a4b…6c23b
- USD Coin (Base Sepolia) contract
- 0x036C…dCF7e
- Payment window
- 2 minutes
- As published
- 1000 smallest units
The catalog’s raw entry
[
{
"asset": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
"extra": {
"name": "USDC",
"version": "2",
"assetTransferMethod": "eip3009"
},
"payTo": "0x6a4b77de6f65808e2095ec0191d110fd1ad6c23b",
"amount": "1000",
"scheme": "exact",
"network": "eip155:84532",
"maxTimeoutSeconds": 120
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"text": "string",
"schema": null
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"data": null,
"valid": false,
"applied_fixes": [
{
"path": "string",
"rule": "string",
"detail": "string"
}
],
"remaining_issues": [
{
"path": "string",
"keyword": "string",
"message": "string"
}
],
"extraction_method": "string"
}
}
},
"schema": {
"type": "object",
"$defs": {
"AppliedFix": {
"type": "object",
"required": [
"path",
"rule",
"detail"
],
"properties": {
"path": {
"type": "string",
"description": "JSON Pointer to the field that was corrected (e.g. `/user/age`; `\"\"` = the whole value)."
},
"rule": {
"type": "string",
"description": "Which bounded correction rule fired (e.g. `type_coercion`, `additional_property_stripped`,\n`enum_case_insensitive_match`, `required_default_filled`, `clamped_to_minimum`,\n`clamped_to_maximum`, `array_truncated_to_max_items`)."
},
"detail": {
"type": "string",
"description": "Human-readable detail of what changed."
}
},
"description": "One deterministic correction actually applied to the extracted value."
},
"RemainingIssue": {
"type": "object",
"required": [
"path",
"keyword",
"message"
],
"properties": {
"path": {
"type": "string",
"description": "JSON Pointer to the field that still fails validation."
},
"keyword": {
"type": "string",
"description": "The JSON Schema keyword that failed (e.g. `pattern`, `format`, `minItems`, `oneOf`)."
},
"message": {
"type": "string",
"description": "The underlying validator's own error message."
}
},
"description": "One schema violation that could NOT be corrected -- never silently dropped or guessed."
}
},
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"title": "ParseJsonRequest",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"description": "Free-form or messy text to extract structured JSON from -- already-valid JSON, JSON\nwrapped in prose or a markdown code fence, or malformed JSON (trailing commas,\nsingle-quoted strings, unquoted keys, a truncated array/object)."
},
"schema": {
"default": null,
"description": "Optional JSON Schema to validate the extracted value against and auto-correct where a\nbounded, deterministic fix rule applies. Omitted = extraction only, no validation."
}
}
},
"type": {
"const": "http"
},
"method": {
"const": "POST"
},
"bodyType": {
"const": "json"
}
}
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"const": "json"
},
"example": {
"type": "object",
"title": "ParseJsonResponse",
"required": [
"data",
"extraction_method",
"applied_fixes",
"remaining_issues"
],
"properties": {
"data": {
"description": "The extracted (and, if a schema was supplied, corrected) JSON value."
},
"valid": {
"type": [
"boolean",
"null"
],
"description": "Whether `data` satisfies `schema` after correction. `None` when no `schema` was supplied\n-- never conflated with \"assumed valid\"."
},
"applied_fixes": {
"type": "array",
"items": {
"$ref": "#/$defs/AppliedFix"
},
"description": "Every correction actually applied, in the order applied."
},
"remaining_issues": {
"type": "array",
"items": {
"$ref": "#/$defs/RemainingIssue"
},
"description": "Every schema violation that remains after correction -- non-empty only when `schema` was\nsupplied and at least one issue couldn't be fixed by a bounded v1 rule."
},
"extraction_method": {
"type": "string",
"description": "How `data` was obtained: `\"direct\"` (already valid JSON), `\"repaired\"` (malformed JSON\nfixed in place), or `\"extracted_and_repaired\"` (isolated from surrounding text, then\nfixed)."
}
}
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-10-08 22:20Z
- Last indexed by Roundhouse
- 2026-10-10 20:16Z
- Last enriched (probe, favicon, geo)
- –
- x402 version
- 2
- Max timeout
- 120s
- Liveness probe
- Not probed
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent: it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
Nothing indexed for this service or its provider yet. Not a claim that it is unused — only that we hold no record. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service [Staging] 17711 Extract Correct and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=%5BStaging%5D%2017711%20Extract%20Correct' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://staging.api.17711.xyz/registry/extract-correct-service/v1/extract-correct/parse_json, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://preview.roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://preview.roundhouseai.io/skill.md first — it is the whole procedure.