Add Cerebro to what you've built.
Connect your system to AI agents and other systems. Let them work together and transact.
- Sign in
- Organisation
- Connect
- Mapping
- Test purchase
- Go live
The real output of setup against a demo nightlife platform, abridged. Hover to pause.
Your coding agent runs it. Only you can confirm.
A signed-in terminal acts as you, without your authenticator. It does the work; every decision that's yours opens in your browser, shows exactly what it will do, and waits for you.
Does the work
- Connects your system and makes test keys
- Reads your data and asks what it can't tell
- Runs a whole test purchase
- Pauses, switches off, blocks and revokes at once
- Asks for anything else, and gets a link
Decides
- Going live, and the mapping agents see
- Live keys and webhook secrets, shown once, to you only
- Your team, payouts and terms
- Re-opening anything you paused or blocked
- Each link works once, for 30 minutes, for exactly what it shows
Then run it from the same place
$ npx @cerebro-one/connect readyAre you live? Answered from the same rules agents are checked against, with what's missing and who acts.
$ npx @cerebro-one/connect teamWho's in your organisation and who's invited. Changes are confirmed in the browser.
$ npx @cerebro-one/connect keysEvery key, when it was made and last used. A key's value is shown once, never again.
$ npx @cerebro-one/connect webhooksAdd, test and stop endpoints. A live endpoint's secret appears in your browser only.
$ npx @cerebro-one/connect terminalsThe terminals signed in as you. Sign one out, or all of them, at once.
$ npx @cerebro-one/connect askAnything only a person may do: going live, payouts, the team. You get a link to confirm.
One Cerebro, three ways in
Connect every business you serve, at once
A booking or ticketing platform connects once. It can then make the businesses and offerings it supports available to agents, with individual controls for what is enabled.
- Your format, read as it isCerebro maps your data and asks only what it can't tell
- Per business, per offeringSwitch any of them on or off for agents
- Changes caughtWhen your data changes shape, what no longer fits is held back
- Your checkoutPayment links only to the hosts you approve
What you offer, reachable by AI agents
A shop, a salon, a venue, an app for song requests or custom orders. Your own software keeps running the way it does today.
- Your rulesWho can buy, and what an agent must show first
- Your system confirmsEvery sale is made by your system, once
- Requests with answersQuestions you need answered, amounts within your limits
- Tested before liveA test agent runs a whole purchase against your test system
Let your agent find, ask and buy
Your own agent, a developer's, or an agent company's product connects over MCP or HTTPS and gets one interface, whoever is on the other side.
- Prices before purchasesA quote fixed until it expires
- Retries that never buy twiceThe same key returns the same sale
- Holds that lapse by themselvesNothing stays blocked by accident
- Credentials and customer permissions stay out of the modelKeys, customer tokens and buyers' authorizations go through your server, never through what the model can use
However something is sold, agents can buy it
Ticket types and seats, a chosen person, prices that change by the hour, a request with an amount the buyer sets, goods that ship. Each works the way its seller already sells it.
Seats, ticket types, add-ons
A seat for every ticket, extras with stock, the venue's own price with fees and tax, in one order.
A chosen person, at a chosen time
Who is free when, priced by their level. Two buyers for the same slot: exactly one gets it.
Priced by the hour
Courts, tables and rooms in parallel, each slot with its own price.
The buyer sets the amount
A song request, a dedication, a custom order: the answers the seller needs, and an amount within its limits.
Goods that ship
Shipping priced from the address, followed to the door.
Examples, not categories to fit into. Each runs on its own demo system, built separately against the public SDK and tested through the full transaction, including two buyers racing for the last one.
One interface, whoever is on the other side
MCP or HTTPS, one format. The person sees the seller's exact total before anything is bought.
What every agent gets
- The price before the purchaseA quote from the seller, fixed until it expires
- Holds that lapse on their ownNothing stays blocked by accident
- Retries that never buy twiceThe same idempotency key returns the same sale
- What's possible, on every resultHold, buy or check only, as the seller allows
What Cerebro does once it's in
Whether what you've built sells something or acts for people, Cerebro gives it a common way to exchange requests, information and actions with connected systems. Your existing product, customers and rules stay yours.
consumo_minimo→minimum spend · per tablesenal→deposit · 30% · upfrontestado: libre→availablemoneda?→asks you: EUR or USDUnderstands your system
Reads your data in your own format, works out what each field means, and asks you only what it can't tell. When your data changes shape, it notices and holds back what no longer fits until you approve again.
- your format
- plain-word questions
- you approve
Carries requests and answers, both ways
Each request goes to the system that can answer it, and each answer comes back: what's offered, what's free, the exact price, a hold, a confirmation, an outcome. One record of all of it.
- find
- price
- hold
- confirm
- record
Keeps your rules
Who can buy, what an agent must show before it commits, what's paused or switched off. Your prices, your checkout, your terms, applied on every request.
- who can buy
- your prices
- your checkout
From request to outcome
The seller's own system confirms, and payment happens on its own checkout.
Built for sales that have to be right
No duplicate orders
Every purchase uses an idempotency key. If a response is lost, retrying with the same key recovers the original sale instead of creating another.
Your rules, on every request
Allow or block agents, switch off a venue or an offering, pause at any time, and say what an agent must show before it commits.
The agreed price
The buyer sees the total before committing, priced by the seller's system or from its own prices; a confirmation that contradicts it goes to review. Payment happens on the seller's own checkout.
Every sale traceable
Every change to a sale is an event on record, and the ledger of fees and the audit trail are append-only: nothing in them is edited or deleted.
No casual overrides
An uncertain outcome is settled on evidence, approved by two people.
If you'd rather write it yourself
import { Cerebro } from '@cerebro-one/connect'; import { shop } from './your-system.js'; // your own code export const connection = Cerebro.connect({ key: process.env.CEREBRO_KEY, // Every status and payment word your system uses, in your own words. statuses: ['retenida', 'confirmada', 'pendiente', 'cancelada', 'asistio', 'no_vino', 'pagado', 'sin_pagar'], checkoutDomains: ['pay.yourshop.com'], // where your checkout pages live offerings: () => shop.listAll(), // required: everything you sell, as you store it availability: (id, query) => shop.free(id, query), // what's free between query.from and query.to hold: (id, order) => shop.hold(id, order), // optional: { ref, expires_at } release: (ref) => shop.unhold(ref), // optional: frees a hold early confirm: (id, order) => shop.sell(id, order), // { ref, status, checkout?: { url, amount, currency, expires_at } } checkout: (ref) => shop.newPaymentPage(ref), // optional: a fresh page for the same order cancel: (ref) => shop.cancel(ref), // optional: under your own terms status: (ref) => shop.status(ref), // optional: { status, payment? } in your words }); const { level, can } = await connection.ready; console.log(`Connected at level ${level}: ${can.join(', ')}`);
Install the SDK
Your coding agent does it, or you do. The seller SDK runs next to your database and only calls out to Cerebro: no new API, no open ports.
npm install @cerebro-one/connectApprove your mapping
Cerebro reads your data as it is and asks only what it can't tell. Nothing goes live until you approve it.
Go live
Agents you allow find, quote and buy. Your system confirms each sale, under your terms.
One fee, only when you sell.
1% of each completed sale. At least $0.50, never more than 3% of the sale. At most $25.
Everything else costs nothing
- Connecting your system
- Searches and availability
- Holds
- Testing
- A sale that is cancelled, declined or refunded in full
Free for agents
An agent pays nothing to find, hold and buy. The seller pays the fee, on the sales that complete.
Your terms change only if you accept new ones
You read your fee terms in full and confirm them yourself. A change is a new version you accept, never an edit.
In other currencies the minimum and maximum are the equivalent amounts, written into your terms when you accept them, so they don't move with exchange rates. After a partial refund the fee is worked out again on what was kept.
Questions from people connecting
For anyone selling, and the platforms behind them
Who can connect?
Anything that sells, and anything that buys. A platform for many businesses, a business's own site or software, an app (a song request, a dedication, a custom order), and any AI agent: your own, a developer's or an agent company's. Selling systems connect with Cerebro's SDK, set up by a developer or a coding agent; agents connect over MCP or HTTPS. A business that sells through a provider's software reaches agents through that provider.
Is Cerebro a marketplace?
No. There is no Cerebro storefront or directory for people to browse. Cerebro keeps an index of what you offer only so the agents you allow can find it, at your prices, on your checkout, under your rules. Your customers stay yours.
Do we need a public API?
No. The SDK runs in your backend and connects to your existing functions, calling out to Cerebro; nothing new is exposed. A developer or a coding agent sets it up. A business that sells through a provider's software is reached through that provider.
Do we have to change our data model?
No. Return your data as it is, and approve how it looks to agents before anything goes live.
What happens when our format changes?
Cerebro notices answers that no longer match what you approved and holds those offerings back until you confirm the new format.
Who handles payment and cancellations?
You do, as today: payment on your own checkout page, cancellations under your own terms.
Which agents can buy from us?
The ones you allow. You can block an agent, limit agents to the ones you choose, or pause your connection at any time.
Do the businesses on our platform have to sign up?
No. You decide distribution, as with any channel. Leave a business out, and agents never see it.
For agent builders
What can agents do through Cerebro?
Discover offerings, check availability, get prices, place holds and make purchases across connected sellers.
How do agents connect?
Through one API or MCP interface, with the same transaction capabilities across connected sellers.
Who controls prices and availability?
Each seller does. Cerebro returns the information and permissions the seller provides, as it provides them.
Who confirms a purchase?
The seller's own system confirms it, and stays responsible for its inventory, terms and fulfilment.
Can we test before going live?
Yes. The sandbox runs discovery and complete purchases against test sellers before you have production access.
Can one person connect their own agent?
Yes. An agent you built for yourself connects the same way as an agent company's: one API or MCP. Going live is checked for a person as for a company, starting with smaller limits.
Talk to us
Cerebro is in private beta. Tell us what you built, whether it sells or buys, and we'll reply by email.