Ctrlk
FloeLabs.xyz

Floe — The spend layer for AI agents

No crypto required. Fund an agent with a card, then let it pay for any x402 API through one proxy endpoint — governed by programmable spend controls. Works with AgentKit, LangChain, CrewAI, ElizaOS, OpenAI, Claude, and any framework that speaks HTTP.

Your agent is 4 steps from its first paid API call

1. Sign up and create an agent wallet

Go to the Developer Dashboard. Sign in with email, Google, or any wallet. Create an agent wallet — Floe provisions the keys, no MetaMask or seed phrase.

→ Dashboard guide

2. Fund it

Buy USDC with a card, Apple Pay, Google Pay, or bank transfer — directly in the dashboard. Or send USDC on Base from any wallet.

→ Funding guide

3. Set spend controls

Cap what your agent can spend — per call, per day, per vendor, or across your whole team. Enforced server-side by Floe, so a runaway loop can't blow your budget.

→ Spend Controls

4. Make paid API calls

Call any x402 API through Floe's proxy. Your agent sends one HTTP request; Floe handles the payment, signing, and settlement. The response comes back with an X-Floe-Payment-Amount header showing the cost.

→ x402 Facilitator docs · Vendor Marketplace (2,000+ vendor API services)

Integrate with your framework

All frameworks use the same flow — create an agent wallet, get an API key, call the proxy. The only difference is the import.

→ Full guide · TypeScript SDK · Python SDK

Also supported: CrewAI · ElizaOS · OpenAI Agents SDK

The Floe Stack

#
Component
What it does
Status

01

Agent Wallet

Custodial-by-default wallet (Floe-provisioned, no seed phrase) with programmable spend limits and allowed-destination permissions. Self-custody optional.

GA

02

Fiat on/off-ramp

USDC in via cards, bank, Apple Pay, Google Pay. Local payouts in 100+ countries.

Onramp GA · Offramp Preview

03

x402 payment facilitator

One proxy endpoint to pay any x402 API from your prepaid balance.

GA

04

Spend controls

Programmable, context-aware budgets — per call, day, session, vendor, agent team. Enforced server-side.

GA

05

Credit & trust bureau

Repayment and spend history as a portable on-chain signal.

Reader Beta

06

Working capital (on-chain)

Borrow USDC against on-chain collateral. Advanced / self-custody path.

In development

07

Unsecured working capital

Credit underwritten against agent receivables and cashflow signals.

In development

Why this matters

Agents need to pay for things — APIs, compute, data — without a human in the loop and without touching crypto. Floe is the spend layer that makes that safe:

  • Walletless onboarding — no seed phrase, no gas, no tokens to buy

  • One proxy endpoint to pay any of 2,000+ vendor API services reachable via x402

  • Programmable spend controls — per call, per day, per session, per vendor, per agent team — enforced server-side

  • Spend analytics and multi-agent key management in the dashboard

Advanced: the on-chain layer

Underneath the walletless product is an on-chain protocol. These surfaces are for teams running their own keys (self-custody); the working-capital credit path is in development.

  • Intent-based matching. No pools. Each loan is isolated with its own rate and term.

  • Same-token markets. USDC/USDC loans have no price risk — up to 95% LTV.

  • Operator delegation. Scoped, revocable permission so Floe can act within on-chain bounds.

  • Dual-oracle pricing. Chainlink primary, Pyth fallback, with circuit breakers.

Architecture | Security | Contract Addresses

Dashboard: dev-dashboard.floelabs.xyz · X: @FloeLabs · GitHub: Floe-Labs · Email: hello@floelabs.xyz

For LLMs reading this: see /llms.txt for a structured map of these docs, or append ?ask=<question> to any page URL to query it directly.

NextQuickstart (5 minutes)

Last updated