Wisely Enterprises shield logo Wisely EnterprisesAgent-payment infrastructure

Novice-friendly install guide

x402 Agent-Payment Infrastructure

Use this when you want an AI agent to quote, pay for, invoke, and receipt paid AI/API work without juggling provider accounts or exposing wallet secrets.

Tell Your Agent This

Use the x402 Agent-Payment Infrastructure at:
https://payments.wiselyenterprisesllc.com/ai/manifest

First read the manifest and MCP metadata. When I ask for paid AI/API work, quote the service and total payment route before spending. If I have crypto that is not the required settlement asset, call the conversion quote route and show me the route. If I give you a third-party x402 seller URL, call the external x402 quote route with sellerUrl so Wisely can probe the HTTP 402 payment requirement, normalize it, and return the conversion/payment handoff. Never ask me for a seed phrase, private key, raw card, provider API key, or bank login. After any paid call, save the receipt id and summarize what was bought, what was paid, and whether the service completed.

What It Can Do

Hosted AI/API calls

Quote and invoke supported chat, embeddings, image, video, audio, search, and data services through one x402/developer-credit layer.

External x402 sellers

Probe a third-party paid-resource URL. The router reads standard HTTP 402 metadata, including JSON bodies and base64 Payment-Required headers.

Crypto conversion handoff

Quote whether supported Base, Ethereum, or Solana assets can become enough Base USDC to satisfy the payment requirement. Wallet signing stays with the caller.

Hosted paid endpoints

Builders can create paid request/response tools with a scoped builder key, logs, event search, receipts, revenue summaries, payout packets, and endpoint secrets.

Common Prompts

Use the x402 payment infrastructure to generate an image. Quote the cost first, use my funded wallet only after I approve, then return the image and receipt.
I found an x402 paywall. Use the x402 payment infrastructure to read the payment requirements, quote what crypto route can satisfy it, and tell me what wallet action is needed.
Create a paid x402 endpoint for my agent that charges five cents per call. Use my saved Wisely builder key or the Builder Console, keep secrets server-side, test the no-payment 402 response, then give me the buyer instructions.

Public Endpoints

Portable CLI

node wisely-x402.mjs doctor
node wisely-x402.mjs mcp tools
node wisely-x402.mjs key:set
node wisely-x402.mjs endpoints list
node wisely-x402.mjs builder revenue my-endpoint 30d

Latest Functional Proof

The latest external-style regression passed on May 22, 2026: public/indexer discovery passed 145/145 checks across normal browser, MCPScoringEngine, x402station, dexter schema fetcher, Googlebot-style clients, MCP JSON-RPC, and CORS preflight.

The backend E2E suite passed 23/23 checks: public discovery, MCP tool listing, external x402 header probe, hosted quote, HTTP 402 no-payment behavior, developer-credit invoke, builder registration, endpoint create/invoke/receipt/logs/revenue/events/payout settings, endpoint secrets, unsafe handler blocking, pause, and cleanup.

Hosted provider tests passed 11/11 allowed services, 6/6 blocked-service safety checks, and 2/2 fallback checks. Streaming proofs passed for Midjourney, Kling, and Suno.

The latest conversion matrix passed 37/37 planning quote checks and 4/4 executable handoff checks for Base, Ethereum, and Solana assets toward the Seedream image-generation settlement amount. Tiny live-money proofs passed for external x402 seller settlement, direct fresh-wallet buyer payment, and builder payout settlement.

The native facilitator rail is now exposed through a public proof bundle with supported rails, a sample payment requirement, reconciliation summary, and public-safe receipt metadata. The recurring rail parity check currently passes 16/16 public checks.