Skip to main content
Connect Zero when agents need capabilities outside their native tools — image generation, transcription, real-world data lookups, and other paid APIs — using a Zero wallet connected once for the deployment.

​
When to use it

  • give agents a free capability search path when they hit something they cannot do natively
  • fund paid external capability calls from a workspace-connected Zero wallet
  • keep wallet custody and funding on the Zero side instead of Roomote billing

​
How setup works

  1. An admin enables Zero from Settings > Integrations.
  2. That admin connects Zero once for the workspace via OAuth.
When Zero is enabled for the deployment, Roomote installs the zero CLI for matching tasks and activates the packaged Zero skill. Completing the org OAuth connection lets agents authenticate through the MCP connector and run the capability loop with shell commands.

​
What to expect

  • Search is free. Agents can discover services without spending.
  • Paid fetches use the workspace wallet. Roomote does not front a shared platform wallet for Zero.
  • CLI-first loop. Preferred commands are zero search, zero get, zero fetch, and zero review. Treat --max-pay as required for unfamiliar paid calls.
  • Auth and funding helpers. The Zero MCP connection is for authentication and funding; the CLI owns discovery and paid calls.

​
Practical tips

  • Connect Zero with an account appropriate for shared agent spend, then fund the wallet from the Zero profile page when a call needs balance.
  • Ask Roomote to search Zero for a concrete capability before expecting a paid fetch.
  • Review spend and balances in Zero’s own product surfaces; Roomote does not meter Zero spend into product billing.