Anteproof Chain API

openapi: 3.2.0
info:
  title: Anteproof Chain API
  description: 'Read-only access to the Anteproof forecast archive: live forecasts, question detail, and the full calibration/launch-gate audit trail. Anteproof is a product of Recoilix LLC.'
  version: 0.1.0
tags:
- name: Chain
paths:
  /v1/chain/head:
    get:
      summary: Chain Head
      description: 'The forecast log''s current hash-chain head: what the daily

        Anteproof receipt anchors (packages/anchor). The statement is the same

        one foresight_anchor.head.HEAD_SQL runs — one snapshot, so hash, id,

        count and max issued_at describe the same chain state. The chain

        links by id (see foresight_core.repository.append_forecast), so the

        head is the highest-id row''s hash; backtest rows are links too and

        are counted.'
      operationId: chain_head_v1_chain_head_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties: true
                type: object
                title: Response Chain Head V1 Chain Head Get
      tags:
      - Chain
  /v1/chain/rows:
    get:
      summary: Chain Rows
      description: 'The chain itself, so a receipt''s head can be re-derived with no

        trust in us: every row''s hashed fields (foresight_core.hashchain

        .HASH_FIELDS) plus prev_hash/row_hash as hex, in chain (id) order,

        keyset-paginated. Timestamps are pre-rendered in the exact canonical

        form the hash covers (UTC ISO-8601 from foresight_core.hashchain

        .canonical_json) so a verifier hashes the strings verbatim. Backtest

        rows are included — they are links in the chain and omitting them

        would make it impossible to recompute.'
      operationId: chain_rows_v1_chain_rows_get
      parameters:
      - name: after_id
        in: query
        required: false
        schema:
          type: integer
          minimum: 0
          default: 0
          title: After Id
      - name: limit
        in: query
        required: false
        schema:
          type: integer
          maximum: 1000
          minimum: 1
          default: 1000
          title: Limit
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
                title: Response Chain Rows V1 Chain Rows Get
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Chain
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
  securitySchemes:
    clerkSessionBearer:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: 'A Clerk session token, sent as `Authorization: Bearer <jwt>`. The signature (RS256, against the configured Clerk JWKS) and the expiry are verified; the issuer and the authorized party are also checked where they are configured. An operation marked with this scheme refuses a request that does not carry a valid session token. An Anteproof API key is not accepted in its place.'
    anteproofApiKey:
      type: apiKey
      in: header
      name: X-API-Key
      description: 'An Anteproof API key (`ap_…`), created at https://anteproof.com/account. On the public operations in this document — the ones that list no security requirement — it may be sent either as `X-API-Key: ap_…` or as `Authorization: Bearer ap_…`. It is OPTIONAL on those: a request without it is served just the same, and a request with a live key is counted against the account''s monthly allowance (the reply then carries X-Api-Calls-Used, X-Api-Calls-Limit and X-Api-Calls-Reset). It is not a session credential: an operation marked `clerkSessionBearer` refuses it with 401, live key or not. An `ap_…` key that is invalid or revoked is refused with 401 on any operation in this document; otherwise the key is optional. Because no operation requires one, no operation in this document lists this scheme. The MCP endpoint at /mcp, which this document does not describe, requires a credential — an API key or an OAuth sign-in — for every call except discovery: a POST whose JSON-RPC messages are all `initialize`, `notifications/initialized`, `ping` or `tools/list` is served without one.'
    stripeWebhookSignature:
      type: apiKey
      in: header
      name: Stripe-Signature
      description: 'Stripe''s webhook signature: `t=<unix>,v1=<hex hmac-sha256 of "<t>.<body>">`, checked against this endpoint''s signing secret with a five-minute tolerance on `t`. A request whose signature does not verify is refused with 401. This operation receives Stripe''s callbacks.'