Federated search finds paid capability sources with live pricing before your agent commits spend.
The buy-side of machine-native commerce.
SELAT gives agents one purchase motion for paid capabilities they discover at runtime: data, scraping, media, compute, and on-chain actions. One self-custody treasury, hard caps before spend, provider-native settlement, and one reconciled ledger.
Agent setup
Copy & paste this prompt into your agent:
Help me set up SELAT. Read https://selat.ai/llms.txt and follow the SELAT plugin install instructions for this harness. Use the SELAT-AI/selat-plugins marketplace repo, keep discovery free, and ask me before any command that spends or moves funds.
Works with
What your agent can't do yet is one paid call away.
Your agent runs skills; skills call paid endpoints. SELAT reaches both at runtime, so the catalog lives where your agent works: in the terminal, through free discovery, before wallet setup or spend. The protocol is the integration: nothing here was hand-integrated and nothing is gatekept. The catalog grows as the rails' merchant pool grows.
| Registry | Merchants | Endpoints | Categories | Rail // Settles |
|---|---|---|---|---|
| agents.circle.com | 20+ vetted merchants — QuickNode, Alchemy, Exa, Messari, BlockRun | 600+ | Chain data, inference, enrichment, email, market data | x402 // USDC on Base, Polygon + 10 more chains |
| Agentic.Market | 650+ merchant domains — indexes the x402 Bazaar and beyond | 20,000+ listed | Search, data, inference, media, social, trading | x402 // USDC on Base, Solana, Polygon |
| mpp.dev/services | 130+ services — Browserbase, Dune, Allium, AgentMail first-party | 1,400+ | Data, AI, web, search, compute | MPP // Tempo |
| Apify Store | Community Actor developers — each Actor its own merchant | 20,000+ Actors | Scraping, automation, integrations | x402 prepaid token // USDC on Base |
The catalog lives in your terminal
selat skill list --available # vetted skills, ready to run
selat search "<what you need>" # the whole catalog, rankedBoth free. No wallet required until you choose a paid run.
Discover, fund, authorize, execute, reconcile.
Create and fund one self-custody treasury once. Per-provider onboarding disappears.
Purchasing policy lives at the money layer, with caps checked before every signed payment.
Each provider is paid natively on the protocol, scheme, and chain it already accepts.
The result returns with a receipt, and every purchase lands in one ledger.
The provider picks the rail. Your agent doesn't care.
A paid step might answer with x402, MPP, or the next machine-payment protocol, each with its own flow, scheme state, and settlement chain. SELAT reads the quote, checks your caps, pays the provider natively, and records the purchase, attributed to that provider, in one treasury ledger.
Chained run
Every AI workflow becomes a purchasing workflow.
Real agent work rarely stops at one endpoint. A research run might buy search, scraping, enrichment, and delivery from different providers in sequence. SELAT keeps that chain inside one execution: each step gets a live quote, caps are checked before spend, and each provider is paid on its own rail.
Your agent sees one run, not a stack of vendor errands. You see the final result plus itemized receipts, with every purchase attributed to the provider it paid and reconciled in one ledger.
Chained RunOne execution• Live quote per step
• Caps before spend
• Itemized receipts
• Caps before spend
• Itemized receipts
Jun 26, 2026
Why AI Agents Break the Moment a Task Needs Payment
Agents can discover services mid-task but stall when payment starts — no runtime payment surface, no shared credentials, no unified liquidity. Here's why agents break at payment, and what closes the gap.
Jun 18, 2026Multi-Rail Agent Payment Routing: One Wallet, Every Rail
As agent payment rails multiply — x402, MPP, Circle Gateway — builders pay an integration tax that grows with each one. Here's the case for rail-neutral routing: one wallet, one signature, every rail.
Jun 10, 2026x402 vs MPP: Which Agent Payment Protocol Should You Use? (2026)
x402 and MPP both let AI agents pay for APIs over HTTP 402 — but they settle differently. A builder's comparison of rails, costs, and when to use each (or both).
Jun 5, 2026How AI Agents Pay for APIs: A Builder's Guide to Agentic Payments
AI agents can now pay for APIs, data, and compute mid-task — no human checkout. Here's how agentic payments actually work, from HTTP 402 to wallets, rails, and spending limits.