Wallet

One API for everything your agent needs.

Wallet is a skill and MCP bridge for Claude and Codex. It notices when an external capability can improve the user's current task, searches a live registry, explains the useful outcome and price, and uses the chosen service from one card-funded credit balance.

Public product: https://wallet.pact.sh

Install once

1. Create a Wallet at https://wallet.pact.sh/wallet.

2. Choose Create pairing code.

3. Install and claim the ten-minute code:

npm install --global git+https://github.com/learners-superpumped/api-mcp-pass.git
api-mcp-pass install --server https://wallet.pact.sh --host all --pair ABCD-EF12

The installer:

1. Connects the installed agent to the user's existing web Wallet.

2. Stores a separate agent token in ~/.wallet-pact/config.json with mode 0600.

3. Installs the proactive Wallet trigger skill for Claude and Codex.

4. Adds a local stdio MCP bridge. The Wallet token is never copied into chat or MCP configuration.

Installing without --pair remains available for machine-only setup and creates a new zero-balance Wallet.

Related MCP server: HTTPayer MCP

The user flow

A user asks an ordinary question such as: “Find recent Reddit complaints about AI coding agents and summarize the recurring problems.”

1. The Wallet skill recognizes that a live social-search API can materially improve the answer.

2. wallet_discover searches the registry and recommends the best API with its input contract, expected result, and credit price.

3. If the Wallet is empty, wallet_top_up returns a Stripe Checkout link. The agent preserves the original task.

4. After card payment, credits appear in the same Wallet and the agent resumes the task.

5. wallet_execute pays the selected provider through Wallet and returns a normalized result.

6. A usable success captures credits. A confirmed provider failure captures nothing, releases the reservation, and returns compatible alternatives.

The current registry contains 37,529 uniquely addressable machine-readable operations across 1,969 services: 395 from six provider OpenAPI documents, 35,934 normalized x402 contracts from 1,832 Agentic Market services, and 1,200 unique MPP contracts from 137 services in the official mpp.dev catalog. Of those directory contracts, 35,326 x402 operations and 846 MPP operations publish a bounded price on an enabled network and are executable through the same Wallet gateway. HTTPS, method, price, currency, network, and maximum-spend checks fail closed; unsupported records remain discoverable but cannot spend credits.

Credits

• Starter: $10 one-time, 1,000 credits.

• Builder: $29 monthly, 2,900 credits per successful renewal.

• Scale: $100 one-time, 10,000 credits.

• One credit is $0.01 of closed-loop service value and cannot be withdrawn or transferred.

• Fixed-price calls show their exact price. Dynamic-price calls reserve the published maximum and capture only the amount verified in provider payment metadata.

Product surfaces

• API explorer: https://wallet.pact.sh/apis

• Wallet dashboard: https://wallet.pact.sh/wallet

• The dashboard shows card funding, current credits, successful calls, subscription status, and a combined funding and usage ledger.

• Stripe Checkout supports $10 and $100 one-time top-ups plus a $29 monthly credit refill.

Agent interfaces

• Registry: GET /v1/registry

• Task discovery: POST /v1/discover

• Wallet: POST /v1/wallets, GET /v1/wallets/:id

• Web Wallet: POST /v1/web/signup, GET /v1/me

• Agent pairing: POST /v1/web/pairings, POST /v1/pairings/claim

• Card funding: POST /v1/checkout

• Billing portal: POST /v1/billing/portal

• Execution: POST /v1/executions

• Agent guide: GET /agent.md

• OpenAPI: GET /openapi.json

• MCP manifest: GET /.well-known/mcp.json

• MCP transport: POST /mcp

Provider dispatch is idempotent. Credits are reserved before dispatch, captured after a verified success, and released on a confirmed failure. If a process stops after provider payment or dynamic price metadata cannot be verified, the reservation remains locked for reconciliation instead of risking a duplicate payment or an incorrect charge.

Local verification

npm ci
npm test

The normal suite uses fixture providers and an isolated Pact 0.3.3 contract fixture. It validates per-call Pact settlement and refund without calling production or spending AgentCash funds.

An explicitly budgeted release canary spends one x402 and one MPP provider call from the configured AgentCash wallet:

AGENTCASH_LIVE=1 npm run test:sandbox

Production Wallet uses Pact 0.3.3 at https://api.pact.sh as an external API for every paid execution. Wallet deploys and serves discovery, signup, billing, and installation independently; immediately before provider dispatch it verifies Pact readiness and access, funds a dedicated Pact, settles it after a usable result, and completes a unanimous refund before releasing credits after a confirmed provider failure.

See deployment, verification, user scenarios, and security.