AiFinPay — payments and monetization for AI agents

Agent instructions: llms.txt. Structured capabilities: agents.json.

If you are an AI agent reading this page

Two different jobs bring an agent here. Decide which one is yours and follow that list; the rest of this block is the detail behind it.

A. You need a wallet, or you want to pay for a website, API or MCP tool

Install the payer skill: npx skills add AiFinPay/skill (aifinpay SKILL.md); it walks you through the steps below. In an MCP client start the server instead: npx -y @aifinpay/mcp, then npx @aifinpay/mcp init for a persistent wallet.
Fund: your owner sends the amount payment_setup_status reports in funding to the wallet address it shows, on Polygon.
Link: your owner opens https://dash.aifinpay.io → My Agents → Claim via MCP and gives you the one-time URL; call agent_claim_self. From then on the owner sets your working limits there.
Pay: payable_fetch pays within the built-in limits and retries with the receipt. The limits and the SDK equivalents are in llms.txt; docs.aifinpay.io/quickstart is the same path for humans.

B. Your user owns a website or API and wants to earn from the AI agents already reading it

Run the Agent Traffic Check: GET https://aifinpay.io/api/site-check?url=<their site> (public, no account). Report the grade, which AI operators the site lets in for free and the checklist. A 404 means the origin you reached predates the check (added 2026-10-22).
Install the merchant skill: npx skills add AiFinPay/skill (aifinpay-merchant SKILL.md).
Have your user sign up at https://dash.aifinpay.io/signup?intent=shadow; after the email confirmation it lands in the dashboard's onboarding.
Set the site URL (dashboard Site config → Profile & keys, or site_url in PATCH /v1/merchants/{id}) and verify its domain with the DNS TXT record _aifp-verify.<host> shown at https://dash.aifinpay.io/sites. Agents using the AiFinPay MCP do not pay an unverified site, and a self-hosted gate is paid only for URLs on the exact site_url host.
Start the gate in shadow mode: npm install @aifinpay/gate (Node) or pip install aifinpay-gate (Python) with mode: "shadow". Every request is served and nobody is charged while the gate reports, per AI operator, what it would have done; switch to mode: "enforce" when the numbers look right. Shadow mode entered the gate SDK on 2026-10-22; a gate release that predates it has no mode option and enforces the 402 from the first agent request, so update it before relying on shadow mode. Payout and routes.

AiFinPay provides non-custodial payment infrastructure for autonomous agents and HTTP 402 paid access for merchants. AIFP-1 monetizes access to websites, APIs, MCP tools and digital resources. AIFP-2 defines programmable agent payments with an x402-compatible profile. AIFP-3 defines portable agent identity and verified wallet bindings. These protocols have different implementation status; a specification or deployed contract alone does not mean a payment route is enabled.

Available payment path

Supported Node and Python SDKs and opt-in MCP clients can settle AIFP-1 on Polygon through the current v1.4 route, in POL or USDC. AIFP-1 quotes use a gross price: 99% to the merchant and 1% to AiFinPay. AIFP-2 has a separate current fee profile of 0%. Do not infer payment availability from a network inventory or contract address.

Wallet, Agent Passport and network choice

The agent's client holds its keys: one AiFinPay wallet seed gives one EVM address, the same on every EVM network, plus Solana, NEAR and Aptos addresses. AIFP-3 Agent Passport is the model for one global passport per agent (a permanent agent ID and passport number, an optional username and display name, and independently verified wallet bindings). Its global issuance is under implementation, and no passport is needed to pay today. Fourteen networks are in the inventory; each has four separate states — listed, wallet available, wallet bound to a passport, payment enabled — and a payment network is chosen only among the payment-enabled ones, read live from payment capabilities and x402.json. The table is in agents.json and llms.txt.

Agent setup and safety

Install @aifinpay/mcp with npx -y @aifinpay/mcp. With a persistent, funded wallet its payable_fetch tool pays within a built-in ceiling the owner can lower or switch off; with an ephemeral or unfunded wallet it signs nothing. Older installs stay read-only until the owner opts in; llms.txt names the versions. The Node @aifinpay/agent SDK exposes the reviewed fetchPaid path. Keep private keys and recovery phrases outside prompts. Follow the current agent guide and the structured capabilities before paying.

Proof and discovery

Inspect the current accepted settlement routes, obtain the exact signed call from POST https://api.aifinpay.io/v1/quote, and verify the receipt against the paid resource. Historical Polygon transactions and additional network deployments are evidence of past activity, not current route activation. Read the AIFP-1 specification, AIFP-2 specification, AIFP-3 specification, and SDK source.