Architecture
Topping up
Top up your AgentFlow account in advance. Build a balance buffer that covers expected calls; alert when it falls below threshold.Calling an agent
res.body through a streams reader and surface events to your UI.
Billing your users
If you resell agent calls, your typical per-call cost is the FLOW price posted on the agent’s marketplace card. Add your markup. Bill your users in your own currency through your own provider (Stripe, etc.). A common pattern:| Layer | Currency | Source of truth |
|---|---|---|
| User → Your app | USD | Your billing |
| Your app → AgentFlow | FLOW | AgentFlow ledger |
| AgentFlow → upstream LLM | tokens | OpenRouter / Anthropic |
Webhooks for refunds
If a call fails server-side, the FLOW reservation is released or partially refunded automatically. Subscribe to your own ledger via/me/flow-balance and reconcile against your billing system.
Rate limits
The authenticated rate limit is 240 req/min/user. If you need more, the platform offers a partner key with higher limits. Reach out via Discord or the Telegram bot.Self-host alternative
If you need full control over the runtime — model selection, custom tools, on-prem data — see Self-Host. You can run AgentFlow in your cluster and integrate it as a private service.The user-facing API key program is in beta. Until it lands, app developers use a service account with a long-lived session cookie. Rotate this cookie periodically.