Platform

SynthBoard on your stack.
Same experts, same memory.

Run the same rooms from your IDE, your agent or your own code. The same experts, what she keeps, and the same card with its price before anything runs — on every plan.

Start free Read the API docs

Free to start. No card.

Claude Desktop config

One server, one keyMCP

{
  "mcpServers": {
    "synthboard": {
      "url": "https://synthboard.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer sb_live_…"
      }
    }
  }
}

Cursor, Windsurf and any MCP client take the same URL and key.

Three ways in

An API, an MCP server,
and signed webhooks.

Each one reaches the same rooms as the app, under the same rules: a person approves the plan, the card shows its price, and nothing writes to a tool without a confirm.

REST API

46 endpoints: sessions, consults, the catalog, shares, integrations and webhooks. OpenAPI 3.1 at /api/v1/openapi.json. Bearer sb_live_ keys with per-key scopes, an IP allowlist and a daily spend cap.

API reference

Plan, then startREST

# 1 · plan it: who sits, and the card's "up to" price
curl https://synthboard.ai/api/v1/sessions/plan \
  -H "Authorization: Bearer sb_live_…" \
  -H "Content-Type: application/json" \
  -d '{"question": "Raise prices now, or in January?"}'

# 2 · start it, once a person approves the plan
curl https://synthboard.ai/api/v1/sessions \
  -H "Authorization: Bearer sb_live_…" \
  -H "Content-Type: application/json" \
  -d '{"plan_id": "<from step 1>"}'

MCP server — 44 tools

Plan, start and read a board or a consult from Claude, Cursor or any MCP client. A Bearer key, or OAuth 2.1 for clients in a browser. Bare questions are planned first, so nothing starts until a person approves.

MCP docs

A few of the toolsMCP

synthboard.session.plan        plan a board or a consult
synthboard.session.start       start it once you approve
synthboard.consult.message     a follow-up question
synthboard.world_model.search  search what she keeps
synthboard.session.get         read the memo
synthboard.session.share       a read-only link to it

Signed webhooks

Subscribe to 6 session events — a run completed, failed, cancelled and more — with a signing secret per endpoint. Built for n8n, Zapier, Pipedream and Make.

Webhook docs

One delivery, and how to check itHMAC-SHA256

POST https://your.app/hooks/synthboard
X-SynthBoard-Event: session.complete
X-SynthBoard-Timestamp: 1759312800
X-SynthBoard-Signature: sha256=9f2c…

// verify (Node)
const mac = createHmac('sha256', secret)
  .update(`${timestamp}.${rawBody}`)
  .digest('hex');
const ok = timingSafeEqual(
  Buffer.from(mac), Buffer.from(signature.slice(7)));

The tools she reads

The same connections the app uses, read-only until you allow writing; every write is a preview you confirm, on Pro and above.

Every tool

Governance by default

Code gets the same rules
a person does.

What a call cannot do

Nothing runs on its own.

A bare question cannot start a room; it is planned, and a person approves the plan.
Nothing writes to your tools until someone confirms the preview.
A board never bills above its card.
Every tool call leaves an audit record.

Keys and limits

On every plan.

Compare what each plan includes on pricing.

API and MCP access on every plan, Free included.
sb_live_ keys with per-key scopes, an IP allowlist and a daily spend cap.
The API and MCP call log is kept for 12 months, visible under Developers → Usage.

Under the seats

One room,
several model families.

Seats are spread across model families, so the room is not one lab’s habits.

GPT
Claude
Gemini
Grok

Each expert researches alone, then reacts once to the others — on a model that is not everyone else’s.

Questions

Fair questions.
Straight answers.

What developers ask before they wire it in.

Or read the MCP guide · webhooks · get in touch

Which plans include the API and MCP?

Every plan, Free included. Generate a key in the MCP Control Center and call /api/v1/health with it; a 200 means you are in.

How do I authenticate?

With a Bearer sb_live_ key, scoped per key, with an optional IP allowlist and a daily spend cap. Browser-embedded MCP clients use OAuth 2.1 instead.

Can my code start a board from a bare question?

No. A bare question goes through synthboard.session.plan first, so a person approves who sits and the price before anything runs.

Does a run from code cost the same as one in the app?

Yes. The same card and the same credits: the plan comes back with its one “up to” number before anything starts. A board never bills above its card.

How are webhooks signed?

With HMAC-SHA256 over the timestamp and the raw body, using a secret per endpoint, in the X-SynthBoard-Signature header. The event name and the timestamp travel in their own headers.

What is logged when my code calls SynthBoard?

The API and MCP call log keeps the tool name, PII-scrubbed parameters, status, correlation id and caller IP for 12 months, as the security audit trail for programmatic access. You can see it under Developers → Usage.