> ## 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. # One payment with its raw on-chain transaction > The same projection as `/feed` plus `raw` — the complete Soroban `getTransaction` JSON (envelope, auth entries, events) the classification was made from, so every claim is independently checkable against the ledger. ## OpenAPI ````yaml /api-reference/explorer.openapi.yaml get /tx/{hash} 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: /tx/{hash}: get: tags: - payments summary: One payment with its raw on-chain transaction description: > The same projection as `/feed` plus `raw` — the complete Soroban `getTransaction` JSON (envelope, auth entries, events) the classification was made from, so every claim is independently checkable against the ledger. operationId: getTransaction parameters: - name: hash in: path required: true schema: type: string pattern: ^[0-9a-fA-F]{64}$ - name: network in: query schema: type: string description: Disambiguates when the same hash exists on several observed networks responses: '200': description: Payment detail content: application/json: schema: $ref: '#/components/schemas/PaymentDetail' '400': $ref: '#/components/responses/InvalidQuery' '404': description: > Not an ingested payment. `retryable: true` — ingestion tails the ledger with a few seconds of lag, so a very recent settlement may simply not be here yet. content: application/json: schema: $ref: '#/components/schemas/Error' example: code: explorer_tx_not_found reason: >- No ingested payment matches this transaction hash. Either it is not an x402-shaped settlement, it predates ingestion, or it has not been observed yet. retryable: true details: hash: >- 0000000000000000000000000000000000000000000000000000000000000000 components: schemas: PaymentDetail: allOf: - $ref: '#/components/schemas/Payment' - type: object required: - payments - raw properties: payments: type: array description: > Every payment settled in this transaction. A transaction can settle several ops; the top-level fields mirror the first op (so a single-payment tx reads as one Payment), and this array holds them all. items: $ref: '#/components/schemas/Payment' raw: description: > The complete Soroban getTransaction JSON (envelope, auth entries, events) this classification was made from — every claim is independently checkable. type: object additionalProperties: true Error: type: object required: - code - reason - retryable properties: code: type: string description: >- Stable machine-readable identifier — branch on this, never on `reason` reason: type: string description: Non-null human-legible explanation retryable: type: boolean description: Whether an identical retry could plausibly succeed details: type: object additionalProperties: true Payment: type: object required: - network - epoch - ledger - txHash - scheme - buyer - seller - amount - amountDecimal - assetContract - txSource - facilitator - confidence - closedAt properties: network: type: string description: CAIP-2 network id example: stellar:testnet epoch: type: string description: > Chain-epoch discriminator. Testnet resets restart ledger numbering; rows never join across epochs. Treat (network, epoch, txHash) as the unique key. ledger: type: integer txHash: type: string example: c827992c48bfe911a9b68abcef62e135b2b9555e5211f5c0ea0cdecb3aa8d558 scheme: type: string enum: - exact - upto buyer: type: string description: The paying account (G… classic or C… smart contract account) seller: type: string description: The payTo address that received the payment amount: type: string description: >- Stroop-scale integer string of what actually moved. "0" is legal (upto nonce burn). example: '3500000' amountDecimal: type: string description: 7-decimal display form. Never do arithmetic on this. example: '0.35' ceiling: type: string description: upto only — the client-authorized maximum example: '10000000' ceilingDecimal: type: string example: '1' assetContract: type: string description: The SAC (token contract) the transfer happened on example: CBIELTK6YBZJU5UP2WWQEUCYKLPU6AUNZ2BQ4WWFEIE3USCIHMXQDAMA asset: type: string description: >- SEP-11 asset string ("native" or "CODE:ISSUER"). Absent on Horizon-backfilled rows. example: USDC:GBBD47IF6LWK7P7MDEVSCWR7DPUWV3NY3DTQEVFL4NAT4AQH3ZLLFLA5 assetCode: type: string description: >- Display code derived from `asset` (native → XLM). Absent when `asset` is. example: USDC txSource: type: string description: >- The account that submitted the transaction (facilitator signer/channel) feeSource: type: string description: Fee-bump fee source, when the envelope was fee-bumped feeChargedStroops: type: string description: Net fee the submitter actually paid (charge minus refund) example: '23086' facilitator: oneOf: - type: 'null' - type: object required: - id properties: id: type: string example: rail402 displayName: type: string example: Rail402 description: >- The attributed facilitator, or null when unknown (confidence x402-shaped) confidence: type: string enum: - rail402 - verified-facilitator - x402-shaped sigExpirationLedger: type: integer description: The buyer authorization's signatureExpirationLedger memo: type: string muxedId: type: string description: Destination muxed id when the transfer used a muxed account closedAt: type: string format: date-time description: Ledger close time serviceName: type: string description: Bazaar enrichment — WHAT was bought, when the seller is cataloged resource: type: string description: Bazaar enrichment — the resource URL responses: InvalidQuery: description: A parameter failed validation; details name it content: application/json: schema: $ref: '#/components/schemas/Error' example: code: explorer_invalid_query reason: Query parameter "scheme" must be one of exact, upto. retryable: false details: parameter: scheme value: bogus ````