Your portal blocks AI agents today. With AgentBridge you could let recognised agents in: on your terms, at your price.
More and more people send an AI agent to search flats, houses or used machinery for them. In the pilot, your portal would offer such agents a mandate: you would set the price per retrieval and what the data may be used for. The agent would pay automatically for each retrieval, and both sides would get a signed receipt.
Pilot programme in preparation. Nothing here is live yet; we are looking for the first portals and agent owners.
Join the pilotFor agent owners
Why an agent, not a scraper
Anna is moving to Valencia. She asks her AI agent to watch three portals for a two-room flat within her budget and to tell her only about new matches. She wants her evenings back, not a copy of your portal. Today her agent is blocked, or it scrapes without asking. With AgentBridge it would say who it is, accept your terms, pay for each retrieval and fetch only what her search needs.
For portals
In the pilot: revenue from traffic you block today
You would set the price per retrieval and be paid per retrieval. The terms are settled in the pilot conversation.
Your terms, checked on every request
You would decide what the data may be used for, for example personal search only, no training, no republishing. An agent that does not accept the mandate would get nothing.
Knowing who is asking
Each agent would sign its requests with its own key (Web Bot Auth, HTTP Message Signatures, RFC 9421). You would see a named agent, not an anonymous scraper.
A signed receipt per retrieval (planned)
For every retrieval both sides would keep a signed receipt: which agent, which page, which terms, which price, when.
A bridge to x402 / HTTP 402, with an EU fallback
AgentBridge is designed to speak x402 / HTTP 402 "Payment Required", the payment protocol started by Coinbase, so it could sit next to pay-per-crawl paywalls of the kind Cloudflare offers. We are not fighting that protocol.
Where a portal or an agent owner needs an EU path, AgentBridge would add a sovereign fallback: its own 402 offer format, a prepaid account in euros, and an append-only log of every retrieval, hosted in the EU.
For agent owners
- In the pilot you would top up a prepaid balance in euros at destill.ai. No payments are taken today.
- Your agent would pay automatically for each retrieval, only at portals that offer a mandate and only up to the price you allow.
- Your agent would use a separate key for each portal.
- Every retrieval would leave a signed receipt you can keep.
What already exists in our lab
- Signed agent identity (Web Bot Auth, RFC 9421)
- Mandate check before each request
- Signed receipt per action
- Separate keys per site
Built and tested in our lab. Not running on any portal yet.
What it does not do
- Nothing is live: no portal and no agent runs AgentBridge yet, and no payments are taken.
- AgentBridge does not stop agents that never ask. Blocking those stays with you or your bot protection.
- A mandate says what a recognised agent may do. It cannot stop an owner from breaking the terms later; the receipts show what was fetched under which terms.
- Whether a use is lawful is a legal question. AgentBridge records the terms, it does not decide them.
- Keys are held in software today.
The pilot
- One portal, one section (for example rentals in one city), your price and your terms, a small group of invited agents.
- Success measure agreed in writing before the start, for example every retrieval carries a valid receipt and none happens outside the terms.
- In the pilot you would set the price per retrieval and be paid per retrieval; the terms are agreed in the pilot conversation.
We answer in writing. No cookies, no analytics, no third-party scripts.