SchemaSure website screenshot

SchemaSure

Structured data extraction API that converts unstructured text or HTML into JSON guaranteed to validate against a caller-supplied JSON Schema, or returns a typed error at no charge. Access is gated by x402 pay-per-call micropayments (USDC on Base), with no accounts or API keys.

SchemaSure publishes 4 API contracts indexed on the APIs.io network, including Health API, Image extraction · x402 V2 API, Legacy V1 evaluation API, and 1 more. Tagged areas include Structured Data Extraction, text-to-JSON, JSON Schema, Document Parsing, and Data Cleaning.

The SchemaSure catalog on APIs.io includes 1 Spectral governance ruleset.

SchemaSure’s developer surface includes authentication, sandbox, pricing, support, and 20 more developer resources.

45.9/100 developing ▬ flat Agent 41/100 agent ready Front door AI 4/6 moderate Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →
AccessPaidOpen
1 published contract 1 MCP Servers 2 Agent Skills
Structured Data Extractiontext-to-JSONJSON SchemaDocument ParsingData CleaningLLM ToolingAI Agentsx402-micropaymentsAgent-NativeA2AMCP

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site. Kin Score badge preview for SchemaSure It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/schemasure/"><img src="https://apis.io/badge/schemasure/card.svg" alt="SchemaSure on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
  • Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
  • Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
  • Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
  • Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
  • Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
  • Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
5 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/schemasure/apis.yml: open an issue on github.com/api-evangelist/schemasure to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

MarketPositionDepthRegistered MCP serverDeclares compatibility
RPA and Document AI (RPA marketplaces, intelligent document processing) standard 40.9 (thin) - -
x402 Micropayments & Agentic Pay-per-Call standard 40.9 (thin) - -

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 4

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

measured — observed by APIs.io (conformant)
tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified
measured — observed by APIs.io (documented)
measured — observed by APIs.io (published)

APIs 4

Individual APIs this provider publishes, each with its own machine-readable definition.

SchemaSure Health API

The Health API from SchemaSure — 1 operation(s) for health.

SchemaSure Image extraction · x402 V2 API

The Image extraction · x402 V2 API from SchemaSure — 1 operation(s) for image extraction · x402 v2.

SchemaSure Legacy V1 evaluation API

The Legacy V1 evaluation API API from SchemaSure — 1 operation(s) for legacy v1 evaluation api.

SchemaSure Primary x402 V2 API

The Primary x402 V2 API API from SchemaSure — 1 operation(s) for primary x402 v2 api.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

SchemaSure MCP Server

First-party MCP client, local-stdio only (npx -y @noamjose/schemasure); no hosted endpoint — /mcp probed 404 on 2026-09-03.

MCP SERVER

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

SchemaSure API pricing

Prices published by SchemaSure, read 2026-10-28 from schemasure.com/.well-known/pricing.json.

PlanPrice
text-extraction $0.02/call, flat, failed calls free per successful extraction
Includes: freeCalls: 0
image-extraction $0.06/image, flat, failed calls free per image (base64 PNG/JPEG/WebP)
Includes: freeCalls: 0

Plan details, limits and sources →

Billed by: successful extraction · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Schemasure Rate Limits

0 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

FinOps 1

Cost, billing, and metering signals for API financial operations.

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

SchemaSure API Rules

44 rules · 41 errors 2 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Schemasure Openapi Overlay

5 actions · update · schemasure-openapi.json

DERIVED

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Schemasure Authentication

2 schemes

SECURITY

Schemasure Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Schemasure Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 5

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 1

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
name: SchemaSure
description: Structured data extraction API that converts unstructured text or HTML into JSON guaranteed to validate against
  a caller-supplied JSON Schema, or returns a typed error at no charge. Access is gated by x402 pay-per-call micropayments
  (USDC on Base), with no accounts or API keys.
url: https://schemasure.com/apis.json
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: open
  trial: false
  try_now: false
  public: true
  gated: none
  gated_source:
  - onboarding
  label: Paid · Open access
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
created: '2026-07-19'
modified: '2026-09-03'
specificationVersion: '0.23'
tags:
- Structured Data Extraction
- text-to-JSON
- JSON Schema
- Document Parsing
- Data Cleaning
- LLM Tooling
- AI Agents
- x402-micropayments
- Agent-Native
- A2A
- MCP
tags_raw:
- structured-data-extraction
- text-to-JSON
- JSON-Schema
- document-parsing
- data-cleaning
- LLM-tooling
- AI-agents
- x402-micropayments
- agent-native
- A2A
- MCP
apis:
- aid: schemasure:schemasure-health-api
  name: SchemaSure Health API
  description: The Health API from SchemaSure — 1 operation(s) for health.
  humanURL: https://schemasure.com
  tags:
  - Health
  properties:
  - type: OpenAPI
    url: openapi/schemasure-health-api-openapi.yml
  - type: LLMsTxt
    url: llms/schemasure-llms.txt
  - type: Documentation
    url: https://schemasure.com/llms.txt
  - type: ErrorCatalog
    url: errors/schemasure-problem-types.yml
  - type: ToolCrosswalk
    url: mcp/schemasure-tool-crosswalk.yml
