# I opened a live agent marketplace. The receipts were the product.

> Source: <https://dev.to/alexar76/i-opened-a-live-agent-marketplace-the-receipts-were-the-product-4hl1>
> Published: 2026-09-15 11:19:16+00:00

Most “agent economy” posts sell you a framework, a Discord, or a token.

I wanted the boring thing: **a public catalog where an agent can find a tool, call it, and keep a receipt** — without me standing in the loop.

That surface is live. It is called **AIMarket Hub**. The URL is [modelmarket.dev](https://modelmarket.dev). Crypto stays off this title on purpose. The shape here is discover → invoke → receipt.

Counted **2026-09-15** from [`/ai-market/v2/stats/live`](https://modelmarket.dev/ai-market/v2/stats/live):

| Invokes | **710** (704 ok — 99.2%) | 
| External / self | 700 / 10 | 
| Federated hubs | **14** | 
| Capabilities | **177** | 
| p50 latency (24h) | **90 ms** | 
| Revenue / hour | **$0.0010** | 

That last number is the honesty tax. This is not Uniswap. It is a small live market that already meters calls. The screenshots below are the product, not a mock.

*The terminal. EN UI. MCP remote in the same chrome: `https://modelmarket.dev/mcp`.*

**If your agent stack only works inside a demo transcript, you don't have a market — you have a screenshot.**

A market needs supply, demand, a place they meet, a price, and a way to fail out loud. The Hub is that place. Frameworks are how you *talk* to it.

We already wrote the 15-minute “list your own HTTP tool” walkthrough ([publish-and-earn](https://dev.to/alexar76/i-made-my-api-discoverable-to-ai-agents-and-got-it-paid-per-call-in-15-minutes-4kin)) and the two-tool MCP door ([Hub MCP](https://dev.to/alexar76/i-connected-one-mcp-server-it-searched-a-live-marketplace-and-returned-a-signed-weather-receipt-204e)). This piece is narrower: **open the live terminal and read what it is actually doing.**

`source_hub`.
HTTP **402** is a product feature, not an error page: Channel → Invoke → Receipt → Settle. Settlement exists (USDC on Base, small demo funds). You do not need a wallet to *watch* the feed or run a free trial.

*EXT = someone else paid. One weather row at 475 ms is free and red — fail loud, not a painted success.*

When I loaded the page, the tape was not a synthetic demo reel. It was:

| capability | hub | price | latency | 
|---|---|---|---|
| `gaia.weather.read@v1` | iot.modelmarket.dev | $0.001 | ~80–97 ms | 
| `sortes.draw@v1` | oracles family | $0.006 | 18 ms | 
| `murmuration.aggregate@v1` | oracles family | $0.002 | 48 ms | 

Weather dominates. That is honest demand, not a balanced pie chart. Sortes is the verifiable-draw capability other live surfaces actually spend. This article is not those products. One failed weather call sits in the same list as the successes. Pretty dashboards that hide the red row are cosplay.

The decoder strip above the table is the same grammar: `capability_id` → route `[LOCAL/FED]` → traffic `[EXT/SELF]` → `$` → ms → ✓/✗.

*Match, not autocomplete theatre. Prices and “click to try free” on the same card.*

I typed **fair randomness for a lottery**. Back came, among others:

`sortes.verify@v1` — verify an ECVRF proof offline · `platon.beacon@v1` — hash-chained randomness beacon · `platon.random@v1` — signed chaos-VRF · Search is a **catalogue**. It is not a lottery. Read the description before you spend a trial. The Hub already has a free-trial path (a handful of invokes per visitor per hour) so you can feel a receipt before any wallet.

Same box accepts other intents the landing already suggests: *wildfire brief near a facility*, *protect a ship from navigation spoofing*. Those are live SKUs with their own honesty footnotes. This article does not tour them.

Three doors. Pick one. Do not install seventeen servers.

| Door | What it is | 
|---|---|
| **Terminal** | [modelmarket.dev](https://modelmarket.dev) — search, try, watch the feed | 
| **MCP** | `https://modelmarket.dev/mcp` — two tools:`market_search` ,`market_invoke` | 
| **CLI** | [`pip install aimarket-hub`](https://pypi.org/project/aimarket-hub/) — publish your own capability | 

If you want agents inside LangGraph/CrewAI to see the catalogue as native tools, that is a [two-line bridge](https://dev.to/alexar76/181-more-tools-for-your-langgraph-agent-in-two-lines-2g76). If you want to *list* an endpoint you already have, that is the 15-minute article. This page is the room those posts assume is real.

Production listing still has gates (publish token, signed provider responses, supply-security). Start on the public terminal or a local hub. Don't paste a localhost `invoke_url` at prod and act surprised.

If a market that fails loud and keeps receipts is your kind of boring, a ⭐ on the hub repo helps other people find the example. Concrete issues help more than a polite “cool stack.”

*Built in the open. The screenshots are the product, not a mock. Numbers from 2026-09-15.*