Know what your voice agents
truly cost.
Your voice agent's whole bill on one ledger. Inside Vapi, Retell, LiveKit, Pipecat & Bland, or fully BYOK.
Your voice agent's whole bill on one ledger. Inside Vapi, Retell, LiveKit, Pipecat & Bland, or fully BYOK.
Your voice agent's whole bill on one ledger. Inside Vapi, Retell, LiveKit, Pipecat & Bland, or fully BYOK.
Read https://dev-dashboard.floelabs.xyz/agents.md and set up Floe for this project.Read https://dev-dashboard.floelabs.xyz/agents.md and set up Floe for this project.https://dev-dashboard.floelabs.xyz/
Read https://dev-dashboard.floelabs.xyz/agents.md and set up Floe for this project.
Start with the guardrail. No account.
floe-guard hard-stops a runaway agent before it burns your bill. Local, framework-agnostic, MIT.
Running voice agents on Vapi, Retell, Bland, LiveKit or Pipecat?
15 minutes with the founders.
Running production agents on Vapi, Retell, Bland, LiveKit or Pipecat?
15 minutes with the founders.
Every leg of the call. One key. One ledger.
A voice call spends across 7–20 vendors. Floe meters and caps all of them — keyless on the gateway catalog, or BYOK with your own provider keys. These are the verified services live today; anything not listed is one submission away.
The BYOK metered proxy prices any model OpenAI or Anthropic ships — pass the model id, bring your key, get metering and a server-side cap. If a provider sells it and Floe can price it, it's callable.
Sarvam's Indic chat, STT (Saaras), and TTS (Bulbul) run on the same key and ledger as the rest of your stack — regional-language agents without a separate vendor relationship.
Every service here is metered against the same balance and policies. When the cap is hit, the call is refused before any upstream spend — that's the whole point.
"Token and TTS usage varies every call, so true per-call cost only exists by joining usage data across providers after the call. Floe gives us that in real time."
CEO
$5M ARR voice agency
1/4
"Floe solves one of the missing pieces that voice AI builders need to operate autonomously in the real world: multi vendor billing and secure spending governance."
Ratikesh
Voice AI Developer at Pharma Company
2/4
"Shoutout to [Floe] app because cost tracking is HARD"
Naomi Carrigan
DevRel / Community Lead at Deepgram
3/4
"The problem Floe's solving is real. We hear some version of it from every team managing multi-model, multi-vendor agent stacks."
Partnerships Team
Z.ai
4/4
Every model your agent needs — no per-provider accounts
Point your OpenAI-compatible SDK at Floe, pass your Floe key, and call models pay-as-you-go.
No. BYOK is live today: keep your own vendor accounts and keys — Floe meters, joins, and caps on top of them, and your platform spend flows onto the same ledger via end-of-call webhooks. Keyless — Floe fronts the vendor, one key, welcome credits — is the fast lane for prototypes and net-new agents.
Most production teams run BYOK; most prototypes start keyless. Switch anytime.
A voice call touches 7–20 vendors billing separately, and token and TTS usage varies every conversation — so true per-call cost only exists by joining usage data across providers after each call.
Floe does that join in real time and enforces budgets on top: caps rejected before money moves where Floe is in the path, and a circuit breaker that denies the next call everywhere else. One ledger: per-call, per-agent, per-vendor, per-customer.
Token routers meter your LLM spend — ~40% of a voice call's bill. The other ~60% — telephony, STT, TTS, search, memory — is spread across vendors they never see.
Floe meters the entire bill, enforces caps across all of it, and sits as the governance layer above your whole stack, token routers included.
Yes — through the platforms' own documented extension points, with zero platform cooperation. Point the custom-LLM slot at Floe for pre-call enforcement on ~60% of call cost; connect the end-of-call webhook and every call lands on one ledger with a between-call circuit breaker.
On BYOK, these platforms report provider costs as $0 — Floe is how you see and cap that spend anyway.
No — by design. A dropped call is a worse failure than an expensive one. Enforcement is pre-call admission: where Floe is in the path (LLM, STT, TTS, Floe Phone), an over-budget call is denied before it starts. Where it isn't, Reconcile Mode meters the cost at call-end and the circuit breaker denies the next call.
Your coverage score shows exactly which of your spend sits in which bucket.
A per-agent number in your dashboard: the % of that agent's spend that is pre-call enforceable vs post-call reconciled vs dark — across every platform it runs on. No single platform can compute this about itself, because no platform sees spend outside its own runtime.
The score also tells you which leg to move to raise it.
One Floe key covers the stack, live today: LLMs (OpenAI, Anthropic, Venice AI), speech (Deepgram, ElevenLabs), telephony (Floe Phone via Twilio), and memory, data & search (HydraDB, Exa, Tavily) — part of a marketplace of 36+ services across 8 categories, 2,000+ payable APIs.
Open-weight models — Llama, Qwen, DeepSeek, Mistral, Gemma, Command-R — run keyless via the gateway, pay-as-you-go.
Pick your lane. On a platform: one config field (custom-LLM slot) plus a webhook — no code. BYOK: point your OpenAI-compatible SDK at Floe's base URL with your Floe key; drop-in SDKs for AgentKit, LangChain, CrewAI, Vercel AI SDK, OpenAI Agents, and Claude (MCP). Keyless: paste one line into Claude Code or Cursor and your agent provisions itself. Or hit the REST API from anything that speaks HTTP.
Full quickstart: Agent Quickstart →
Fund by Visa, Mastercard, ACH, Apple Pay, Google Pay, or local methods in 100+ countries; settlement is automatic.
Pricing: free to integrate — no subscription, no seat fees, no minimums. Floe earns 5% on volume routed through it; vendors you call charge their own rates. BYOK only free.
Where Floe is in the path: per-call and daily caps, vendor allowlists, and time-bound permissions are enforced before payment — an over-cap call gets a 402, not a bill. Everywhere else: Reconcile Mode catches the cost at call-end and the circuit breaker denies the next call, across every platform at once.
Plus a self-serve kill switch: pause any agent instantly, or let a policy auto-trip it. A runaway campaign dies at call N, not call 10,000.
Alex Christian (DataMynt co-founder; payments, treasury, and compliance risk at Airwallex, Western Union, eBay) and Shivam Chaturvedi (DataMynt co-founder; CTO at Kado.money, acquired; founding engineer at Transak). Both shipped payments, compliance, and billing infrastructure at scale before Floe.
Every leg of the call. One key. One ledger.
These are the verified services live today; anything not listed is one submission away.
Sarvam's Indic chat, STT (Saaras), and TTS (Bulbul) run on the same key and ledger as the rest of your stack — regional-language agents without a separate vendor relationship.
"Token and TTS usage varies every call, so true per-call cost only exists by joining usage data across providers after the call. Floe gives us that in real time."
CEO
$5M ARR voice agency
1/4
"Floe solves one of the missing pieces that voice AI builders need to operate autonomously in the real world: multi vendor billing and secure spending governance."
Ratikesh
Voice AI Developer at Pharma Company
2/4
"Shoutout to [Floe] app because cost tracking is HARD"
Naomi Carrigan
DevRel / Community Lead at Deepgram
3/4
"The problem Floe's solving is real. We hear some version of it from every team managing multi-model, multi-vendor agent stacks."
Partnerships Team
Z.ai
4/4
"Token and TTS usage varies every call, so true per-call cost only exists by joining usage data across providers after the call. Floe gives us that in real time."
CEO
$5M ARR voice agency
1/4
"Floe solves one of the missing pieces that voice AI builders need to operate autonomously in the real world: multi vendor billing and secure spending governance."
Ratikesh
Voice AI Developer at Pharma Company
2/4
"Shoutout to [Floe] app because cost tracking is HARD"
Naomi Carrigan
DevRel / Community Lead at Deepgram
3/4
"The problem Floe's solving is real. We hear some version of it from every team managing multi-model, multi-vendor agent stacks."
Partnerships Team
Z.ai
4/4
Free to integrate and try BYOK. 5% per keyless spend through Floe.
Who's behind Floe
No. BYOK is live today: keep your own vendor accounts and keys — Floe meters, joins, and caps on top of them, and your platform spend flows onto the same ledger via end-of-call webhooks. Keyless — Floe fronts the vendor, one key, welcome credits — is the fast lane for prototypes and net-new agents.
Most production teams run BYOK; most prototypes start keyless. Switch anytime.
A voice call touches 7–20 vendors billing separately, and token and TTS usage varies every conversation — so true per-call cost only exists by joining usage data across providers after each call.
Floe does that join in real time and enforces budgets on top: caps rejected before money moves where Floe is in the path, and a circuit breaker that denies the next call everywhere else. One ledger: per-call, per-agent, per-vendor, per-customer.
Token routers meter your LLM spend — ~40% of a voice call's bill. The other ~60% — telephony, STT, TTS, search, memory — is spread across vendors they never see.
Floe meters the entire bill, enforces caps across all of it, and sits as the governance layer above your whole stack, token routers included.
Yes — through the platforms' own documented extension points, with zero platform cooperation. Point the custom-LLM slot at Floe for pre-call enforcement on ~60% of call cost; connect the end-of-call webhook and every call lands on one ledger with a between-call circuit breaker.
On BYOK, these platforms report provider costs as $0 — Floe is how you see and cap that spend anyway.
No — by design. A dropped call is a worse failure than an expensive one. Enforcement is pre-call admission: where Floe is in the path (LLM, STT, TTS, Floe Phone), an over-budget call is denied before it starts. Where it isn't, Reconcile Mode meters the cost at call-end and the circuit breaker denies the next call.
Your coverage score shows exactly which of your spend sits in which bucket.
A per-agent number in your dashboard: the % of that agent's spend that is pre-call enforceable vs post-call reconciled vs dark — across every platform it runs on. No single platform can compute this about itself, because no platform sees spend outside its own runtime.
The score also tells you which leg to move to raise it.
One Floe key covers the stack, live today: LLMs (OpenAI, Anthropic, Venice AI), speech (Deepgram, ElevenLabs), telephony (Floe Phone via Twilio), and memory, data & search (HydraDB, Exa, Tavily) — part of a marketplace of 36+ services across 8 categories, 2,000+ payable APIs.
Open-weight models — Llama, Qwen, DeepSeek, Mistral, Gemma, Command-R — run keyless via the gateway, pay-as-you-go.
Pick your lane. On a platform: one config field (custom-LLM slot) plus a webhook — no code. BYOK: point your OpenAI-compatible SDK at Floe's base URL with your Floe key; drop-in SDKs for AgentKit, LangChain, CrewAI, Vercel AI SDK, OpenAI Agents, and Claude (MCP). Keyless: paste one line into Claude Code or Cursor and your agent provisions itself. Or hit the REST API from anything that speaks HTTP.
Full quickstart: Agent Quickstart →
Fund by Visa, Mastercard, ACH, Apple Pay, Google Pay, or local methods in 100+ countries; settlement is automatic.
Pricing: free to integrate — no subscription, no seat fees, no minimums. Floe earns 5% on volume routed through it; vendors you call charge their own rates. BYOK only free.
Where Floe is in the path: per-call and daily caps, vendor allowlists, and time-bound permissions are enforced before payment — an over-cap call gets a 402, not a bill. Everywhere else: Reconcile Mode catches the cost at call-end and the circuit breaker denies the next call, across every platform at once.
Plus a self-serve kill switch: pause any agent instantly, or let a policy auto-trip it. A runaway campaign dies at call N, not call 10,000.
Alex Christian (DataMynt co-founder; payments, treasury, and compliance risk at Airwallex, Western Union, eBay) and Shivam Chaturvedi (DataMynt co-founder; CTO at Kado.money, acquired; founding engineer at Transak). Both shipped payments, compliance, and billing infrastructure at scale before Floe.
No. BYOK is live today: keep your own vendor accounts and keys — Floe meters, joins, and caps on top of them, and your platform spend flows onto the same ledger via end-of-call webhooks. Keyless — Floe fronts the vendor, one key, welcome credits — is the fast lane for prototypes and net-new agents.
Most production teams run BYOK; most prototypes start keyless. Switch anytime.
A voice call touches 7–20 vendors billing separately, and token and TTS usage varies every conversation — so true per-call cost only exists by joining usage data across providers after each call.
Floe does that join in real time and enforces budgets on top: caps rejected before money moves where Floe is in the path, and a circuit breaker that denies the next call everywhere else. One ledger: per-call, per-agent, per-vendor, per-customer.
Token routers meter your LLM spend — ~40% of a voice call's bill. The other ~60% — telephony, STT, TTS, search, memory — is spread across vendors they never see.
Floe meters the entire bill, enforces caps across all of it, and sits as the governance layer above your whole stack, token routers included.
Yes — through the platforms' own documented extension points, with zero platform cooperation. Point the custom-LLM slot at Floe for pre-call enforcement on ~60% of call cost; connect the end-of-call webhook and every call lands on one ledger with a between-call circuit breaker.
On BYOK, these platforms report provider costs as $0 — Floe is how you see and cap that spend anyway.
No — by design. A dropped call is a worse failure than an expensive one. Enforcement is pre-call admission: where Floe is in the path (LLM, STT, TTS, Floe Phone), an over-budget call is denied before it starts. Where it isn't, Reconcile Mode meters the cost at call-end and the circuit breaker denies the next call.
Your coverage score shows exactly which of your spend sits in which bucket.
A per-agent number in your dashboard: the % of that agent's spend that is pre-call enforceable vs post-call reconciled vs dark — across every platform it runs on. No single platform can compute this about itself, because no platform sees spend outside its own runtime.
The score also tells you which leg to move to raise it.
One Floe key covers the stack, live today: LLMs (OpenAI, Anthropic, Venice AI), speech (Deepgram, ElevenLabs), telephony (Floe Phone via Twilio), and memory, data & search (HydraDB, Exa, Tavily) — part of a marketplace of 36+ services across 8 categories, 2,000+ payable APIs.
Open-weight models — Llama, Qwen, DeepSeek, Mistral, Gemma, Command-R — run keyless via the gateway, pay-as-you-go.
Pick your lane. On a platform: one config field (custom-LLM slot) plus a webhook — no code. BYOK: point your OpenAI-compatible SDK at Floe's base URL with your Floe key; drop-in SDKs for AgentKit, LangChain, CrewAI, Vercel AI SDK, OpenAI Agents, and Claude (MCP). Keyless: paste one line into Claude Code or Cursor and your agent provisions itself. Or hit the REST API from anything that speaks HTTP.
Full quickstart: Agent Quickstart →
Fund by Visa, Mastercard, ACH, Apple Pay, Google Pay, or local methods in 100+ countries; settlement is automatic.
Pricing: free to integrate — no subscription, no seat fees, no minimums. Floe earns 5% on volume routed through it; vendors you call charge their own rates. BYOK only free.
Where Floe is in the path: per-call and daily caps, vendor allowlists, and time-bound permissions are enforced before payment — an over-cap call gets a 402, not a bill. Everywhere else: Reconcile Mode catches the cost at call-end and the circuit breaker denies the next call, across every platform at once.
Plus a self-serve kill switch: pause any agent instantly, or let a policy auto-trip it. A runaway campaign dies at call N, not call 10,000.
Alex Christian (DataMynt co-founder; payments, treasury, and compliance risk at Airwallex, Western Union, eBay) and Shivam Chaturvedi (DataMynt co-founder; CTO at Kado.money, acquired; founding engineer at Transak). Both shipped payments, compliance, and billing infrastructure at scale before Floe.