ExchangeRebel Receipt API

The Receipt API from ExchangeRebel — 7 operation(s) for receipt.

GitHub OpenAPI

Operations 7

GET /toll/receipt Receipt Verification service catalog #
GET /toll/receipt/health Receipt Verification service health #
GET /toll/receipt/criteria The published receipt verification criteria #
GET /toll/receipt/corpus The pinned public test corpus identity #
POST /toll/receipt/precheck Free headline pre-check of one captured challenge + receipt header pair #
POST /toll/receipt/verify Full signed receipt verification for one paid call #
GET /toll/receipt/metrics Receipt Verification aggregate counters #

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API
curl "https://apis.io/api/v1/apis/exchangerebel-com:exchangerebel-com-receipt-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

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.

OpenAPI Specification

exchangerebel-com-receipt-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: ExchangeRebel — pay-per-call APIs for AI agents (x402 on…
  version: 1.0.0
  contact:
    name: 'ExchangeRebel (operator: Rebel Data)'
    url: https://exchangerebel.com
    email: sound.money.investing@gmail.com
  x-guidance: 'All paid operations use x402 on Solana: call without payment to get a 402 challenge (SOL recipient + USDC token account + fresh memo), pay with the memo attached via the Solana Memo program, then retry with header X-Payment-Tx: <signature> and ?toll_memo=<memo>. Challenges are dual-version: the PAYMENT-REQUIRED header carries the x402 v2 PaymentRequired object and the response body carries the same challenge in x402 v1 form for compatibility. Free operations (security: []) include each service''s /health catalog with full response shapes. Prices in x-payment-info are USD per call unless the summary says otherwise (RPC is per 1,000-request block; Telegram provisioning is per bot-month; transcription is per minute of audio).'
  description: '67 data and utility APIs behind x402 tolls, settled in SOL or USDC on Solana. Call a paid endpoint without payment to receive a 402 x402 challenge (recipient + fresh memo), pay with the memo attached via the Solana Memo program, then retry with the X-Payment-Tx header and toll_memo query parameter. Free catalog/health endpoints are marked without x-payment-info. Full catalogs: GET /toll/discovery and each service''s /health.'
servers:
- url: https://exchangerebel.com
tags:
- name: Receipt
paths:
  /toll/receipt:
    get:
      tags:
      - Receipt
      summary: Receipt Verification service catalog
      responses:
        '200':
          description: 'Success. Returns the service catalog: what a receipt verification includes, the price ($0.01 per receipt), the published criteria (settlement-evidence/v1, receipt form), the pinned test corpus, and the scope statement (one captured 402 challenge plus the PAYMENT-RESPONSE header from its paid call, matched field by field and checked against the chain; the header''s unsigned status is stated plainly and never upgraded into an attestation).'
      security: []
      operationId: getTollReceipt
      x-operation-id-source: derived
  /toll/receipt/health:
    get:
      tags:
      - Receipt
      summary: Receipt Verification service health
      responses:
        '200':
          description: Success. Returns service liveness and the report signer address.
      security: []
      operationId: getTollReceiptHealth
      x-operation-id-source: derived
  /toll/receipt/criteria:
    get:
      tags:
      - Receipt
      summary: The published receipt verification criteria
      responses:
        '200':
          description: 'Success. Returns the full published criteria (settlement-evidence/v1, receipt form): the input contract (one captured challenge plus its PAYMENT-RESPONSE header), the graded fields, the verdict states, and the pinned public test corpus identity; every report is reproducible from them.'
      security: []
      operationId: getTollReceiptCriteria
      x-operation-id-source: derived
  /toll/receipt/corpus:
    get:
      tags:
      - Receipt
      summary: The pinned public test corpus identity
      responses:
        '200':
          description: 'Success. Returns the public test corpus identity for receipt verification: corpus id receipt-evidence-corpus/v1 and its SHA-256 pin bbc0e3bf73fe0b4001b3c16837df494cb2f76322082686d888b8418c550b2ead (the SHA-256 of the corpus''s canonical serialization, verifiable with the published harness). The corpus is buyer-runnable before paying.'
      security: []
      operationId: getTollReceiptCorpus
      x-operation-id-source: derived
  /toll/receipt/precheck:
    post:
      tags:
      - Receipt
      summary: Free headline pre-check of one captured challenge + receipt header pair
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                caller:
                  type: string
                  description: Solana base58 wallet of the operator; keys the free allowance (100/day per wallet).
                challenge:
                  type: object
                  description: The captured 402 challenge object exactly as issued by the endpoint that was paid. Processed in memory only, never stored.
                paymentResponse:
                  type: string
                  description: The PAYMENT-RESPONSE header value from the paid call (base64 JSON string; a raw JSON string or the decoded object are also accepted). Processed in memory only, never stored.
              required:
              - caller
              - challenge
              - paymentResponse
      responses:
        '200':
          description: 'Success. Returns assessability only: whether the challenge + header pair is well-formed for grading. No field is matched, no chain read is performed, and no verdict is returned. When the caller''s free allowance is exhausted, the response is the /toll/receipt/verify payment challenge instead.'
      security: []
      operationId: postTollReceiptPrecheck
      x-operation-id-source: derived
  /toll/receipt/verify:
    post:
      tags:
      - Receipt
      summary: Full signed receipt verification for one paid call
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                challenge:
                  type: object
                  description: The captured 402 challenge object exactly as issued by the endpoint that was paid. Processed in memory only, never stored.
                paymentResponse:
                  type: string
                  description: The PAYMENT-RESPONSE header value from the paid call (base64 JSON string; a raw JSON string or the decoded object are also accepted). Processed in memory only, never stored.
              required:
              - challenge
              - paymentResponse
      responses:
        '200':
          description: 'Success. Returns the full signed report: the decoded header fields, the per-field match report against the challenge, the chain verdict from the settlement-evidence/v1 engine for the header''s transaction, the header''s unsigned status stated plainly, and an as-of timestamp.'
        '402':
          description: 'Payment Required (x402). A per-item fee: $0.01 per receipt - each challenge + PAYMENT-RESPONSE header pair you submit is charged at $0.01; the payment includes one receipt verification — one captured 402 challenge plus the PAYMENT-RESPONSE header from the paid call — returned as the decoded header fields, a per-field match report against the challenge (recipient, asset, amount, network, payer, success, and memo when the challenge carries one), the chain verdict from the settlement-evidence/v1 engine for the header''s transaction, the header''s unsigned status stated plainly, and an as-of timestamp. Factors are printed per field; there is NO composite score. The service reports what the header IS — it never upgrades the unsigned header into an attestation; the chain, not the header, is ground truth for settlement. Nothing about the submitted receipt is stored beyond the payments ledger''s closed field list. The response body carries the payment instructions in x402 v1 form: payTo (the operator''s Solana wallet), the amount (10000 USDC units = $0.01 per receipt) and a fresh memo. Pay in USDC on Solana with the memo attached via the Solana Memo program, then resubmit the same request with the payment transaction in the X-Payment-Tx header and ?toll_memo=<memo>, re-sending the request body. The PAYMENT-REQUIRED response header carries the same object in x402 v2 form.'
      x-payment-info:
        protocols:
        - x402
        price:
          mode: fixed
          currency: USD
          amount: '0.01'
      security:
      - x402Payment: []
      operationId: postTollReceiptVerify
      x-operation-id-source: derived
  /toll/receipt/metrics:
    get:
      tags:
      - Receipt
      summary: Receipt Verification aggregate counters
      responses:
        '200':
          description: Success. Returns aggregate counters (paid receipts, distinct payers, free pre-checks today). Aggregate only - no payer identities, no submitted receipt content.
      security: []
      operationId: getTollReceiptMetrics
      x-operation-id-source: derived
components:
  securitySchemes:
    x402Payment:
      type: apiKey
      in: header
      name: X-Payment-Tx
      description: 'x402 toll payment proof: the Solana transaction signature of a payment carrying the memo from the 402 challenge; send together with ?toll_memo=<memo>. Payment itself is made on-chain in SOL or USDC to the recipient named in the challenge.'