ExchangeRebel Validity Check API

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: Validity Check
paths:
  /toll/validity:
    get:
      tags:
      - Validity Check
      summary: Validity Check service catalog
      responses:
        '200':
          description: 'Success. Returns the service catalog: what a validity check includes, the price ($0.01 per challenge/payload, both ops), the published criteria (payer-preflight/v1, op validity-check) and its published TIGHT thresholds, the pinned test corpus, and the scope statement (deterministic ceiling and window arithmetic on the one artefact you submit; no composite score).'
      security: []
      operationId: getTollValidity
      x-operation-id-source: derived
  /toll/validity/health:
    get:
      tags:
      - Validity Check
      summary: Validity Check service health
      responses:
        '200':
          description: Success. Returns service liveness and the report signer address.
      security: []
      operationId: getTollValidityHealth
      x-operation-id-source: derived
  /toll/validity/criteria:
    get:
      tags:
      - Validity Check
      summary: The published validity criteria and thresholds
      responses:
        '200':
          description: 'Success. Returns the full published criteria (payer-preflight/v1, op validity-check): the upto ceiling rules, the TIGHT window thresholds, and the pinned public test corpus identity; every report is reproducible from them.'
      security: []
      operationId: getTollValidityCriteria
      x-operation-id-source: derived
  /toll/validity/corpus:
    get:
      tags:
      - Validity Check
      summary: The pinned public test corpus identity
      responses:
        '200':
          description: 'Success. Returns the public test corpus identity for validity checks: corpus id validity-corpus/v1 and its SHA-256 pin 84517be97c1376a0bc7767a96e9d55acc6d6e640c0ee3cb9b817205da7706099 (the SHA-256 of the corpus''s canonical serialization, verifiable with the published harness). The corpus is buyer-runnable before paying.'
      security: []
      operationId: getTollValidityCorpus
      x-operation-id-source: derived
  /toll/validity/precheck:
    post:
      tags:
      - Validity Check
      summary: Free headline pre-check of one validity submission
      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 one upto challenge: scheme, network, payTo, asset, max_amount_required (the ceiling), asset_decimals.'
                payload:
                  type: object
                  description: 'The one signed-payload descriptor whose validity window is evaluated: rail plus its validity fields (e.g. valid_before for EVM).'
                evaluation_at_unix:
                  type: integer
                  description: The evaluation instant, unix seconds. The window is evaluated at this instant, never at a hidden clock.
              required:
              - caller
      responses:
        '200':
          description: 'Success. Returns assessability only: whether the submission (challenge for the upto op, payload + evaluation instant for the validity op) is well-formed. No ceiling or window verdict is returned. A malformed submission is refused free. When the caller''s free allowance is exhausted, the response is the /toll/validity payment challenge instead.'
      security: []
      operationId: postTollValidityPrecheck
      x-operation-id-source: derived
  /toll/validity/upto:
    post:
      tags:
      - Validity Check
      summary: Full signed ceiling-exposure statement for one upto challenge
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                challenge:
                  type: object
                  description: 'The one upto challenge: scheme, network, payTo, asset, max_amount_required (the ceiling), asset_decimals.'
              required:
              - challenge
      responses:
        '200':
          description: 'Success. Returns the full signed report: the ceiling-exposure statement for the submitted upto challenge: the maximum signable amount in atomic and human units, the machinery status, and the one-signature status, and an as-of timestamp.'
        '402':
          description: 'Payment Required (x402). A per-item fee: $0.01 per challenge/payload - each submitted artefact is charged at $0.01; the payment includes one ceiling-exposure statement for the one upto challenge you submit — the maximum signable amount exactly as the challenge states it (atomic units, plus the human-unit rendering where the artefact states the asset''s decimals), the scheme machinery the artefact requires, and the one-signature-one-settlement property — each stated as a printed factor sourced from the challenge as submitted, with anything the artefact cannot establish reported as such. 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 challenge/payload) 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: postTollValidityUpto
      x-operation-id-source: derived
  /toll/validity/validity:
    post:
      tags:
      - Validity Check
      summary: Full signed validity-window evaluation of one payload at one stated instant
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                payload:
                  type: object
                  description: 'The one signed-payload descriptor whose validity window is evaluated: rail plus its validity fields (e.g. valid_before for EVM).'
                evaluation_at_unix:
                  type: integer
                  description: The evaluation instant, unix seconds. The window is evaluated at this instant, never at a hidden clock.
              required:
              - payload
              - evaluation_at_unix
      responses:
        '200':
          description: 'Success. Returns the full signed report: the window evaluation for the submitted payload at the stated evaluation instant: remaining seconds, the verdict against the published TIGHT thresholds, and the evaluation instant echoed, and an as-of timestamp.'
        '402':
          description: 'Payment Required (x402). A per-item fee: $0.01 per challenge/payload - each submitted artefact is charged at $0.01; the payment includes one ceiling-exposure statement for the one upto challenge you submit — the maximum signable amount exactly as the challenge states it (atomic units, plus the human-unit rendering where the artefact states the asset''s decimals), the scheme machinery the artefact requires, and the one-signature-one-settlement property — each stated as a printed factor sourced from the challenge as submitted, with anything the artefact cannot establish reported as such. 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 challenge/payload) 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: postTollValidityValidity
      x-operation-id-source: derived
  /toll/validity/metrics:
    get:
      tags:
      - Validity Check
      summary: Validity Check aggregate counters
      responses:
        '200':
          description: Success. Returns aggregate counters (paid calls, distinct payers, free pre-checks today). Aggregate only - no payer identities, no submitted artefacts.
      security: []
      operationId: getTollValidityMetrics
      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.'