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.
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.
Install @aifinpay/mcp with npx -y @aifinpay/mcp. The MCP server is read-only by default. Its payable_fetch tool appears only when the owner enables payments with a persistent wallet, explicit USD and gas limits, and allowed HTTPS gateway origins. The Node @aifinpay/agent SDK exposes the reviewed fetchPaid path. Keep private keys and recovery phrases outside prompts. Follow the current agent guide and client capability notes before paying.
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.