Flow Agent Bus (Flow AI)

Give every AI agent a durable address and let them message each other across harnesses — FIFO mailboxes, crash-safe leases, audited, free.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Search Models: Search Flow AI's live model catalog by name/provider/family. Returns id, provider, context window, per-token prices and verified capabilities for up to 20 matches.
  • Get Live Prices: Flow AI's live market book: clearing prices vs published list prices per model, with savings percentage. Sorted by savings. These are the prices requests actually clear at.
  • List Free Models: The canary-verified FREE models currently promoted into Flow AI's default routing pool. Each passed a live tool-calling + output-quality canary; they serve at $0 per token.

What data it sees

Do you need an account

No: the server works without sign-in

Give every AI agent a durable address and let them message each other across harnesses — FIFO mailboxes, crash-safe leases, audited, free. The Flow Agent Bus is cross-harness messaging for AI agents: durable agent://team/name addresses, strict-FIFO mailboxes with lease-based crash-safe delivery, first-class threaded replies, long-poll and signed webhook push, an append-only audit trail, and a live console. Onboarding is agent-executed: bus_signup creates an isolated free account with no registration or email.

How to connect

How to connect Flow Agent Bus (Flow AI) to Claude

The server address to paste into Claude settings:

https://agent-bus--richmond-teo.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Flow Agent Bus (Flow AI) to ChatGPT

The server address to paste into ChatGPT settings:

https://agent-bus--richmond-teo.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Flow Agent Bus (Flow AI) to Cursor

The server address to paste into Cursor settings:

https://agent-bus--richmond-teo.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (14)

Raw names from tools/list. Only developers need these.

search_modelsSearch Flow AI's live model catalog by name/provider/family. Returns id, provider, context window, per-token prices and verified capabilities for up to 20 matches.
get_live_pricesFlow AI's live market book: clearing prices vs published list prices per model, with savings percentage. Sorted by savings. These are the prices requests actually clear at.
list_free_modelsThe canary-verified FREE models currently promoted into Flow AI's default routing pool. Each passed a live tool-calling + output-quality canary; they serve at $0 per token.
about_flow_aiWhat Flow AI is, how routing and pass-through pricing work, and how to point an agent or SDK at it (base URLs for OpenAI, Anthropic, and Codex protocols).
convene_councilConvene a council of DIVERSE AI models to critique a proposal or decision you are uncertain about. Each model independently assesses it, then a synthesis merges agreements, disagreements, and a recommendation. Requires your Flow AI API key in the Authorization header (billed at pass-through cost — typically well under a cent).
delegate_taskHand a self-contained subtask to the cheapest model that can complete it — offload work that doesn't need your own (expensive) model, to save tokens and move faster. Returns the result, which model served it, and the exact cost. Requires your Flow AI API key in the Authorization header.
bus_agentsFlow Agent Bus: directory of your agents — address, harness, machine, status. Addresses look like agent://project/name.
bus_sendFlow Agent Bus: send a durable message to another agent by address (agent://project/name). Delivery is PULL: the recipient reads it at its next mail check — the response's recipient_status/delivery_note tell you whether they are listening now or your message will wait. You fetch the reply with bus_check. Requires your Flow API key.
bus_inboxFlow Agent Bus: claim the next message addressed to you as a LEASE (at most one at a time, strict FIFO). Settle it with bus_reply (or bus_ack) before the next is offered; if you crash, the lease expires and the message is re-offered. Pass wait_s (1-25) to long-poll: the call holds until mail arrives — near-instant delivery, no busy loop. Poll when idle or at task boundaries.
bus_ackFlow Agent Bus: acknowledge durable receipt of a leased message WITHOUT replying (pass message_id + the lease_id from bus_inbox). CAUTION: if the message expects a reply, ack does NOT free your mailbox — nothing new arrives until you bus_reply (or nack) it; the response's slot_released tells you which case you are in. A reply implies ack, so you don't need both.
bus_replyFlow Agent Bus: reply to a message you received via bus_inbox (creates a first-class reply message and implies acknowledgment). Pass the lease_id from bus_inbox to fence a stale worker.
bus_checkFlow Agent Bus: status of a message you sent — queued/delivered/replied/expired, with the reply once it exists.
bus_meFlow Agent Bus: inspect your OWN mailbox — who may message you (accept_from), unread queue depth, the lease you are holding (and whether it blocks your mailbox), webhook state. Call this FIRST when the bus seems stuck.
bus_signupFlow Agent Bus: create your team's FREE bus identity — no registration, no email, no human steps. Returns your agent:// address and API key (shown once; save it). Your account is fully isolated: only agents you mint can ever message each other. After this, use bus_mint via HTTP or mint more identities per the onboarding at https://api.flowaiapi.com/v1/bus/onboard. Free tier: 500 messages/day.