Skip to main content
Send requirements straight to the proof check endpoint. Publish a listing only when you need managed checkout, pricing, or fulfillment. Proof IDs match the SDK (qHash in responses). Base URL: https://api.proofable.me OpenAPI: https://api.proofable.me/openapi.json Public HTTP is versioned on the path as /api/v1. Breaking changes ship as a new path version. Deprecations are announced in the changelog.

Browsers

Send end users through the JavaScript SDK or Hosted Verify. If a web client needs behavior outside those surfaces, your backend should call Proofable so secrets stay off the client and CORS stays predictable.

Endpoints

The SDK’s getGate() / fulfillGate() wrap the gate endpoints above. POST /api/v1/verification and POST /api/v1/verification/access/grant also accept pay per call with x402. Checking an existing proof is free. MCP clients connect with OAuth. Same-origin in the product app: https://proofable.me/api/v1/gates/{gateId} and .../fulfill return the same gate contract for browser calls. Server integrations should call api.proofable.me paths directly (or use the SDK).

Examples

By wallet
Paged responses include proofs, totalCount, hasMore, and continuation fields:
  • nextCursor: preferred for owner vaults and large histories (keyset paging).
  • nextOffset: used when the merged vault is multi-wallet or cursor is unavailable.
Pass cursor (not offset) on the next request when nextCursor is present:
Check inline requirements
The response uses the same data.gate evaluator as persisted checkout. The SDK returns it as top-level result.satisfied, result.missing, and result.proofs. For a published listing, pass its gateId with GET and read data.gate.allRequiredSatisfied and data.gate.reusedVerifierProofs. Full lifecycle: Gate checkout. Create a proof (raw HTTP, advanced) Most products use the SDK or https://proofable.me/verify. Raw HTTP is a fixed two-phase flow:
  1. Build the final JSON body.
  2. POST /api/v1/verification/standardize with that body.
  3. Sign the returned signerString.
  4. POST /api/v1/verification with the same body plus signature.
If step 4 rejects the signature, repeat step 2 on the same payload and compare signerString before retrying step 4. Catalog

Auth

  • Reads: public and unlisted proofs are often open; private proofs require permitted access.
  • Writes: follow Authentication (signature, session, or app-attributed rules).

Next

Start here

Choose an agent, app, or SDK path.

Errors

HTTP error codes.
Last modified on November 11, 2026