How it works · a vision paper

Agents can call anything. Almost nothing is worth calling.

ChatGPT, Claude and Gemini already accept custom MCP servers. The client half of the agentic economy is finished and in everybody's hands. The supply half is missing: the data worth calling sits behind aggregator fees, behind $15–30K seat licences, or nowhere at all — and no open registry of vertical sources exists to connect. This paper sets out the network that builds one. Who collects the data, what makes a record trustworthy enough for an agent to act on rather than merely read, and how a vertical is served per call with no platform in the middle.

Thesis · the connector shipped, the supply did not Five sections, four figures · the missing layer, the network, the record, the query Reading time · about seven minutes
01Fig. 1

The problem

Professional-grade data exists. Reaching it directly does not. It sits inside aggregator platforms that own the interface to it, or it sits nowhere in particular — spread across the sites of the people who actually hold it, in whatever shape they happened to choose. Either way, nobody gets to ask a direct question and receive a direct answer.

That arrangement has a price, and it is paid twice. Visibility goes to whoever can afford it: search placement yesterday, placement inside answer engines today. Access goes through platforms that rent out other people's inventory and take a cut of every booking, every lead, every deal. The provider raises the price to cover the cut, and the buyer pays it. The businesses whose data is being monetised are the ones left with the thinnest margin in the chain.

Where a vertical has been properly assembled, it is sold the way it has always been sold — per seat, per year, to institutions. Bloomberg for markets, CoStar for commercial property, PitchBook for private companies: each of them excellent, and each of them closed. A licence, a login, and a vertical you may read but cannot plug into anything. Building one takes 100+ human researchers and the result goes for $15–30K a seat. That moat is exactly what a contributor network inverts.

The demand is changing shape

The economy is moving from one where a person does the research to one where an agent does it for them. That changes what it means to be represented at all. For two decades the answer was SEO — be findable by a search engine. Lately it is GEO — be quotable by an answer engine. The next answer is MCP: be callable by an agent. Not a page to be read, and not an API someone integrates once, but a surface an agent can query and act on by itself.

The connector shipped; the thing to connect did not

OpenAI, Anthropic and Google already let anyone attach a custom MCP server to their assistant. The client half of the agentic economy is finished and in everybody's hands. The supply half is missing: there is no open registry of vertical data sources that a person or a business can simply connect and start using. How that data gets gathered, kept current and distributed is the whole problem — and it is why agents still cannot do the things they are plainly supposed to do.

Assistants already accept custom MCP servers, and the data sits in aggregator platforms, per-seat terminals, or nowhere. The connectable layer between them does not exist yet. DEMAND ChatGPT Claude Gemini CUSTOM MCP · SUPPORTED Vertical data ANY PERSON OR BUSINESS CAN CONNECT DOES NOT EXIST YET SUPPLY Aggregator platforms Professional terminals Everyone else FEE ON EVERY DEAL PER-SEAT LICENCE NOT AGGREGATED AT ALL THE CLIENT HALF OF THE AGENTIC ECONOMY SHIPPED — THE SUPPLY HALF DID NOT
FIG. 1 — Assistants already accept custom MCP servers. What is missing is the layer between them and the data: vertical sources anyone can connect, rather than platforms that charge for the privilege of passing through.

What it unlocks

A place to stay
A vertical of properties, served over MCP. You connect it to the assistant that already knows your dates, your budget and who is travelling, and it proposes the two that fit instead of returning ten tabs. Because MCP carries actions and not only text, it checks the real price and books with the host directly — the platform fee that was inflating the nightly rate is simply not in the path.
A building to build
A vertical of construction suppliers, each reachable through its own agent. A developer's agent walks the whole list — specification, availability, price, lead time — and closes against the ones that answer. Procurement that occupies a team for weeks resolves in a single pass.
Then both sides
The first iteration is an agent calling an MCP server. The one after it is two agents settling something through one: the traveller's agent and the host's, the developer's and the supplier's. That only works if the data underneath is current and verifiable, which is what the rest of this paper is about.
02Fig. 2

A network instead of a research desk

The closed verticals were built the expensive way: a hundred researchers, a decade, and a seat licence to pay for them. MCPie builds them the other way round. Anyone with an AI subscription runs the open-source client. The client does the reading, the network does the checking, and a vertical assembles itself out of thousands of small, independently verified contributions.

Nobody owns the result. It is not an aggregator's inventory and it is not a terminal's catalogue. It is an open registry with a per-call price, and the contributors who built it earn from every record it confirms. The cycle is the same whatever the vertical covers — holiday lets in one country, building suppliers in one region, licensed contractors in one city:

