SchemaSure
Pay-per-call API that extracts strict, JSON-Schema-valid typed JSON from unstructured text or HTML. Output is guaranteed to validate against the caller-supplied JSON Schema (Ajv, draft 2020-12) or the request returns a typed error and is not charged (charge-only-on-success). The primary production API uses x402 V2 with USDC on Base mainnet; a legacy V1 endpoint provides limited free evaluation calls. No signup, API keys, or account dashboard — built for autonomous AI agents.
AgentCard object — a capabilities object, a declared protocolVersion, and a well-formed skills array.
/.well-known/agent.json, the
pre-0.3 location, rather than the current /.well-known/agent-card.json. Clients written
against A2A 1.0.0 will not find it.
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
Extract to JSON Schema extract_to_schema
Turn any unstructured text or HTML into JSON that is guaranteed to validate against a caller-supplied JSON Schema, or return a typed error with no charge. General-purpose: your schema defines the domain (invoices, receipts, resumes, product pages, logs, etc.) — there is no per-document-type specialization. For best accuracy, add a `description` to ambiguous fields (e.g. "tax rate as a decimal such as 0.0725") and make optional fields nullable so absent values return null instead of a guess. Accepts text/HTML input (inputType text|html|auto); OCR noise, number/date formats, and detail lines are normalized automatically. Benchmarked 100% schema-valid with ~0.99 field F1 and zero hallucinations across a 10-doc-type corpus (11 items, incl. an adversarial prompt-injection tier), p50 latency ~1.5s. Evidence: /.well-known/benchmarks.json. Live operational counters are at /metrics.
x402structured-outputai-agentsstructured-datajsonextractionschemajson-schematext-to-jsondata-cleaningparsingllmagents2026-07-28 from https://schemasure.com/.well-known/agent.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.