TPT/Documentation

PUBLIC BETA

TPT Documentation

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

Current production mode

Anonymous route and read access is enabled. Ledger and admin tools remain Bearer-protected. Live inbound collection is disabled while payment fulfillment is hardened.

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

Mount the public HTTP endpoint in your client.

Describe the outcome

Send the task, constraints, and optional atomic budget.

Receive evidence

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

Connect an MCP client

Use the same endpoint from an IDE, assistant, wallet, or upstream agent. TPT negotiates the MCP version per request and keeps a legacy compatibility path for older clients.

MCP client configuration

{
  "mcpServers": {
    "tpt": {
      "type": "http",
      "url": "https://tpt-xi.vercel.app/api/mcp"
    }
  }
}

Initialize over HTTP

curl -X POST https://tpt-xi.vercel.app/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

→

04Executepolicy gate + fallback

Intent planner: ClawRouter returns structured capability fit for known candidates.
Hard constraints: capability fit and budgetAtomic can remove a candidate regardless of score.
Fallback: execution continues through ranked candidates up to the configured attempt limit.
Learning: latency and reliability measurements feed future ranking.

tools/call · route arguments

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

Read the intent-routing specification →

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.AI

Discovery is not execution. Public endpoints are inspected lazily and still pass protocol, URL, tool-safety, credential, and outbound policy gates before a call is allowed.

REFERENCE

MCP tools and resources

Tool	Purpose	Access
`route`	Understand, rank, execute, and return a receipt.	Public beta
`classify`	Explain scores, constraints, and fallback without execution.	Public beta
`list_routes`	Inspect quotes, latency, reliability, trust, and readiness.	Public beta
`ledger`	Review receipts, costs, balances, and settlement evidence.	Bearer

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

HTTP API

Endpoint	Method	Description
`/api/mcp`	POST	Stateless MCP entry point.
`/marketplace.json`	GET	Search and paginate the normalized catalog.
`/metrics.json`	GET	Public product usage totals.
`/api/health`	GET	Runtime, state, auth, payment, and route readiness.
`/api/cron-marketplace-sync`	GET / POST	Protected provider snapshot refresh.

Open the live catalog JSON →

OPERATIONS

Authentication and safety

Production uses hybrid auth. Anonymous clients can discover and route during the public beta; 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.

Deadline policy

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

Payments

TPT has adapters for canonical x402, OKX x402 v2, and Thru. Collection stage and outbound spending are separate controls.

Production collection is currently disabled.

The Marketplace is running in free launch mode while paid fulfillment recovery is completed. Payment adapters remain fail-closed when required capability, identity, or settlement evidence is missing.

Read the payment-rails specification →

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.

Connect a Neon database and configure the required encrypted environment variables.
Keep TPT_PAYMENT_STAGE=disabled until the payment rollout gates are satisfied.
Run npm run verify and the environment-specific deployment preflight.
Push main; Vercel builds the static docs and serverless functions together.

Open the production runbook →

Previous← The Stack NextLaunch the App →