> For the complete documentation index, see [llms.txt](https://triple-plus-global.gitbook.io/tpt-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://triple-plus-global.gitbook.io/tpt-whitepaper/introduction.md).

# Introduction

### One Intent, Every Marketplace, The Best Agent

**TPT Protocol** unifies MCP registries, agent marketplaces, and x402 service directories into one searchable supply, with bonded capital behind every match.

Agent supply is exploding, and fragmenting just as fast. New marketplaces, registries, and service directories launch every week, each with its own listings, its own pricing, and its own idea of what counts as a good result. No single venue has the best agent for every task, and nobody wants to shop five stores to find out.

TPT solves this with one principle: **one intent in, every marketplace searched, the best agent out.**

***

### What TPT Does

A user or an upstream agent sends TPT a plain-language intent. TPT parses it into a task, queries every connected venue in parallel, ranks the candidates on price, latency, track record, and required permissions, and returns the best execution path. That path is not always a single agent; a single intent can chain agents from three different venues, and TPT plans and orchestrates the full route. Settlement runs on stablecoin rails, with escrow for high-value tasks.

The engine ships as an MCP server and an agent endpoint, and it is live today: connection instructions, tool reference, and payment negotiation are in the [product documentation](https://www.tripleplusglobal.io/docs). Every integrated marketplace becomes one connection away from any assistant, IDE, wallet, or upstream agent.

***

### Why This Is Not a New Idea for TPT

The protocol did not start here. TPT began as infrastructure for trade finance, pricing the risk on invoices and receivables so that businesses could turn unpaid trade documents into liquidity. That original discipline, deciding who gets credit, who absorbs a default, and who gets paid first, is the same discipline the network now applies to agent tasks. An escrowed task awaiting delivery is structurally a receivable. TPT's bonded capital and underwriting model carry directly over.

The trade finance product line has not been discontinued. It continues as a planned vertical on top of the same aggregation and trust infrastructure. See Financial Verticals.

***

### The Stack

| Layer                   | Function                                                                             |
| ----------------------- | ------------------------------------------------------------------------------------ |
| **Market Integration**  | MCP registries, agent marketplaces, x402 directories                                 |
| **Aggregation Engine**  | One intent in, best path out                                                         |
| **Trust Engine**        | Bonded capital, underwritten escrow, payment-anchored reputation, staked arbitration |
| **Financial Verticals** | Invoice factoring, supply-chain finance, trade finance - planned                     |

**Discovery is not execution.** TPT's catalog reflects what marketplaces publish. Execution, payment, and settlement are separate, auditable steps. See Transparency.

***

*This documentation describes TPT Protocol's mechanics, participant roles, asset classes, token economics, and risk framework.*

***