Give an MCP-enabled agent a public URL and receive concise Schema.org JSON-LD or field-level Product evidence. Start with a free preflight, choose the result you need, and pay only for a successful paid response.
Use JSON Recon when an agent needs structured page data, predictable fields, or Product evidence without repeating page-reading work in every downstream step.
Receive the primary structured entity and useful response metadata instead of passing raw page content through every later step.
Full, Lite, and Verified Product advertise reusable JSON Schemas through MCP, OpenAPI, and x402 discovery so agents can validate and route results consistently.
Verified Product reports field-level support, conflicts, coverage, observation time, and a content hash. Its verdict describes consistency within the requested page, not an independent guarantee about the seller or item.
Use a prepaid API key or an x402 wallet. Prices are fixed by result type, preflight is free, and failed paid requests are not charged.
The service is designed for tasks where a compact entity or explicit Product evidence is more useful than a large page payload.
Actual context and latency savings depend on the page, client, and workflow. JSON Recon returns concise JSON so agents can avoid carrying unnecessary page content forward.
Public pages vary in accessibility and data quality. JSON Recon returns an explicit success or failure and charges only successful paid responses.
Submit a public URL and the requested result type. No page-specific configuration is required.
Check whether a URL is a reasonable candidate before authorizing a paid request.
Paid successes include a primary type, confidence, timing, and other result-specific quality signals.
Per-success billing: Preflight is free. Failed paid requests do not consume prepaid balance, and x402 authorization settles only for a successful paid response.
Start with the free check. Then choose Lite for published markup, Full for a useful page-level entity, or Verified Product for field-level Product evidence.
Quick choice: need exactly what the page publishes? Choose Lite. Need a useful primary entity? Choose Full. Need field-level Product evidence and conflicts? Choose Verified Product.
extract_schemaChoose Full for a concise page-level Schema.org entity at $0.01 or Lite for Schema.org JSON-LD published by the page at $0.005. Lite marks navigation-only or container-only results as low information.
verify_productChecks Product fields against multiple representations on the requested page. Returns field-level evidence, contradictions, observation time, a content hash, and a verified, conflicted, or insufficient_evidence verdict. Non-product pages do not consume balance.
check_extractabilityA free check that tells an agent whether a public URL is a reasonable extraction candidate before spending. It returns a concise difficulty and confidence assessment without requiring credentials.
Published Schema.org data, with low-information signaling.
A concise page-level Schema.org entity.
Field-level corroboration and contradiction evidence.
Each paid success follows a published result contract. Agents can validate required fields, inspect quality signals, and handle each result type without guessing its shape.
Full and Lite return JSON-LD with a primary schema_type.
Responses expose confidence and provenance metadata. Lite also identifies a result that contains only navigation or container markup.
Verified Product returns verified, conflicted, or insufficient_evidence with field-level support and contradictions.
The same contracts are advertised through MCP, OpenAPI, and x402 discovery to reduce integration drift.
Paid successes provide the structured entity plus the metadata defined for that result type. Values vary with the requested public page.
Expect success, data, schema_type, confidence, cached, and extraction_ms, with additional public metadata when available.
Expect a Product entity, verdict, observed time, content hash, field evidence, contradictions, coverage counts, and an estimate of context avoided.
Route the entity to the part of your workflow that handles its declared schema_type.
Stop, retry, or request review when confidence is low, Lite reports low information, or Product evidence conflicts.
Retain the public confidence, source, observation time, and content hash fields required by your application.
Free preflight: install the MCP server with no credentials and use check_extractability before paying. Paid tools explain which credential is missing.
Prepaid API key: generate a key in the developer dashboard, add balance, and set JSONRECON_API_KEY.
x402 wallet: use a dedicated low-balance wallet funded with USDC on Base mainnet. No JSON Recon account is required.
Add the configuration to Claude Desktop, Cursor, or another MCP client, then restart that client. Keep API keys and wallet keys only in its environment configuration. When both payment options are present, prepaid API-key billing is used by default.
Create a prepaid API key →{
"mcpServers": {
"jsonrecon": {
"command": "npx",
"args": ["-y", "@jsonrecon/mcp-server"],
"env": {
"JSONRECON_API_KEY": "jr_liv_xxxxx"
}
}
}
}{
"mcpServers": {
"jsonrecon": {
"command": "npx",
"args": ["-y", "@jsonrecon/mcp-server"],
"env": {
"JSONRECON_PAYMENT_MODE": "x402",
"JSONRECON_EVM_PRIVATE_KEY": "0x_your_private_key",
"JSONRECON_X402_SESSION_LIMIT_USDC": "1.00"
}
}
}
}The MCP server exposes all three tools immediately. A practical agent flow is short and explicit.
Call check_extractability with the public URL.
Select Lite, Full, or Verified Product based on the decision the agent needs to make.
Use prepaid balance or the configured x402 wallet for the published price.
Validate the result and pass only the fields needed by the next workflow step.
“Check whether this URL is a good JSON Recon candidate before spending anything.”
“Use Lite to retrieve the Schema.org JSON-LD published on this page and flag a low-information result.”
“Use Full to return the primary page-level Schema.org entity, then summarize only the fields relevant to my task.”
“Verify this product page and stop if the price, availability, or identity fields conflict.”
Preflight is free. Lite is $0.005, Full is $0.01, and Verified Product is $0.02. Failed paid requests and non-product Verified requests do not consume balance.
Never paste an API key or private key into a prompt, support message, repository, or website form. Use your MCP client's environment configuration.
Use a dedicated low-balance wallet and set JSONRECON_X402_SESSION_LIMIT_USDC to the maximum authorization total appropriate for the task.
Login-only content, private networks, and pages that deny automated access may fail. Use preflight first when access is uncertain.
Verified Product reports consistency among representations on one page at one observation time. It is not seller authentication, inventory confirmation, or an independent product guarantee.
401: check the API key. 402: fund or authorize payment. 422: revise the URL or requested result. 429: wait and retry.
Important: JSON Recon helps agents obtain and evaluate Schema.org data. Search engines and other consumers apply their own eligibility, quality, and ranking policies; a structured result is not a ranking or rich-result guarantee.