A four-stage cycle: build, validate, publish, update. Update feeds back into build, so the set is continuously rebuilt rather than left to go stale. 0102 0304 BuildValidate PublishUpdate contributors readthe sources contributors mustagree, or it fails signed verticals,queryable at once sources drift, therecord is rebuilt RE-ENTERS AS NEW WORK — THE SET NEVER GOES STALE REJECTED, NOT AVERAGED
FIG. 2 — The cycle every vertical runs on. Stage 04 is not an endpoint: it re-enters at 01, which is the difference between a dataset and a living one. A research desk sells a snapshot that starts ageing the day it ships; a network keeps rebuilding.
01 BUILD

Run the open-source client. It reads a vertical's sources with the AI subscription you already pay for, and submits what it finds.

02 VALIDATE

The client cross-checks each record against other contributors' before it's accepted. Disagreements are rejected, not averaged.

03 PUBLISH

Validated records go live as signed verticals that agents can query immediately.

04 UPDATE

The client re-checks published data as it drifts — feeding straight back into 01, so the set never goes stale.

03Fig. 3

Why an agent can act on it

An agent that books the stay or commits to the supplier is not reading data. It is acting on it. A wrong nightly rate is a wrong booking; a stale lead time is a missed site date. In an economy where people do the research, a bad row costs a minute of someone's attention. In one where agents do it, a bad row becomes a transaction. Trust is therefore not a feature of the network. It is the condition on which the network is allowed to exist at all.

So a record earns publication; it does not arrive with it. Three properties are enforced before a field is allowed to answer a query, and one of them keeps running for the record's whole life.

One record passes three gates — proof of fetch, cross-validation and drift tracking — before and after publication. Conflicting records are rejected. one record SUBMITTED GATE 1 Proof of fetch where + when, kept GATE 2 Cross-validation independent agreement CONFLICT → REJECTED PUBLISHED Queryable signed, traceable GATE 3 · DRIFT TRACKING — RE-CHECKED FOR LIFE, REBUILT ON CHANGE
FIG. 3 — Gates 1 and 2 run before publication. Gate 3 never stops, which is why a published record can be trusted a year later — and why an agent can be allowed to act on it rather than merely read it.
Proof of fetch
Every record carries evidence of where and when it was collected, so a field can always be traced back to its source document.
Cross-validation
A record is only published once independent contributors agree on it. Conflicts are surfaced and rejected rather than silently merged.
Drift tracking
Published data is re-checked continuously. When a source changes, the record is rebuilt instead of quietly rotting.
04Fig. 4

Any agent can connect it

Every vertical is served as an MCP server — the same kind ChatGPT, Claude and Gemini already accept — and as a plain API for anyone not running an agent. There is no seat, no licence and no bundle. A query costs a query: each vertical carries an x402 endpoint, so an agent pays per call in USDC without a human opening an account first, and every field it receives is traced to the document it came from.

For the business inside the vertical, this is what representation now means. It was a page a search engine could index; then a passage an answer engine could quote; now it is a record an agent can call and act on. Nobody sells the placement, and nobody takes a cut of what the agent goes on to do.

The first verticals are forming now. Which grow next is decided by where contributors and demand actually point.

Each vertical is served as an MCP server with an x402 endpoint. An agent queries it, pays per call in USDC, and can trace any field back to its source document. FINALIZED DATA thousands of recordseach cross-validated each kept current ONE VERTICAL, SERVED MCP server search · get, per vertical x402 ENDPOINT pay per query, in USDC AGENT OR TEAM Queries it directly through MCP, or a normal API no seat licence, no bundle — only the calls actually made ANY FIELD TRACES BACK TO THE SOURCE DOCUMENT IT CAME FROM
FIG. 4 — Data moves left to right; provenance runs the whole way back. Both directions matter: one makes the data usable, the other makes it checkable — and no platform sits on the path between the two ends.
05

Where it goes

The first iteration is one agent calling one vertical: a traveller's assistant asking a registry of places to stay, a developer's agent walking a list of suppliers. That alone takes the platform out of the middle of the deal.

The second is two agents settling something through it. The host's agent holds the calendar and the price; the traveller's holds the dates and the budget; the vertical is the ground they both stand on, and the booking closes with neither person in the loop. The supplier's agent quotes, the developer's compares and commits. Agent-to-agent commerce is not a separate product to be built afterwards. It is what happens as soon as both sides of a market are callable and the record between them can be trusted.

That is the whole thesis. The connector has already shipped. The supply half is a network anyone can join, a registry anyone can connect, and a record anyone can check — built in the open by the people who need it, before someone builds it closed.