Cerebro connects businesses, platforms, software and AI agents, giving them a common way to exchange information, take action and transact through the systems they already use.
The real output of setup against a demo nightlife platform, abridged. Hover to pause.
cerebro --what-do-you-power
Every agent, platform or application you want to work with usually means another integration to build and maintain. Cerebro is one common layer instead: connect what you already run once, and exchange information, requests and actions with the systems connected to it. Each keeps its own data, customers, rules and workflows.
cerebro powers connections between ├─ businessestheir own systems, sites and software ├─ platformsand every business they serve, through one connection ├─ softwareapplications that provide a capability, or use one └─ ai agentsyour own, a developer's, or an agent company's ✓ one installation ✓ your rules ✓ your system stays the source of truth
cerebro interfaces
An assistant, a messaging app, a speaker, a car, glasses, an app someone else built: each is a way people reach a business. Connected through Cerebro, every request from any of them lands in the same place: your system, live, under your rules.
The same running shoes as last time, size 43.ordered · delivery tomorrow
Tee time for four on Saturday morning, near Sotogrande.confirmed · Sat 09:10
A VIP table for eight tonight, upstairs if possible.confirmed · table 12 · floor 2
Two early-bird tickets for Saturday's closing party.confirmed · €15 each
Half-day boat for six tomorrow, with a skipper.held · 10:00 · deposit 50%
Sunset kayak tour for two on Friday.confirmed · Fri 19:30
Team dinner for twelve next Thursday, private room.sent to the venue · confirms in minutes
Is there a padel court free near me in an hour?held · court 3 · 18:30
One connection. Each new interface reaches every business you serve, with no work on your side.
Later in messaging: iMessage, Instagram.
Agents people build for themselves, and agent companies' products.
As they open to buying by voice.
Wherever people ask next.
cerebro connect --as platform|business|agent
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.
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 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.
cerebro sell --anything
Cerebro's first capabilities are commercial: discovery, live availability, prices, holds and transactions. 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.
A seat for every ticket, extras with stock, the venue's own price with fees and tax, in one order.
Who is free when, priced by their level. Two buyers for the same slot: exactly one gets it.
Courts, tables and rooms in parallel, each slot with its own price.
A song request, a dedication, a custom order: the answers the seller needs, and an amount within its limits.
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.
cerebro agents --interface
MCP or HTTPS, one format. The person sees the seller's exact total before anything is bought.
cerebro explain --flow
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 USDReads 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.
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.
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.
The seller's own system confirms, and payment happens on its own checkout.
Every purchase uses an idempotency key. If a response is lost, retrying with the same key recovers the original sale instead of creating another.
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 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 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.
An uncertain outcome is settled on evidence, approved by two people.
npm install @cerebro-one/connect
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(', ')}`);
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/connectCerebro reads your data as it is and asks only what it can't tell. Nothing goes live until you approve it.
Agents you allow find, quote and buy. Your system confirms each sale, under your terms.
cerebro terms --summary
Connect once. Every agent and platform on Cerebro can then find, hold and buy what you sell, in your own system, under your own rules. Each one that joins is new reach you didn't have to build.
One connection to everything sellers have connected. Your user asks, and it is held or bought in seconds: no scraping, no forms, no checking back later.
Connecting, searches, availability, holds and testing cost nothing. Neither does a sale that is cancelled, declined or refunded in full.
An agent pays nothing to find, hold and buy.
You read your fee terms in full and confirm them yourself. A change is a new version you accept, never an edit.
cerebro help
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.
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.
No. Return your data as it is, and approve how it looks to agents before anything goes live.
Cerebro notices answers that no longer match what you approved and holds those offerings back until you confirm the new format.
You do, as today: payment on your own checkout page, cancellations under your own terms.
The ones you allow. You can block an agent, limit agents to the ones you choose, or pause your connection at any time.
No. You decide distribution, as with any channel. Leave a business out, and agents never see it.
Discover offerings, check availability, get prices, place holds and make purchases across connected sellers.
Through one API or MCP interface, with the same transaction capabilities across connected sellers.
Each seller does. Cerebro returns the information and permissions the seller provides, as it provides them.
The seller's own system confirms it, and stays responsible for its inventory, terms and fulfilment.
Yes. The sandbox runs discovery and complete purchases against test sellers before you have production access.
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.
Cerebro is in private beta. Tell us what you built, whether it sells or buys, and we'll reply by email.