- aid: schemasure:schemasure-image-extraction-x402-v2-api
  name: SchemaSure Image extraction · x402 V2 API
  description: The Image extraction · x402 V2 API from SchemaSure — 1 operation(s) for image extraction · x402 v2.
  humanURL: https://schemasure.com
  tags:
  - Image extraction · x402 V2
  properties:
  - type: OpenAPI
    url: openapi/schemasure-image-extraction-x402-v2-api-openapi.yml
  - type: LLMsTxt
    url: llms/schemasure-llms.txt
  - type: Documentation
    url: https://schemasure.com/llms.txt
  - type: ErrorCatalog
    url: errors/schemasure-problem-types.yml
  - type: ToolCrosswalk
    url: mcp/schemasure-tool-crosswalk.yml
- aid: schemasure:schemasure-legacy-v1-evaluation-api-api
  name: SchemaSure Legacy V1 evaluation API
  description: The Legacy V1 evaluation API API from SchemaSure — 1 operation(s) for legacy v1 evaluation api.
  humanURL: https://schemasure.com
  tags:
  - Legacy V1 evaluation API
  properties:
  - type: OpenAPI
    url: openapi/schemasure-legacy-v1-evaluation-api-api-openapi.yml
  - type: LLMsTxt
    url: llms/schemasure-llms.txt
  - type: Documentation
    url: https://schemasure.com/llms.txt
  - type: ErrorCatalog
    url: errors/schemasure-problem-types.yml
  - type: ToolCrosswalk
    url: mcp/schemasure-tool-crosswalk.yml
- aid: schemasure:schemasure-primary-x402-v2-api-api
  name: SchemaSure Primary x402 V2 API
  description: The Primary x402 V2 API API from SchemaSure — 1 operation(s) for primary x402 v2 api.
  humanURL: https://schemasure.com
  tags:
  - Primary x402 V2 API
  properties:
  - type: OpenAPI
    url: openapi/schemasure-primary-x402-v2-api-api-openapi.yml
  - type: LLMsTxt
    url: llms/schemasure-llms.txt
  - type: Documentation
    url: https://schemasure.com/llms.txt
  - type: ErrorCatalog
    url: errors/schemasure-problem-types.yml
  - type: ToolCrosswalk
    url: mcp/schemasure-tool-crosswalk.yml
maintainers:
- FN: SchemaSure Support
  url: https://schemasure.com
  email: support@schemasure.com
generated:
  by: apis.io/add
  model: claude-opus-4-8
  confidence: 95
  at: '2026-07-19T22:23:17.395Z'
common:
- type: Overlay
  url: overlays/schemasure-openapi-overlay.yaml
- type: Website
  url: https://schemasure.com
- type: VulnerabilityDisclosure
  url: security/schemasure-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/schemasure-domain-security.yml
- type: WellKnown
  url: well-known/schemasure-well-known.yml
- type: SecurityTxt
  url: well-known/schemasure-security.txt
- type: Security
  url: security/schemasure-vulnerability-disclosure.yml
- type: Packages
  url: packages/schemasure-packages.yml
- type: SDKs
  url: packages/schemasure-packages.yml
- type: MCPServer
  url: mcp/schemasure-mcp.yml
  description: First-party MCP client, local-stdio only (npx -y @noamjose/schemasure); no hosted endpoint — /mcp probed 404
    on 2026-09-03.
- type: Conformance
  url: conformance/schemasure-conformance.yml
- type: Lifecycle
  url: lifecycle/schemasure-lifecycle.yml
- type: Authentication
  url: authentication/schemasure-authentication.yml
- type: Sandbox
  url: sandbox/schemasure-sandbox.yml
- type: Conventions
  url: conventions/schemasure-conventions.yml
- type: DataModel
  url: data-model/schemasure-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Plans
  url: plans/schemasure-plans-pricing.yml
- type: RateLimits
  url: rate-limits/schemasure-rate-limits.yml
- type: APIsJson
  url: https://schemasure.com/apis.json
  description: Provider-published APIs.json 0.18 portfolio discovery index (also saved at well-known/schemasure-apis-json.json).
- type: Pricing
  url: https://schemasure.com/.well-known/pricing.json
- type: TermsOfService
  url: https://schemasure.com/terms
- type: PrivacyPolicy
  url: https://schemasure.com/privacy
- type: Support
  url: mailto:support@schemasure.com
image: https://schemasure.com/icon.svg
x-enrichment:
  date: '2026-09-03'
  status: enriched
  artifacts_added: 30
  pass: local-v2

SchemaSure API — frequently asked questions

Does SchemaSure have an API?

Yes. APIs.io lists 4 APIs from SchemaSure, including SchemaSure Health API, SchemaSure Image extraction · x402 V2 API and SchemaSure Legacy V1 evaluation API, and 1 more.

Is there an OpenAPI specification for the SchemaSure API?

Yes. APIs.io indexes 4 OpenAPI specifications for SchemaSure, each linked for download from this page.

How do I authenticate with the SchemaSure API?

SchemaSure uses bearer-token authentication (2 schemes). The details are profiled on APIs.io as Schemasure Authentication.

How much does the SchemaSure API cost?

SchemaSure publishes its prices; its text-extraction plan is $0.02/call, flat, failed calls free per successful extraction as of 2026-10-28. APIs.io lists 2 pricing plans for SchemaSure, with each plan's price, limits and inclusions under Pricing on this page.

Does SchemaSure have an MCP server?

Yes. APIs.io lists 1 MCP server for SchemaSure: First-party MCP client, local-stdio only (npx -y @noamjose/schemasure); no hosted endpoint — /mcp probed 404 on 2026-09-03.

Is the SchemaSure API ready for AI agents?

SchemaSure has a Kin Score of 45.9 out of 100 (developing) and an Agent Readiness score of 41.4 (agent-ready), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/schemasure"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/schemasure/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/schemasure/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.