The awareness tools exist so a model can ask whether the budget is there and whether the call is worth it before committing, and the forecast call runs a whole planned sequence through the policy before any of it executes. The part that matters when the model reasons badly is that the soft signal and the hard ceiling are separate: the spend cap and merchant allowlist are enforced on the server, so an agent cannot overspend regardless of what it decides.
Floe's spend layer in your MCP client: it costs each call as it ends across every vendor on one ledger, ties the spend to a client and campaign, and gives the agent tools to ask whether it can afford a call before making it. The same server carries Floe's lending market — intents, loans, collateral, liquidation — and executes paid x402 calls under a server-side spend cap and merchant allowlist. Signing up needs no card and no wallet.
- Spend awareness before the money goes: get_credit_remaining separates spendable balance from borrowing headroom, get_loan_state reports idle, borrowing, at_limit or repaying, and estimate_x402_cost prices a call against your own credit.
- Hard limits the agent cannot talk its way past: set_spend_limit and clear_spend_limit, register_credit_threshold for warnings on the way down, and an allowlist with set_allowlist_mode across off, host, vendor or both, plus per-entry spend caps.
- Paid calls: check_x402_url probes whether a URL is x402-protected and what it costs without any credential, x402_forecast runs a whole planned sequence through a policy preflight, and x402_pay settles with an idempotency key so a retry cannot double-pay.
- Market reads on the lending side: get_markets with current rates and liquidity, open lend and borrow intents, get_intent_details by offer hash, and get_token_price for a market's oracle price.
- Loan mechanics as unsigned transactions you sign yourself: create_lend_intent, create_borrow_intent, create_counter_intent, repay_loan, add_collateral, withdraw_collateral, liquidate_loan and revoke_intent.
- Position monitoring: get_loan, get_user_loans as both borrower and lender, get_loan_health for LTV, liquidation risk and early repayment terms, and get_accrued_interest.
- Pre-trade maths: calculate_risk, estimate_interest, check_compatibility between two intents, and simulate_transaction, which dry-runs an unsigned transaction and returns success or revert with a gas estimate.
- Fleet management on a developer key: create_agent, list_agents, get_agent, pause_agent as a per-agent kill switch, close_agent, and create, rotate, revoke and budget an agent's keys.
- Funding and reporting: get_funding_instructions, open_credit_line with its bounds checked first, get_balances, get_activity and get_usage_summary.
- Webhooks over a named event catalog — loan health and expiry warnings, liquidation, repayment, agent and key events, first x402 settlement — created, listed and test-fired.
- get_agent_reputation returns a score, a band and the collateral multiplier it implies, and search_floe_docs searches Floe's own documentation from inside the client.
A Floe key, and the tools say which kind they want: an agent key for spend limits, allowlists and paying, a developer key for creating agents, minting keys and reading account balances. Three tools need neither — the market list, the x402 URL probe and the docs search. Signup takes no card and no wallet and comes with a welcome credit. Connect to the hosted server over HTTP with the key as a bearer token, or run it locally over stdio with FLOE_API_KEY in the environment.
One command plus a key — npx -y add-mcp https://mcp.floelabs.xyz/mcp, then supply credentials