TPTDocs
⌘ K
Documentation menu +
TPT/Documentation
PUBLIC BETA

TPT Documentation

One MCP endpoint for discovering, ranking, and executing services across agent marketplaces.

Mainnet only

TPT is Mainnet-only. Connect at /api/mcp using Sui Mainnet or Robinhood Chain. Former Testnet endpoints return HTTP 410 and do not accept requests or payments.

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.

1

Connect

Mount the public HTTP endpoint in your client.

2

Describe the outcome

Send the task, constraints, and optional atomic budget.

3

Receive evidence

Get the result, selected route, attempts, cost, and receipt.

Connect an MCP client

Use Mainnet for wallet and x402 integrations. Discovery and classification do not require payment; an executable route returns its exact quote before signing. TPT negotiates the MCP version per request and supports older clients.

MCP client configuration
{
  "mcpServers": {
    "tpt-mainnet": {
      "type": "http",
      "url": "https://app.tripleplusglobal.io/api/mcp"
    }
  }
}
Initialize over HTTP
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.

01Understandgoal · capabilities · constraints
→
02Retrievecatalog + curated routes
→
03Rankfit · cost · latency · trust
→
04Quotequery fee · provider cost
→
05Executepolicy gate + fallback
  • 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. The budget is the all-in ceiling: provider cost plus TPT fee.
  • 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.
tools/call · route arguments
{
  "name": "route",
  "arguments": {
    "query": "Find the official Durable Objects consistency model",
    "budgetAtomic": "50000"
  }
}
x402 payment negotiation
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

# Mainnet route calls -> HTTP 402 for the published 0.01 stablecoin query fee
# Downstream provider cost, when any, is included inside budgetAtomic
# Retry the same body with PAYMENT-SIGNATURE after the wallet signs.
Read the intent-routing guide →

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.

01Official MCP Registry02Coinbase x402 Bazaar03Virtuals ACP04Agentverse05Olas Mech06Nevermined07Smithery08Glama09OKX.AI10Work40211Awesome x402
Discovery is not execution. Marketplace rows expose separate catalog sync, execution mode, and fresh MCP handshake evidence. Production routing is limited to explicitly approved routes; catalog MCP execution stays disabled until a real read-only tool canary is approved. The weekly validator only initializes and lists tools; it never invokes a tool, signs a payment, or claims settlement.

REFERENCE

MCP tools and resources

ToolPurposeAccess
routeUnderstand, rank, execute, and return a receipt.Public beta
classifyExplain scores, constraints, and fallback without execution.Public beta
list_routesInspect quotes, latency, reliability, trust, and readiness.Public beta
ledgerReview receipts, costs, balances, and settlement evidence.Admin only; hidden otherwise

Public resources include tpt://config, tpt://routes, tpt://marketplaces, and the paginated tpt://catalog. tpt://ledger is registered only for an admin-scoped session.

HTTP API

EndpointMethodDescription
/api/mcpPOSTMainnet stateless MCP entry point.
/api/chat-historyGET / PATCH / DELETEWallet-scoped runs and routing feedback.
/marketplace.jsonGETSearch and paginate the normalized catalog.
/api/payment-railsGETConfigured rail capabilities; readiness is not settlement evidence.
/metrics.jsonGETPublic product usage totals.
/api/healthGETRuntime, state, auth, payment, and route readiness.
/api/cron-marketplace-syncGET / POSTProtected provider snapshot refresh.
Open the live catalog JSON →

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.

URL policy

Remote execution is HTTPS-only and rejects private, credential-bearing, or sensitive-query targets.

Tool policy

Discovered MCPs default to safe read-only tools; mutation and payment require explicit approval.

State policy

Neon provides cross-instance replay protection, leases, atomic limits, and last-known-good snapshots.

Chat identity

EVM or Sui wallets sign a five-minute nonce. TPT consumes it once and stores the resulting 12-hour session in an HttpOnly cookie.

Deadline policy

A request-wide budget cancels unfinished work before Vercel’s function deadline.

Payments

TPT uses x402 with Thru for Sui and Robinhood Mainnet payments. Send X-TPT-Payment-Chain: sui or robinhood so TPT returns a wallet-compatible Mainnet challenge.

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.

Robinhood Gas Tank is a facilitator settlement dependency.

TPT can advertise the verified rail and produce an EIP-3009 signing request without a local relayer key. Thru must have Gas Tank funds before it can broadcast settlement; an advertised rail is not the same as a completed canary.

Read the payment-rails guide →

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 TPT_MAINNET_STATE_NAMESPACE=tpt-production-mainnet and configure only Mainnet payment rails.
  3. Run npm run verify and the environment-specific deployment preflight.
  4. Push main; Vercel builds the static docs and serverless functions together.
Read the production guide →
TPT Protocol documentation · Updated August 2026