🔌 MCP Tools
@xentfi/mcp-sdk — a Model Context Protocol server exposing an agent’s own XentFi wallet, spend policy, and payments as 15 tools any MCP client can call: Claude Desktop, Cursor, VS Code, ChatGPT, ElizaOS, CrewAI, Codex.Use this when your agent owns a wallet and needs to check balances, place transfers, or manage its own funds under a XentFi spend Policy.💸 x402 Facilitator
@xentfi/x402-facilitator-sdk — a typed client for verifying and settling HTTP 402 Payment Required payments signed with real EIP-3009 authorizations.Use this when your agent needs to pay for a single API call (or get paid for one) without managing a wallet at all — just a signature.How they fit together
They’re independent: an agent can use MCP tools to manage its own wallet, x402 to pay other services, both, or neither (calling the core API directly). Most agents that transact autonomously use MCP tools for their own treasury and x402 when they need to pay a third-party API mid-task.Two different credentials
See Authentication for how to get each.
Get started
Quickstart
Get credentials and make your first call on either path.
Authentication
Agent API keys vs. WAAS keys, side by side.
Tools Reference
Every
xentfi_* MCP tool.x402 Reference
X402FacilitatorClient, types, and signing helpers.Guides & deep dives
Concepts, client-by-client integration walkthroughs, and full protocol guides live in the Documentation tab so this tab stays focused on quick reference:MCP Tools guide
Client integrations (Claude, Cursor, VS Code, ChatGPT, ElizaOS, CrewAI, Codex) and remote HTTP deployment.
x402 guide
The 402 protocol flow, resource-server and payer walkthroughs, EIP-3009 signing.