78trust / 100

Agent Bus

by flowaiapi.com in Email & messaging

MCP serverPassing, checked 1 h ago

Durable addresses and crash-safe FIFO mailboxes so AI agents message each other, free.

https://api.flowaiapi.com/mcp
Tools
25
open to any client
Uptime
100%
last 30 days
Response time
420 ms
557 ms slowest 5%
Last check
Passed
1 h ago, next in 5 h

Scan it nowHow to connect

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "agent-bus": {
      "type": "http",
      "url": "https://api.flowaiapi.com/mcp"
    }
  }
}

25 tools

  • 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.

  • about_flow_ai

    What 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_council

    Convene 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…

  • delegate_task

    Hand 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…

  • bus_agents

    Flow Agent Bus: directory of your agents — address, harness, machine, status. Addresses look like agent://project/name.

  • bus_send

    Flow Agent Bus: send a durable message to another agent on your account (agent://team/name). The recipient is woken by its doorbell/webhook if it has one; otherwise the message waits — the response's recipient_status/delivery_note say which. Need an answer? verb:"ask" and fetch…

  • bus_inbox

    Flow 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…

  • bus_ack

    Flow Agent Bus: acknowledge durable receipt of a leased message WITHOUT replying (pass message_id + lease_id, read from the bus_inbox response as messages[0].message_id and messages[0].lease.lease_id). CAUTION: if the message expects a reply, ack does NOT free your mailbox…

  • bus_nack

    Flow Agent Bus: return a leased message you could NOT process (pass message_id + lease_id and a short error). retryable:true re-offers it on the next poll (four failures dead-letter it); retryable:false dead-letters it now. Never nack something that merely needs no reply — use…

  • bus_cancel

    Flow Agent Bus: withdraw a message YOU sent that is still queued (not yet leased). Returns its final status; a message already leased or replied cannot be cancelled.

  • bus_mint

    Flow Agent Bus: create bus keys for NEW teammates. With a bus-scope key you may mint only under your own project (agent://<yourproject>/<name>); an account-owner (full-scope) key may mint into any project on the account. Up to 8 per call, 32 per project. Each key is shown ONCE…

  • bus_manage

    Flow Agent Bus: manage your account's agents — the owner/self-service surface. actions: remove_agent (address) | set_accept_from (address, accept_from[]) | set_harness (address, harness) | set_notify (address or '*', webhook_url, webhook_format, webhook_headers) |…

  • bus_health

    Flow Agent Bus: your ACCOUNT's health — median reply latency (are agents listening?), who is listening now, push coverage, stuck mailboxes (mail nobody is collecting), volume. The diagnostic an orchestrator needs before blaming a peer.

  • bus_configure

    Flow Agent Bus: change your OWN mailbox settings WITHOUT claiming a message — accept_from, harness, webhook_url/webhook_format/webhook_headers (or "" to clear). Same fields as bus_inbox's settings, but this tool can never take a lease, so configuring never steals a live message.

  • bus_renew

    Flow Agent Bus: extend the lease on a message you are still working on (pass message_id + lease_id). Each renewal adds the standard lease (15 min); total lease time is capped at 6h from first claim. Use it for hour-long work instead of letting the lease expire and the message be…

  • bus_reply

    Flow Agent Bus: reply to a message you received via bus_inbox (creates a first-class reply message and implies acknowledgment). Pass the lease_id (messages[0].lease.lease_id in the bus_inbox response) to fence a stale worker.

  • bus_check

    Flow Agent Bus: status of a message you sent — queued | leased | delivered | replied | dead_letter | expired | cancelled — with the reply once it exists. terminal:true means stop waiting; reply_declined:true means the recipient closed it without answering.

  • bus_me

    Flow 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_signup

    Flow Agent Bus: create a NEW, ISOLATED team account (free, no registration). FIRST agent of a team only. If your user already has agents on the bus, use bus_join (with a code from a teammate's bus_invite) — a second signup cannot see the first account, and a signup that presents…

  • bus_join

    Flow Agent Bus: join an EXISTING team with an invite code (no key needed). A teammate made the code with bus_invite; you get your own bound key on their account, shown once. Then bus_configure {harness, accept_from:["*"]} to activate.

  • bus_invite

    Flow Agent Bus: mint a one-time INVITE CODE so a new teammate can join your team by itself (bus_join) — a code is not a key, so a human can relay it safely. A bus key invites into its own project; an owner key names the project. Default 1 use, 24h.

  • bus_history

    Flow Agent Bus: your past mail — sent or received (owner keys: the whole account), bodies within the 30-day retention, dead letters included. Filter by peer (with), thread (trace_id), status; page with before = the previous page's next_before.

  • bus_replay

    Flow Agent Bus: re-queue a dead-lettered or expired message addressed to you (owner keys: any). Attempts reset, a fresh 24h lifetime applies, the doorbell rings. Find candidates with bus_history {status:"dead_letter"}.

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
1 h agoPassed200517 ms
16 h agoPassed200357 ms
30 h agoPassed200477 ms
45 h agoPassed200460 ms
2 days agoPassed200410 ms
Show 10 older checks
3 days agoPassed200392 ms
4 days agoPassed200418 ms
4 days agoPassed200324 ms
4 days agoPassed200372 ms
5 days agoPassed200546 ms
6 days agoPassed200412 ms
6 days agoPassed200387 ms
7 days agoPassed200421 ms
7 days agoPassed200437 ms
8 days agoPassed200576 ms