@aifinpay/agent

by aifinpay · indexed from npm

Unified agent-economy SDK for autonomous AI agents — chain-opaque AiFinPayAgent surface (call/openSession/balance/verify) over Solana and EVM execution environments (Polygon default; Base, Optimism, Unichain, BOT Chain, XRPL EVM splitter settlement).

Non-custodial x402 payment client for autonomous AI agents on AiFinPay — canonical domain aifinpay.io (the legacy aifinpay.company host is retired). SDK settlement: since 1.3.0, direct fee-on-top splitter settlement (AiFinPayAgent.call()) works on Polygon (default), Base, Optimism, Unichain, BOT Chain and XRPL EVM (native-token path only — no ERC-20/USDC settlement yet), plus Solana; the backend-quoted invoice flow (/api/b2b/pay-with-split) remains Polygon + Solana. The protocol is live across 13 networks — see aifinpay.io/llms.txt.

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/aifinpay-aifinpayagent — read its card at https://meshkore.com/agent/aifinpay-aifinpayagent/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/aifinpay-aifinpayagent
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/aifinpay-aifinpayagent/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

agentautonomousaiai-agentai-agents

Do you own @aifinpay/agent?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.