SchemaSure · Authentication Profile

Schemasure Authentication

Authentication

SchemaSure declares 2 security scheme(s) across its OpenAPI definitions.

Structured Data Extractiontext-to-JSONJSON-SchemaDocument ParsingData CleaningLLM ToolingAI Agentsx402-micropaymentsagent-nativeA2AMCP

Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

x402-payment x402

· in: header ()

x402-payment-v1 x402

· in: header ()

Source

Authentication Profile

generated: '2026-09-03'
method: searched
source: https://schemasure.com/llms.txt + well-known/schemasure-x402.json
note: >-
  derive-authentication.py produced no profile because the OpenAPI declares no securitySchemes —
  correctly: SchemaSure has no authentication in the credential sense. There are no accounts, API
  keys, or OAuth. Access control is x402 pay-per-call payment: an unsigned request returns 402
  with a PAYMENT-REQUIRED challenge; the caller signs the terms with an x402 V2-compatible wallet
  (USDC on Base mainnet, eip155:8453) and retries with PAYMENT-SIGNATURE. Identity is the payer
  wallet address. OAuth discovery documents 404 (recorded in well-known/schemasure-well-known.yml).
schemes:
- name: x402-payment
  type: x402
  version: 2
  in: header
  request_header: PAYMENT-SIGNATURE
  challenge_header: PAYMENT-REQUIRED
  receipt_header: PAYMENT-RESPONSE
  network: eip155:8453 (Base mainnet)
  asset: USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)
  applies_to: [/v2/extract, /v2/extract-image]
  note: Charge-only-on-success; failed calls are not settled. Do not hardcode payment terms — validate the live challenge.
- name: x402-payment-v1
  type: x402
  version: 1
  in: header
  request_header: X-PAYMENT
  receipt_header: X-PAYMENT-RESPONSE
  applies_to: [/extract]
  note: Legacy flow after the 3 free evaluation calls per client.
api_keys: none
oauth: none
accounts: none

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact in the catalog.
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 security artifact

curl "https://apis.io/api/v1/security/schemasure-authentication"

All security posture

curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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.

GitHub Google LinkedIn

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