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

> ## Agent Instructions
> Tribridge is a crypto payment gateway for Solana and Sui (TON is coming soon). API base URL is https://api.tribridge.xyz. The API Reference documents ONLY the public endpoint surface: checkout sessions (create/get/generate-wallet/customer/simulate/verify/cancel), the two public payment-link endpoints, health probes, and the changelog. Server-side calls that create payments authenticate with the x-api-key header using a tri_test_... key (fully simulated test mode, no real funds) or tri_live_... key (real mainnet payments) - never expose keys client-side; all other documented endpoints are public with no auth. Dashboard, admin, OTP/auth, payouts, wallets, and webhook-management endpoints are intentionally NOT part of the public docs - they are dashboard-only and must not be presented as public API. Merchant test mode is simulated, not testnet. Refunds are automatic only (underpaid/overpaid), there is no manual refund endpoint. Always verify webhook HMAC-SHA256 signatures from the X-Tribridge-Signature header before trusting payloads. If you are an AI agent: fetch https://docs.tribridge.xyz/llms-full.txt for all documentation in one file, https://docs.tribridge.xyz/openapi/openapi.json for the machine-readable OpenAPI spec, or connect to the read-only MCP server at https://docs.tribridge.xyz/mcp. Any page is available as Markdown by appending .md to its URL. Use only the documented endpoints and fields; do not invent SDK packages or endpoints.

# Health & status

> Liveness probe plus Solana/Sui RPC health checks — no auth.

Quick probes for uptime monitoring and integration debugging. All health endpoints are public and never touch your merchant data.

## Endpoints

| Endpoint | Returns |
| - | - |
| `GET /health/rpc` | Combined Solana + Sui probe: `{ "solana": {ok, latencyMs, slot}, "sui": {ok, latencyMs} }` |
| `GET /health/rpc/solana` | Solana only: `{ "ok": true, "latencyMs": 142, "slot": 312874615 }` |
| `GET /health/rpc/sui` | Sui only: `{ "ok": true, "latencyMs": 96 }` |
| `GET /` | Server liveness: `{ "status": "ok" }` |

```bash Chain-specific probes theme={null}
curl https://api.tribridge.xyz/health/rpc/solana
curl https://api.tribridge.xyz/health/rpc/sui
curl https://api.tribridge.xyz/
```

> [!NOTE]
>
> `ok: false` on a chain means Tribridge currently can't reach that chain's RPC — live deposits on that chain will be delayed. `latencyMs` is the probe round-trip; `slot` (Solana) is the latest observed slot. Test mode is unaffected: it never touches the chain.


## OpenAPI

````yaml GET /health/rpc
openapi: 3.1.0
info:
  title: Tribridge API
  version: 1.0.0
  description: >-
    Public Tribridge API for accepting Solana and Sui payments. Base URL:
    `https://api.tribridge.xyz`.


    This reference covers **only the public surface**: endpoints callable
    without a dashboard session — either fully public or authenticated with a
    merchant `x-api-key`. Dashboard, admin, and account-management endpoints are
    intentionally excluded; manage those from your Tribridge dashboard.


    **Test vs live:** the mode is derived from the key you send (`tri_test_...`
    creates simulated test payments, `tri_live_...` real mainnet payments) —
    never from the request body. Minimum payment amount is $0.50. Rate limit:
    100 requests/minute per IP.
servers:
  - url: https://api.tribridge.xyz
security: []
tags:
  - name: Checkout Sessions
    description: >-
      Create payments, drive the hosted checkout, and follow the customer flow:
      deposit wallet, receipt contact, simulation, verification, cancellation.
  - name: Payment Links
    description: >-
      Read a public payment link and materialize a checkout from it — no API key
      required.
  - name: Status
    description: Service and blockchain RPC health, plus the public changelog.
paths:
  /health/rpc:
    get:
      tags:
        - Status
      summary: Blockchain RPC health
      description: >-
        Combined health probe for the Solana and Sui RPC connections Tribridge
        relies on. No auth.
      operationId: getRpcHealth
      responses:
        '200':
          description: Per-chain health
          content:
            application/json:
              examples:
                healthy:
                  value:
                    solana:
                      ok: true
                      latencyMs: 142
                      slot: 312874615
                    sui:
                      ok: true
                      latencyMs: 96
                degraded:
                  value:
                    solana:
                      ok: true
                      latencyMs: 142
                      slot: 312874615
                    sui:
                      ok: false
                      latencyMs: 5001

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.