cerebro.
Private betaTalk to us →

Add Cerebro to what you've built.

Connect what you sell to AI agents and every platform people buy through: assistants, messaging, voice, cars. One connection.

~/noche — cerebro setup
cerebro.one
  1. Sign in
  2. Organisation
  3. Connect
  4. Mapping
  5. Test purchase
  6. Go live

The real output of setup against a demo nightlife platform, abridged. Hover to pause.

Demonstrated
Cinema seatsEvent ticketsSalon appointmentsPadel courtsTee timesClub tablesProductsShippingSong requestsDedications
Platforms

Connect once. Be everywhere people ask.

An assistant, a messaging app, a speaker, a car, glasses, a watch, an app someone else built: each is a platform people buy through. Cerebro connects what you sell to all of them, and every request lands in the same place: your system, live.

Storefronts: where your businesses can be

One connection. Each new storefront reaches every business you serve, with no work on your side.

1MessagingOpening

WhatsApp. People text a number and buy in the conversation.

  • A link and QR for each businessOpens the chat with the business already named
  • Cerebro runs the conversationLive availability, the exact price, the order
  • The sale lands in your systemSame calendar, same checkout, no double bookings
  • Our fee per sale, nothing elseNo setup, no monthly charge

Later in messaging: iMessage, Instagram.

2AI agentsPrivate beta

Any agent over MCP or HTTPS finds, holds and buys.

Agents people build for themselves, and agent companies' products.

3Voice and homeNext

Home assistants and speakers.

As they open to buying by voice.

4DevicesLater

Glasses, watches, cars.

Wherever people ask next.

Built for what you've built

One Cerebro, three ways in

Platforms

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
Your own business or app

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
Agents

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, which customer a request is for and buyers' authorizations go through your server, never through what the model can use
Commerce

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.

Tickets

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.

10:00 · senior · paid on site
Appointments

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.

€32 day€48 peak
Capacity

Priced by the hour

Courts, tables and rooms in parallel, each slot with its own price.

Requests

The buyer sets the amount

A song request, a dedication, a custom order: the answers the seller needs, and an amount within its limits.

Commerce

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.

For agents

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
agent · conversationExample
Two adults and a child for Dune on Saturday evening, seats together, and a large popcorn.
find Dune · London · Sat · 3→ 19:30 · seats F6–F8 free
quote 2 × Adult, 1 × Child, popcorn, F6 F7 F8→ priced by the cinema · valid 10 min
Three seats together in row F, 19:30.
2 × Adult · 1 × Child£38.50
Large popcorn£6.50
Fees and VAT£4.50
Total£49.50
Go ahead.
confirm quote · Kim Taylor→ confirmed by the cinema · pay on its page
Once it's in

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 table
senal→deposit · 30% · upfront
estado: libre→available
moneda?→asks you: EUR or USD
01

Understands 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
agentseller
02

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
AgentsChosen only
Club Uno
Sala Mar
Paused
03

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.

agent → sellerFindWhat fits, across connected systems
seller → agentAvailabilityLive, from the seller's own system
seller → agentQuoteThe seller's exact price, before anyone commits
agent → sellerHoldReserved for a few minutes, where the seller can
seller → agentConfirmationMade by the seller's system, once
agent → buyerPaymentOn the seller's own checkout
seller → agentFulfilmentShipped, attended or delivered, reported back

Built for sales that have to be right

01

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.

02

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.

03

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.

04

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.

05

No casual overrides

An uncertain outcome is settled on evidence, approved by two people.

Developers

If you'd rather write it yourself

your-platform / src / cerebro.ts
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(', ')}`);
01

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/connect
02

Approve your mapping

Cerebro reads your data as it is and asks only what it can't tell. Nothing goes live until you approve it.

03

Go live

Agents you allow find, quote and buy. Your system confirms each sale, under your terms.

Read the docs →
Why connect

What each side gets

an assistanta travel agenta shopping agentthe next oneyour system
You sell

For sellers

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 reaches every agent and platform
  • Every sale is made by your system, at your price
  • You decide which agents may buy
ticketstablesappointmentsstaysyour agent
You build an agent

For agents

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.

  • One interface, over MCP or HTTPS
  • Live availability and the seller's exact price
  • Held or bought while your user is still there
Cost

Sellers pay only when they sell

Connecting, searches, availability, holds and testing cost nothing. Neither does a sale that is cancelled, declined or refunded in full.

Agents

Free for agents

An agent pays nothing to find, hold and buy.

Terms

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.

Questions

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.

You're connecting
We reply from partner@cerebro.one.