One key. Every vendor. Every model.

Read https://dev-dashboard.floelabs.xyz/agents.md and set up Floe for this project.
Paste into Claude Code, Cursor, or any coding agent.Read the quickstart
Works with
Anything that speaks HTTP — every model, every vendor, one key.
For production teams

Running production agents on Vapi, Retell, Bland, LiveKit or Pipecat?

15 minutes with the founders. Bring your vendor list — we'll map your whole bill onto one ledger on the call.

Alex Christian — Co-founder, Floe
Book a demo
The whole bill

One key covers every line on the invoice

Most agent-payment tools stop at LLM tokens. A voice agent's cost isn't tokens — it's transcription, speech, telephony, search, and reasoning across five vendors on a single call. Floe is the one integration in front of all of it, live today.

One voice call · what it actually coststotal $0.0300
TelephonyTwilio
$0.0072
TranscriptionDeepgram
$0.0041
LLM / reasoningOpenAI
$0.0127
SpeechElevenLabs
$0.0038
SearchExa
$0.0022
A token router sees 42%
Just the LLM slice — $0.0127 of the call.
Floe sees 100%
Every vendor, every line — $0.0300.
LayerVendorsWhat's live
LLM / reasoningOpenAI, Anthropic, Venice AIPay per call, any model, via one Floe key
Speech (STT / TTS)Deepgram, ElevenLabsSame key, same ledger, sub-cent per call
TelephonyFloe Phone via TwilioOn the same ledger + spend caps**
Memory / data / searchHydraDB, Exa, TavilyMetered per call, allowlisted per agent

** Floe Phone spend is unified onto the same ledger with the same spend caps.

Token routers like OpenRouter meter LLM spend. Floe meters the entire agent bill — speech, telephony, search, compute — so your budgets, caps, and cost analytics cover 100% of what a call costs, not the fraction that's tokens.

"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

Keyless LLM · one key

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 separate account and key for every provider — Floe fronts the vendor and meters it on your one ledger. Fund with a card; your agent never touches a wallet.

floe_•••key
Open-weight · live & keyless
LlamaQwenDeepSeekMistralGemmaCommand-R

Served keyless via the Floe gateway, pay-as-you-go — self-hosted and serverless, so no per-provider key to manage.

BYOK optional. Bring your own provider key and pay at cost, or go keyless and let Floe front it.
Open source

Start with the guardrail. No account.

floe-guard hard-stops a runaway agent before it burns your bill. Local, framework-agnostic, MIT.

$pip install floe-guard
Need caps enforced server-side, across vendors, on one ledger?Start Building
FAQ
Your questions, answered

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.

Keyless: the full financial loop
Pay any vendor per call. Authorize every dollar. Bill it from one place.
Connect a card and your agent can pay thousands of vendors via pay as you go APIs with hard spend authorization enforced before the money moves — and one ledger across every vendor.
Step 1 · Fund
Connect a card — your agent is funded
Top up from a card or bank in 100+ countries. Visa, Mastercard, Apple Pay, Google Pay.
Visa · Mastercard · Apple/Google Pay · 100+ countries
// Card or bank in. Vendors paid out.

  IN  Agent Wallet    OUT
  ────             ────
  Cards           Virtual cards
  Bank transfer    Bank accounts
  Apple Pay       Local payouts
  Google Pay
Step 2 · Pay
Pay as you go any vendor API, per call — Floe settles the vendor
Send any URL through the Floe proxy. Floe pays the vendor, settles instantly, and debits your agent’s ledger — down to sub-cent, with no 30¢ card floor. The agent just gets its response back; it never touches the payment layer.
2,000+ payable APIs* · ~50ms signing
// Agent sends the target URL - that's it
await fetch("https://credit-api.floelabs.xyz/v1/proxy/fetch", {
  method: "POST",
  headers: { "Authorization": `Bearer ${apiKey}` },
  body: JSON.stringify({
    url: "https://api.anthropic.com/v1/messages",
    method: "POST",
    body: payload
  })
});

// → Floe settles the vendor, debits your ledger,
//   returns the response. No wallet, no SDK.
// Response header: X-Floe-Payment-Amount
Step 3 · Authorize
Set spend authorization it can’t blow past
Hard limits per agent, per vendor, per task — optionally time-bound — enforced before the call, not on next month’s invoice. Stop a runaway agent at $1 instead of discovering a $400 loop after the fact.
Pre-call enforcement · per-agent · per-vendor · time-bound
// Authorize spend at the agent + vendor level
await fetch("https://credit-api.floelabs.xyz/v1/spend-controls", {
  method: "POST",
  body: JSON.stringify({
    agentId: "agt_research_01",
    dailyCapUsd: 50,
    perCallCapUsd: 2,
    vendors: ["anthropic", "pinecone"], // allowlist
    expiresAt: "2026-06-30T00:00:00Z"
  })
});

// Any call over the cap or off the allowlist is
// rejected BEFORE money moves - a 402, not a bill.
Step 4 · Bill
One ledger across every vendor
Every payment — across all your APIs and all your agents — lands on one itemized ledger. Per-call cost, per-vendor totals, per-agent and per-customer attribution. The spend visibility card-based and per-provider billing can’t give you. Running BYOK or on a platform? The same ledger ingests that spend too — see “Inside your platform.”
Per-call · per-vendor · per-agent · per-customer
// Unified spend ledger, filterable by agent
const feed = await fetch(
  "https://credit-api.floelabs.xyz/v1/developer/activity?agentId=agt_research_01"
)

// Returns an itemized, unified stream:
// [
//   { vendor: "anthropic", call: "messages",
//     costUsd: 0.012, ts, agentId, customerId },
//   { vendor: "pinecone",  call: "query",
//     costUsd: 0.003, ts, agentId, customerId },
//   ...
// ]

// Roll up by vendor, agent, or customer to bill.

"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

Pricing

Free to integrate and try BYOK. 5% per keyless spend through Floe.

$0to integrate
No subscription
No minimums
No seat fees
Get Started
Meet the team

Who's behind Floe

Floe Labs founders
Alex Christian
Co-founded DataMynt. Former Airwallex, Western Union, eBay.
Shivam Chaturvedi
Co-founded DataMynt. Previously CTO Kado.money (Acquired), Founding engineer at Transak.

Book a demo with the founders
15 minutes. We'll map your vendor bill on the call.
FAQ
Your questions, answered

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.

FAQ
Your questions, answered

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.