> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rail402.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Rail402 is an x402 payment facilitator, Stellar-native Bazaar discovery layer, and agent tooling for the Stellar network. It currently targets stellar:testnet.
> The live testnet facilitator is https://facilitator.rail402.dev with endpoints /verify, /settle, /supported, /health, and /discovery/*.
> Payment amounts use 7-decimal SEP-41 integer (stroop) arithmetic. Never use floating-point math for amounts.
> Every rejection returns a machine-readable error code and a non-null human-readable reason. When explaining a failure, surface both.

# Headline numbers



## OpenAPI

````yaml /api-reference/explorer.openapi.yaml get /stats
openapi: 3.1.0
info:
  title: Rail402 Explorer API
  version: 0.1.0
  summary: x402 payments explorer for Stellar
  description: >
    Read-only public API over x402 payment activity observed on Stellar. The
    explorer watches the

    ledger directly (Soroban RPC + Horizon), classifies x402 settlements
    structurally — no

    facilitator registration is required for a payment to appear — attributes
    each payment to the

    facilitator that submitted it, and enriches sellers via the x402 Bazaar.


    **Amounts** are stroop-scale integer strings (7 decimals). Every amount
    field has a

    `…Decimal` companion for display; never do arithmetic on the decimal form.


    **Confidence tiers** (every payment carries one; inference is never
    presented as fact):

    - `rail402` — submitted by the Rail402 deployment's published signer.

    - `verified-facilitator` — submitter matches a registered facilitator's live
    `/supported` signers.

    - `x402-shaped` — structurally an x402 settlement, submitter unknown.


    **History**: the full Soroban RPC retention window (~7 days) is backfilled
    for all

    facilitators including unknown ones, and every registry-verified
    facilitator's complete

    chain-epoch history (back to the 2025-12-17 testnet reset) is recovered from
    Horizon.

    Horizon-recovered rows have no `asset`/`assetCode` (that string only exists
    in event data);

    `assetContract` is always present.


    **Errors** are always `{ code, reason, retryable, details? }` — branch on
    `code`, never parse

    `reason`. CORS is open (`*`): browsers may call this API directly.
servers:
  - url: https://explorer-explorer.up.railway.app
    description: stellar:testnet
security: []
tags:
  - name: payments
    description: The payment stream and per-transaction detail
  - name: entities
    description: Sellers and facilitators
  - name: registry
    description: Facilitator self-registration
  - name: ops
    description: Health and metrics
paths:
  /stats:
    get:
      tags:
        - payments
      summary: Headline numbers
      operationId: getStats
      parameters:
        - name: network
          in: query
          schema:
            type: string
        - name: window
          in: query
          schema:
            type: string
            enum:
              - 24h
              - 7d
              - 30d
          description: >
            Scope every aggregate (totalPayments, uniqueBuyers, uniqueSellers,
            byScheme,

            byConfidence, byAsset, first/lastPaymentAt) to the trailing window;
            the response

            echoes `window` when set. Omit for all-time.
      responses:
        '200':
          description: Aggregates plus ingest health
          content:
            application/json:
              schema:
                allOf:
                  - $ref: '#/components/schemas/Stats'
                  - type: object
                    properties:
                      networks:
                        type: array
                        items:
                          type: string
                      ingest:
                        type: array
                        items:
                          $ref: '#/components/schemas/IngestHealth'
components:
  schemas:
    Stats:
      type: object
      required:
        - totalPayments
        - uniqueBuyers
        - uniqueSellers
        - byScheme
        - byConfidence
        - byAsset
      properties:
        totalPayments:
          type: integer
        uniqueBuyers:
          type: integer
        uniqueSellers:
          type: integer
        byScheme:
          type: object
          additionalProperties:
            type: integer
          example:
            exact: 653
            upto: 22
        byConfidence:
          type: object
          additionalProperties:
            type: integer
          example:
            rail402: 45
            verified-facilitator: 565
            x402-shaped: 65
        byAsset:
          type: array
          items:
            type: object
            required:
              - assetContract
              - count
              - total
            properties:
              assetContract:
                type: string
              asset:
                type: string
              count:
                type: integer
              total:
                type: string
                description: >-
                  BigInt-safe integer-string sum (never a float, never 64-bit
                  SQL)
        firstPaymentAt:
          type: string
          format: date-time
          description: >
            Earliest observed payment — the "data since" anchor. On mainnet this
            is the

            complete-history first for every watched/verified operator (Horizon
            retains full

            history); on testnet nothing older can exist (a chain reset wipes
            all upstream

            sources). It is an observation floor, not a network-wide "first
            ever" guarantee.
        lastPaymentAt:
          type: string
          format: date-time
    IngestHealth:
      type: object
      required:
        - network
        - consecutiveFailures
      properties:
        network:
          type: string
        epoch:
          type: string
        lastLedger:
          type: integer
        lastPollAt:
          type: string
          format: date-time
        lastError:
          type: string
        consecutiveFailures:
          type: integer
        backfill:
          type: string
          description: '"done" or "running (target ledger N)" — the Tier-1 deep backfill'

````