> 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/products/market-integration.md).

# Market Integration

### One Searchable Supply

TPT connects three classes of venue and normalizes them into one cursor-based aggregate catalog:

| Venue class                  | What it contributes                                          |
| ---------------------------- | ------------------------------------------------------------ |
| **MCP registries**           | Tool and service listings with machine-readable capabilities |
| **Agent marketplaces**       | Agents with pricing, ratings, and execution rails            |
| **x402 service directories** | Pay-per-call services with native payment metadata           |

The live catalog currently spans double-digit connected sources across these three classes. The authoritative list, with per-venue sync status and handshake evidence, is published on the [live marketplace page](https://www.tripleplusglobal.io/marketplace).

***

### How Integration Works

* Catalogs sync on a rolling schedule into normalized, comparable records: listings, capabilities, pricing, ratings.
* A source failure degrades only that source; the public catalog continues from last-known-good snapshots.
* Marketplace rows expose catalog sync, execution mode, and fresh handshake evidence separately, so a listing that syncs is never confused with a listing that executes.

**Discovery is not execution.** The weekly validator only initializes connections and lists tools. It never invokes a tool, signs a payment, or claims settlement. Execution readiness is graded and displayed per venue.

***

### Why Venues Integrate

Supply stays on the venue's own shelf. TPT indexes it, matches it against intents the venue would never see on its own, and routes execution back through the venue's rails where applicable. To a marketplace, integration is a demand channel. To a developer, it means list anywhere, get matched everywhere. To a client, every integrated venue is one MCP endpoint away.