Skip to main content
Start with the AiFinPay skill. It contains separate instructions for an agent owner buying access and a merchant charging for a site or API.

Agent owners

For an assistant with MCP support, connect @aifinpay/mcp using the MCP setup guide. For your own application, install the Node or Python SDK and follow its versioned package documentation.
Choose the runtime you use; installing MCP already includes its SDK dependency. Keep the persistent wallet local and verify its public address in the client.
MCP @aifinpay/mcp 2.12.1 pays with payable_fetch from a persistent wallet, on by default within a $5 / $20-per-day ceiling (init → fund → link → pay); Node @aifinpay/agent 2.9.0 pays with fetchPaid and Python aifinpay-agent 2.7.1 with fetch_paid. All settle AIFP-1 (splitter v1.4) on Polygon by default, or on Base when the owner selects it, in the native currency or USDC; the smallest batch is $0.10 plus gas. A quote or invoice alone does not move funds. See payment support.
After creating the wallet, link the agent to your account at dash.aifinpay.io → My Agents to see its balance, payments and receipts. Under Link an agent, Claim via MCP gives a one-time URL for the agent’s agent_claim_self tool. The URL works only through that tool: opening it in a browser, or pasting it into a chat that has no AiFinPay MCP, links nothing. Without the MCP, link the wallet by signed message and have the agent sign the challenge (signDashboardClaim in Node, sign_dashboard_claim in Python). Set the agent’s working limits there under Controls; AiFinPay enforces them on every quote and receipt. Ask the agent to inspect the target origin’s /.well-known/x402.json and its API catalog. Agree on the resource, receipt scope, batch cost and separate gas budget before a supported payment is executed. Read discovery for the difference between general instructions and site-specific routes.

Merchants

Open the dashboard, register your site and follow the merchant onboarding guide. Use the aifinpay-merchant skill to guide integration of @aifinpay/gate. Publish discovery on the same origin as your protected routes. After a real payment, verify the merchant, amount and transaction in the dashboard; a quote or HTTP 402 response is not a completed payment.