deployed an Eve agent Friday, woke up Monday to a $3,200 Stripe dispute. the agent looped on one task for 48 hours.
eve-floe is open-source template that wires an Eve agent to Floe so its spending is governed.
what it does
- hard cap (server-side): every vendor API payment is checked against your budget before it settles over-budget calls are refused, so a runaway loop stops at the cap instead of your invoice.
- per-subagent budgets: the template has a lead agent + a fetcher subagent, each with its own Floe key and cap (a subagent can’t drain the whole budget).
- budget-aware tapering: a skill lets the agent read its remaining budget and downshift (fewer/cheaper fetches) as it nears the cap, so it finishes useful work instead of being cut off.
- one secret: each agent holds a single Floe key…never a provider or vendor key.
complementary to AI Gateway, by design. Floe governs the vendor/API plane (what your agent pays: 2,000+ x402 APIs); Vercel AI Gateway governs the model plane. Use both for complete agent spend control. (eve-floe doesn’t touch your model spend.)
two-step setup for your own agent: drop in agent/connections/floe.ts and set FLOE_AGENT_KEY. Full template + docs in the repo.
- Repo: GitHub - Floe-Labs/eve-floe: Spend controls for Vercel Eve agents — hard budget caps + budget-aware tapering via Floe (template + MCP connection). · GitHub
- Get a key & set a cap: Floe — Developer Console
please break and give feedback 