These are local source versions, not publication claims. The Solana integration
candidate is Node/Python2.5.0, MCP2.7.0 and canonical sibling skill2.8.0. Python2.4.0
was published on2026-10-05; the previous Node2.4/MCP2.6 cohort is preserved on its
release branch. Registry publication, genuine MCP dependency/lock refresh and
standalone CI are separate release gates. No fabricated registry resolutions are
used. Source-cohort checks install the actual packed SDK and skill together.
Solana paid access candidate
The candidate adds complete conditional fetchPaid / fetch_paid execution for
native SOL and classic SPL USDC/USDT. Owners select Solana and its cluster/mode
explicitly, supply a fee plus rent budget and keep the keys locally. The same
local wallet ledger covers EVM and Solana unresolved purchases. Quote, signed
transaction, receipt and public history bind the exact network/program; base58
addresses retain their case.
Both canonical Solana records remain disabled. High-level payment refuses before
quote signing or HTTP when the selected registry record is unavailable. The
source tests use injected synthetic approved records; they do not activate a
network or establish deployed-program/funded acceptance. See
node payment instructions,
Python instructions, and
Solana decision and acceptance.
The current @aifinpay/mcp source registers these tools:
Tool
Purpose
agent_address
Read the current EVM, Solana and Casper public addresses.
agent_reload
Reload configured local wallet files without starting a new conversation.
agent_claim_self
Link the agent to its owner's dashboard with a one-time URL from dash.aifinpay.io. Signs only an AiFinPay claim challenge for the agent's own address; moves no funds.
payable_fetch
Only when the owner enables payments. Fetch a GET resource from an owner-approved AIFP-1 merchant, buying a prepaid batch on the explicitly configured EVM v1.4 chain within owner limits; Polygon remains the default.
agent_quota
Read the agent's quota.
agent_history
Read indexed AiFinPay payment history or retained receipt history.
agent_passport_resolve
Resolve a public Agent Passport identity and verified wallet bindings.
settlement_routes
Read currently runtime-verified AIFP-1 / AIFP-2 settlement routes.
settlement_invoice
Build and validate a non-signing EVM settlement invoice.
settlement_solana
Build and validate a non-signing Solana settlement invoice.
settlement_casper
Build and validate a non-signing Casper settlement invoice.
deployment_info
Read deployment addresses, program IDs and settlement status across supported ecosystems.
With AIFINPAY_MODE=dev, an additional dev_payment_quote tool is available for dev-only quote inspection.
Without owner payment configuration the MCP server is read-only: it signs no payment, and creating an invoice or quote is not a completed payment. payable_fetch is registered — and signs and broadcasts locally — only when the owner sets AIFINPAY_PAYMENTS_ENABLED=1 together with AIFINPAY_MAX_USD, AIFINPAY_DAILY_USD, AIFINPAY_GATEWAY_ORIGINS and a native gas cap (AIFINPAY_MAX_GAS; legacy AIFINPAY_MAX_GAS_POL is Polygon-only). Incomplete enabled configuration refuses startup. See mcp/README.md.
Legacy tools such as agent_call, agent_quote, pay_with_split and quote_split are not registered by the current MCP server.
For a persistent local identity, initialize the keystore once. init creates an encrypted keystore and refuses to create one without a passphrase unless you ask for a plaintext test wallet:
AIFINPAY_WALLET_PASSPHRASE='<a long passphrase>' npx @aifinpay/mcp init
# disposable test wallet only:
npx @aifinpay/mcp init --plaintext
Then use agent_reload and agent_address to verify the selected public wallet. Do not paste seeds or private keys into chat, issues, logs or shared configuration.
The SDK surfaces have different execution status. Do not treat them as interchangeable.
Node / TypeScript
@aifinpay/agent includes the AIFP-1 fetchPaid path. The 2.4.0 source candidate supports Polygon, Base, Optimism, Arbitrum, Avalanche, BNB, Unichain, XRPL EVM and Robinhood. Every non-Polygon rail requires explicit owner selection. Paid execution validates the selected chain, deployment/runtime/signer/profile, pinned token and RPC before signing; native payments require a fresh independent price. Durable bound reservations prevent unresolved payments from resetting the daily cap or buying the same access on another rail. Legacy Polygon v1.3 still requires its separately reviewed settlement pin. Source support does not activate a production route or publish a package.
The Python 2.4.0 source candidate uses AiFinPayAgent.fetch_paid for the same nine EVM mainnets, pinned native/stable assets and exact six/eighteen-decimal token amounts. Every non-Polygon chain requires an explicit native gas budget in wei. Shared local-file reservations serialize concurrent processes, survive unknown broadcasts and reconcile recovered receipts once. Its legacy paid call() settlement path stays disabled. The MCP candidate consumes the Node source cohort with explicit owner chain/asset configuration and private durable recovery.
Current protocol economics documented in the v2 line:
AIFP-1: payer pays the quoted gross amount; merchant receives 99%; AiFinPay receives 1%; creator/referral receives 0%.
AIFP-2 / x402: provider receives 100%; AiFinPay protocol fee is currently 0%.
Older 98.99% / 1% / 0.01% examples belong to a retired fee model and must not be used as current economics.
Merchant monetization
For a site or API that wants to monetize AI-agent traffic:
npm install @aifinpay/gate
The merchant package can return HTTP 402 challenges, expose discovery metadata and meter paid access. See gate/README.md. Python servers (FastAPI, Starlette, Flask, Django) use pip install aifinpay-gate, the same gate as ASGI/WSGI middleware — see python-gate/README.md and the aifinpay-merchant skill in the AiFinPay/skill repository.
Deployment status
Deployment addresses and program IDs are registry data; they are not, by themselves, proof that settlement is enabled. Use deployment_info or the deployment registry and check settlementEnabled / status before presenting a network as active.
Solana
The old Solana program 5g9zWHF1Vv6GiGpA2ZbJQbSCDZd5hAk9AyvabRJvKFx2 was closed and is not the current program.
The current registry contains the redeployed v1.4.1 programs below, both currently disabled for settlement:
Network
Program ID
Settlement status
Reason
Devnet
8dty5bD738Z9TzEkDu8vLSnhpJNWtEGMUEcYaKCUTY6y
Disabled
Backend receipt verification is not implemented.
Mainnet
724Ut31i4ecY4dJ25z8HuZetu3A43xtNkPdk4JdbsfdD
Disabled
Backend receipt verification is not implemented and upgrade authority is not multisig.
Never print, log or publish a seed, private key, keystore JSON or signing secret.
Public addresses and transaction hashes are safe to display.
Do not infer production readiness from a contract address, program ID, quote or invoice alone.
Retain the original quote, transaction reference and idempotency context when recovering from a settlement error to avoid accidental duplicate payment attempts.