Engineering
Add an API once as a shared plugin, not in one bot's chat
Every bot reinvents the same API connection, each with its own secrets.
What hurt
Paul (@PaulShipsAI) gave a five-step answer on connecting an API to a fleet of bots. Not affiliated with xAI.
What to install or create
Check whether a shared plugin already exists; if not, add it once as a shared plugin or MCP; connect the account and secrets there; tell the fleet to use it rather than reinvent it; and require a human OK before paid API spend.
Bots
Fleet
Uses the shared plugin instead of its own connection.
Plugins
None on day one. Follow the first-run steps.
Routines
None on the first run. Watch one manual pass first.
The prompt
His five steps (author-quoted)
Quoted from @PaulShipsAI — as published. Do not invent a second system prompt.
1. Check if a shared plugin for that API already exists 2. If not → add it once as a shared plugin/MCP (not in one bot’s chat) 3. Connect the account / secrets there 4. Tell the fleet: use this plugin, don’t reinvent it 5. Paid APIs → human OK before spend
First run
- 1Read https://x.com/PaulShipsAI/status/2108456937557762345 (credit @PaulShipsAI).
- 2Check the plugin list for an existing shared connection.
- 3If none, add the API once as a shared plugin/MCP and connect secrets there.
- 4Tell every bot to use that plugin.
- 5Add an approval rule before any paid API spend.
Approval fence
Paid APIs need your OK before spend.
What to tweak
One connection, one place for secrets, one instruction to the fleet.
Source
Paul @PaulShipsAI · Original post
Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.
Pro pack
Want the full setup, not just the idea?
Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.