Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดThe TypeScript SDK for Floe — know what every AI call really costs. Floe costs each call the moment it ends across every vendor — telephony, STT, LLM, TTS, search, data — on one ledger, ties the spend to the client and campaign, and shows your margin per contract; then you bill your own customers off those actuals through your own Stripe. This SDK is the programmatic surface: one key that pays any x402 vendor API through one endpoint, with budgets your agent can reason about. Walletless. No crypto required.
Website · Docs · Dashboard · Python SDK
One key for your agent's whole vendor bill — LLM, voice, telephony, search, data — metered per call and budget-capped. Let your coding agent set it up, or wire it yourself:
New accounts get a $3 Welcome Credit (300 API credits) — no card. Set up with your AI tools → · Get a key →
Your agent calls paid APIs — LLMs, voice, search, data. Floe is the spend layer in front of those calls:
Two layers in one package:
FloeAgent (the runtime client) can be used standalone:
npm install floe-agent
The AgentKit action providers need @coinbase/agentkit and its peers:
npm install floe-agent @coinbase/agentkit viem zod
No wallet, no chain. Your agent pays for an API and stays inside its budget.
import { FloeAgent } from "floe-agent";
const agent = new FloeAgent({ apiKey: process.env.FLOE_API_KEY });
// Check budget before spending. `balance()` returns a plain number.
const available = await agent.balance(); // dollars available to spend
// For active loans, pending settlements, and raw units, use:
// const detail = await agent.balanceDetails(); // BalanceResult
// Pay any x402 API. The agent never touches the payment layer.
const res = await agent.fetch({
url: "https://api.exa.ai/search",
method: "POST",
body: JSON.stringify({ query: "AI agent frameworks" }),
});
// res is a FetchResult: res.body (string), res.cost (USDC dollars), res.status
Fund with fiat: operators fund the wallet with USDC via Coinbase — card, bank transfer, Apple Pay, Google Pay — directly from the dashboard. No crypto on-ramp.
Get an agent key: dashboard → connect →
Create an agent → copy the floe_<hex> key (shown once).
Most SDKs let an agent spend. Floe lets an agent reason about spend before it commits, then stops it before it overruns.
// 1. Preflight the cost against your balance — no payment is made.
const estimate = await agent.estimateCost("https://api.example.com/premium");
// estimate => { cost: number; canAfford: boolean; isPaid: boolean }
// 2. Only pay if the agent can afford it.
if (estimate.canAfford) {
await agent.fetch({
url: "https://api.example.com/premium",
method: "POST",
body: JSON.stringify({ prompt: "..." }),
});
}
This is the "answer the three rational-agent questions in one round-trip" workflow: Do I have budget? Is this call worth it? Where am I in my spend?
The lower-level
x402ActionProvideractionestimate_x402_costis a separate API that returns a richer reflection (willExceedAvailable/willExceedSpendLimit) for AgentKit tool calls — see the Advanced section.
// Vercel AI SDK (requires: npm install floe-agent @coinbase/agentkit viem zod)
import { AgentKit } from "@coinbase/agentkit";
import { getVercelAITools } from "@coinbase/agentkit-vercel-ai-sdk";
import { generateText } from "ai";
import { openai } from "@ai-sdk/openai";
import { floeActionProvider, x402ActionProvider } from "floe-agent";
const agentkit = await AgentKit.from({
walletProvider,
actionProviders: [
floeActionProvider(),
x402ActionProvider({ facilitatorApiKey: process.env.FLOE_FACILITATOR_API_KEY }),
],
});
const tools = await getVercelAITools(agentkit);
const { text } = await generateText({
model: openai("gpt-4o"),
tools,
maxSteps: 10,
prompt: "What did my agent spend today?",
});
// MCP (Claude Desktop / Claude Code / Cursor) — zero install
{ "mcpServers": { "floe": {
"url": "https://mcp.floelabs.xyz/mcp",
"transport": "streamable-http"
} } }
These actions are for self-custody and on-chain use cases (managing your own wallet, lending against deposits, MEV/arb). If you're building a standard agent that just needs to pay for APIs, use
FloeAgentabove — you don't need this section.
floeActionProvider() exposes 30 lending actions; x402ActionProvider()
exposes 25 (6 x402 credit-delegation + 10 agent-awareness + 5 merchant-allowlist
npm install floe-agent @coinbase/agentkit viem zod
import { AgentKit } from "@coinbase/agentkit";
import { floeActionProvider, x402ActionProvider } from "floe-agent";
const agentkit = await AgentKit.from({
walletProvider,
actionProviders: [
floeActionProvider({ knownMarketIds: ["0x..."] }),
x402ActionProvider({ facilitatorApiKey: process.env.FLOE_FACILITATOR_API_KEY }),
],
});
// Borrow against on-chain collateral. marketId is required — fetch via get_markets.
await agentkit.run("instant_borrow", {
marketId: "0x...",
borrowAmount: "9500000000",
collateralAmount: "10000000000",
maxInterestRateBps: "800",
duration: "1209600",
});
Skip
x402ActionProvideronly if your agent never makes x402 payments and never queries credit / spend-limit / threshold state. You losex402_fetch,estimate_x402_cost,get_credit_remaining,set_spend_limit, andregister_credit_threshold.
floeActionProvider() — 30 lending actionsWrite actions auto-approve tokens to LendingIntentMatcher with a 1% buffer,
then submit the transaction through your configured WalletProvider and return
a formatted result including the tx hash.
deploy_flash_arb_receiver · check_flash_arb_readiness · verify_flash_arb_receiver
Flash-arb flow: deploy → check readiness → estimate profit → flash_arb →
check balance. The deployed receiver address is stored on the provider instance
and auto-reused; override with receiverAddress.
x402ActionProvider() — 25 actionsAll x402 + agent-awareness + allowlist actions require facilitatorApiKey
configured on x402ActionProvider.
import { AgentKit } from "@coinbase/agentkit";
import { floeActionProvider, x402ActionProvider } from "floe-agent";
const agentkit = await AgentKit.from({
walletProvider,
actionProviders: [
floeActionProvider(),
x402ActionProvider({ facilitatorApiKey: process.env.FLOE_FACILITATOR_API_KEY }),
],
});
Decision-loop pattern (AgentKit):
estimate_x402_cost→ checkwillExceedAvailable/willExceedSpendLimit→ conditionallyx402_fetch. (TheFloeAgent.estimateCostmethod above is the runtime-client equivalent; it gates oncanAfford.)
Opt-in, default-deny restriction on which destinations an agent may pay. An
allowlist entry is a capped policy row that doubles as "allowed AND capped".
Default mode off = allow any vendor.
Coinbase Agentic Wallet (CLI/MPC, send/trade only) is a different product and is NOT compatible with AgentKit ActionProviders — Floe actions need a WalletProvider that can sign arbitrary contract calls.
Networks: Base Mainnet (8453) · Base Sepolia (84532).
npm i -g floe-agent # installs the `floe-agent` bin
floe-agent status --json # auth check + capabilities + balance snapshot
The
floebin name belongs to the standalone platform CLI,@floelabs/cli— the full platform from your terminal: setup, agents, keys, budgets, policies, billing, funds, phone, and metered calls (npx @floelabs/cli init). This package's CLI is invoked asfloe-agent: the AgentKit-companion CLI for the agent-runtime SDK. The interactive lending REPL (floe-agent run, the historical default) is lazy-loaded — management commands never pay its startup cost undernpx.
floe-agent status auth + capabilities probe + balances
floe-agent auth status|set-key dev key via FLOE_API_KEY env or OS keychain
floe-agent agents create|list|get|pause|resume|close agent lifecycle (dev key)
floe-agent agents keys create|rotate|revoke [--budget <usd>] runtime floe_ keys
floe-agent keys create|list|rotate|revoke developer floe_live_ keys
floe-agent policy list|set|delete|reset [--agent <id>|--team] spend policies
floe-agent limit get|set|clear [--agent <id>] session spend cap
floe-agent allowlist mode|add|remove|list [--agent <id>] merchant allowlist
floe-agent balance developer rollup / agent balance
floe-agent fund <agentId> deposit address + funding instructions
floe-agent estimate <url> | floe-agent forecast <url>… x402 cost preflight (agent key)
floe-agent pay <url> [--method --body --header] paid x402 call via /v1/proxy/fetch
floe-agent models | floe-agent usage | floe-agent activity catalog / analytics / feed
floe-agent webhooks create|list|test|rotate-secret|deliveries
floe-agent skills install Floe skill (Floe-Labs/agent-skills) → .claude/skills + ~/.agents/skills
floe-agent mcp install npx -y add-mcp https://mcp.floelabs.xyz/mcp
floe-agent run | register | use | rotate | revoke | open-credit-line legacy wallet flows
--json on every command: raw API JSON on stdout, no spinner/color.0 ok · 1 error · 2 usage · 4 auth required ·
5 payment required (402).NO_COLOR respected.User-Agent: floe-cli/<version>.Management commands (agents, keys, policy, …) resolve, in order:
FLOE_API_KEY when it holds a floe_live_ developer key → the key stored by
floe-agent auth set-key → EIP-191 wallet-signature headers when PRIVATE_KEY is
set. If none of the above is present, the command exits 4 with a pointer to
dev-dashboard.floelabs.xyz. Payment
commands (pay, estimate, forecast) prefer FLOE_AGENT_KEY, then the
active agent's keychain key, then FLOE_API_KEY when it is a floe_ agent
key. So FLOE_API_KEY accepts either key type — the key's own prefix decides
which plane it drives (the API refuses agent keys on /v1/developer/*).
See floe-cookbook for end-to-end
multi-framework agents. The examples/ directory here has a Vercel AI SDK
chatbot (chatbot.ts) and a no-framework standalone script (standalone.ts).
# npm link (live symlink)
npm run build && npm link # then `npm link floe-agent` in your project
# npm pack (simulates a real publish — safest validation)
npm run build && npm pack # creates floe-agent-<version>.tgz
npm pack --dry-run # should include only dist/, README.md, package.json
Project entry points: src/index.ts (exports both providers),
floeActionProvider.ts (lending), x402ActionProvider.ts (x402 +
agent-awareness), schemas.ts (Zod input schemas), cli/ (interactive REPL).
Floe ships the spend layer first and builds credit on top of it.
Website · Docs · Python SDK · MCP server · Examples
MIT
AI Initiative Ledger — Coinbase AgentKit actions, TypeScript (deprecated: use floe-guard or @floelabs/cli)
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Agentkit Actions ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 AI Initiative Ledger — Coinbase AgentKit actions, TypeScript (deprecated: use floe-guard or @floelabs/cli)