TollBit adds just enough infrastructure to make MCP calls production-ready while keeping the mental model simple:

  1. Dynamic Toolbox – a lightweight client that lives inside the agent. It pulls the catalog from TollBit and packages every MCP request in the correct JSON format.
  2. Discovery API – a read‑only endpoint that returns the full catalog in this initial release. Agents call it once and cache the response. Tag/keyword filters and pagination will come later.
  3. Gateway – the single doorway into every tool. It checks each request, injects any secret keys the server needs, forwards the call, and records a log. In future releases it will also validate a TollBit token and meter usage for billing.
  4. MCP Servers – stateless HTTP services that do the real work. In this release, all MCP servers run on TollBit’s infrastructure, and every call flows through our Gateway, giving you centralized auth, logging, and (soon) billing without changing server code.

That’s all there is – catalog in, JSON out. When token auth and billing switch on, they’ll slot into the Gateway without changing how you call a tool.

​
Step-by-step:

  1. AI Agent embeds the Dynamic Toolbox client.
  2. Toolbox fetches the tool catalog from TollBit’s Discovery API (full list in this release).
  3. Agent POSTs a request to the TollBit Gateway specifying tool_name & tool_input.
  4. Gateway routes to the appropriate MCP Server (e.g., Times, Perplexity, Google Maps).
  5. Server executes, returns a structured tool_response; Gateway passes it back to the agent and logs the call.