i̲p iAgentPay
Part of the iJarvis Agent Stack

x402 payments, with guardrails.
Budget, trace, and settle agent spend.

The x402 Foundation (Coinbase, Cloudflare, Stripe, AWS, Google, Microsoft, Visa, Mastercard) standardized agent payments. iAgentPay adds the layer every operator needs: spending limits, counterparty allowlists, budget tracking, settlement analytics.

iagentpay.spend(to=agent, amount=1.50, capability='research')

iAgentPay provides four primitives

Spend governance

Daily/hourly/per-counterparty limits. Spending anomalies flagged before payment authorization.

Counterparty checks

Refuse payment to counterparties below your iAgentFi rating threshold. Allowlist/denylist support.

Treasury analytics

Where is your agent's budget going? Which capabilities actually pay off? Cost-per-outcome reporting.

Multi-network

Base, Ethereum, Solana, Polygon, Arbitrum. Pay where your counterparty accepts, settle where you want.

The gap iAgentPay fills

x402 is primitive; operators need guardrails

Raw x402 is 'agent sees 402 Payment Required, pays USDC, retries.' In production, you need spending limits, approval workflows, and anomaly detection. That's iAgentPay.

Audit trail comes free

Every payment ledgered with full context: which agent, why, for what capability, what outcome. Export to your accounting system.

Works with any agent framework

LangGraph, CrewAI, AutoGen, Anthropic SDK, OpenAI Agents SDK. One integration, all frameworks.

Planned endpoints in Shipping Q3 2026

Preview of the planned API surface. OpenAPI 3.1 specification at /.well-known/openapi.yaml. Endpoints at api.pay.ijarvis.ai will serve requests at shipping q3 2026; agent-consumable JSON by design.

POST /v1/pay Execute x402 payment with guardrails applied
POST /v1/budget Configure spending budgets and limits
GET /v1/ledger Retrieve payment history
GET /v1/analytics Spend breakdown by counterparty, capability, outcome
Status: Shipping Q3 2026 (anchor product). 0.5% routing fee; first $10K volume free.

iAgentPay is one layer

Sixteen products. One stack. One entity. Trust, discovery, observability, payments, safety, simulation, composition, memory, identity, legal, markets, and owned compute underneath. Each layer reinforces the others. Use one or use them all.