TPT Documentation

GETTING STARTED

Quickstart

TPT is a stateless Streamable HTTP MCP server. Add the endpoint to an MCP-compatible client, initialize the connection, then call route with a natural-language goal.

Connect an MCP client

Use Mainnet for production traffic and Testnet while developing wallet or x402 integrations. TPT negotiates the MCP version per request and keeps a legacy compatibility path for older clients.

{
  "mcpServers": {
    "tpt-mainnet": {
      "type": "http",
      "url": "https://app.tripleplusglobal.io/api/mcp"
    },
    "tpt-testnet": {
      "type": "http",
      "url": "https://app.tripleplusglobal.io/api/testnet/mcp"
    }
  }
}

curl -X POST https://app.tripleplusglobal.io/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-11-25",
      "capabilities": {},
      "clientInfo": { "name": "my-agent", "version": "1.0.0" }
    }
  }'

Use Accept: application/json, text/event-stream. JSON responses are used for ordinary calls; subscription streams remain SSE.

CORE CONCEPTS

How routing works

The model interprets intent and scores a bounded menu of known candidates. Local policy remains authoritative: the model cannot invent an endpoint, credential, payment rule, or route ID.

• Intent planner: Gemini returns structured capability fit for known candidates; deterministic policy remains available when the model is unavailable.
• Hard constraints: capability fit and budgetAtomic can remove a candidate regardless of score.
• Fallback: execution stays inside the prepared route policy. A free plan never crosses into a paid route, and a signed retry never switches provider.
• Learning: provider outcomes, latency, normalized failures, and explicit Chat feedback feed future ranking.

{
  "name": "route",
  "arguments": {
    "query": "Find the official Durable Objects consistency model",
    "budgetAtomic": "5000"
  }
}

curl -X POST https://app.tripleplusglobal.io/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "X-TPT-Payment-Chain: robinhood" \
  --data @request.json

# Free selected route  -> result immediately
# Paid selected route  -> HTTP 402 + PAYMENT-REQUIRED + paymentAction
# Retry the same body with PAYMENT-SIGNATURE after the wallet signs.

Marketplace aggregation

TPT normalizes MCPs, agents, services, and jobs from independent marketplaces into one cursor-based catalog. A provider failure degrades only that source; the public catalog continues from last-known-good snapshots.

REFERENCE

MCP tools and resources

Resources include tpt://config, tpt://routes, tpt://ledger, tpt://marketplaces, and the paginated tpt://catalog.

HTTP API

OPERATIONS

Authentication and safety

Production uses hybrid auth. Catalog discovery and the MCP route remain public during beta, while browser Chat requires a connected wallet and one-time nonce signature. Stateful financial and operator surfaces require a Bearer token.

Payments

TPT supports canonical x402, OKX x402 v2, and Thru. Mainnet and Testnet never share an endpoint or payment proof. Send X-TPT-Payment-Chain: sui or robinhood so TPT returns a wallet-compatible challenge for the selected environment.

A paid 402 includes a five-minute wallet authorization and a ten-minute X-TPT-Route-Plan bound to the exact request, route, provider budget, asset, and network. The wallet retries the same body and proof; an expired or mismatched plan is rejected before execution.

Deploy on Vercel

The frontend is a Next.js static export. MCP, health, metrics, marketplace, and cron remain isolated Vercel Functions backed by Neon Postgres.

1. Connect a Neon database and configure the required encrypted environment variables.
2. Use a dedicated *-testnet state namespace and TPT_ALLOW_PRODUCTION_TESTNET=true for the temporary production canary.
3. Run npm run verify and the environment-specific deployment preflight.
4. Push main; Vercel builds the static docs and serverless functions together.