This is the composition mindset: an AI service is a building block, not a destination. A real problem — “tell me everything the web knows about this person” — is several blocks (search, scrape, capture, synthesis) the Catalog proposes and the Router pays for, one call at a time.
Services are building blocks
The old way
Choose a vendor per capability. Create an account with each. Manage a key per account. Write the glue that calls them in order. Repeat for the next problem.
The Catalog way
State the outcome and a budget. Your agent searches the Catalog for each block, proposes a chain of real services, and the Router pays per call — no accounts, no keys, no glue.
How an outcome comes together
1
State the problem and a budget
One prompt: the result you want, and the most you’ll spend getting it. The budget is the guardrail — the agent works within it.
2
The agent searches the Catalog (free)
Discovery needs no key and costs nothing. The agent breaks the problem into blocks and searches for each — search, scrape, synthesis — reading real slugs, prices, and health.
3
The Catalog proposes a chain
Candidate services per block, ranked and priced. This is the “solution” — a concrete set of services that, chained, produce the outcome. You can see it before a cent is spent.
4
Approve a cap once, and it runs
Approve a spending cap, and the Router pays each call within it. Connecting and paying is covered in Using the Catalog from your web assistant and from a harness.
Prompts you can paste
Paste any of these into a harness connected to the Catalog — Claude Code, Claude.ai or ChatGPT with the Nevermined connector, or any MCP host. Each states an outcome and a budget; the agent discovers the building blocks and proposes the chain before spending. The services and prices under each are what the Live Catalog returns today — verified, not illustrative.Prices are per call, as listed today — the Catalog is live and prices drift, so your harness reads the current label. Totals aren’t fixed: a run costs the sum of the calls the agent actually makes, always bounded by the budget you set.
1. Everything the open web knows about a person
The agent searches, scrapes the top results, captures the pages, and has the LLM write the report — each call drawn from your $1.00 cap.
2. A daily brief on a crypto position, priced and sourced
3. Qualify an inbound lead before you reply
More outcomes, same shape
Every one of these is a single prompt with a budget — no wiring, no per-service integration:- Watch a competitor page and report what changed — Web Scraping (
serper-scrape,screenshotone) + AI synthesis. - Check a product batch against public safety recalls — Data & Enrichment + AI synthesis.
- Find the cheapest venue to execute a trade right now — Crypto & Blockchain + Finance & Markets (
coingecko-via-mpp,crypto-data).
See what the Catalog proposes
The discovery step is public and free — no key, no budget, no spend. Run these against production and you’ll see the same services a harness would propose. All four are verified working as written. Browse the whole catalog, see the real shape of a listing (.total is the live count):
Turn a proposal into a run
The proposal is free; executing it — paying each call within your cap — is the connect-and-pay flow:From your web assistant
Connect the Catalog to Claude.ai, ChatGPT, or LangSmith Fleet and approve a cap once.
From a harness
The code-free playbook for driving discovery and payment from your own agent.
Catalog MCP
The
pay_service tool, the spending Delegation, and every refusal code.Payment ledger
Read back exactly what each call cost and how much of the cap is left.