callx402 MCP server

Payload — Developer infrastructure for x402, agent payments, and programmable revenue.

PAYLOAD → VEYLINE (flagship) → CALLX402 (action layer) → REVRULE (separate) → developer products → free utilities.

This repo: callx402 by Payload — the universal action layer into Veyline's x402 infrastructure.

callx402 by Payload

Powered by Veyline. When x402 breaks, callx402.

callx402 is the universal action layer into Veyline's x402 infrastructure. Say what you need done in plain language (or hit an HTTP endpoint) and callx402 routes it to the production system that does the real work: diagnose a broken x402 payment, rescue a failed transaction, route an agent job to the cheapest viable path, resolve settlement state from on-chain evidence, or execute under an explicit budget with fail-closed safety rules.

Why it exists: x402 failures are expensive and opaque. A settlement attempt ends in settlement_pending and nobody knows whether the money moved. A 402 response your wallet misreads. A retry that signs a second authorization for the same intent and pays twice. callx402 exists for exactly those moments: diagnose pins the failure to a stage, rescue triages the incident, resolve settles the question from evidence, route finds the cheapest viable path, execute runs under a hard budget.

Try it (two minutes, no setup, no account):

npm install -g callx402

callx402 status callx402 'complete this job for under $1'

status prints an honest per-subsystem reachability report, no credentials needed. The intent line parses and plans your request, then stops before executing anything: with no live tool endpoint wired it reports "no executable route available", so no money moves. (Use single quotes: in double quotes your shell would eat the $1.)

Free read-only checks against the live Payload rail:

curl https://payload-rail.fly.dev/v1/callx402/actions

curl 'https://payload-rail.fly.dev/v1/callx402/quote?action=diagnose'

The first returns the paid action catalog with prices; the second returns a free price quote for one action. Invoking a rail action is paid per action via checkout (see https://payloadhq.github.io/agents.json); these commands never pay anything.

If it saves you one debugging session, star the repo and read on.

MCP server: connect in 60 seconds

This repo ships a zero-dependency, read-only MCP server (mcp/index.js, node stdlib only, stdio transport) exposing six x402_* diagnostic tools. Nothing here charges, executes, retries, or repays.

git clone https://github.com/Payloadhq/callx402

no npm install needed for the MCP server

Add this block to your MCP client config (replace the path), then restart the client:

{

"mcpServers": { "callx402": { "command": "node", "args": ["/absolute/path/to/callx402/mcp/index.js"] } } }

Ask the client to list its MCP tools: the six x402_* tools should appear. Per-client notes and the raw stdio test handshake: integrations/mcp-clients/.

Note: all six free MCP tools respond on a clean npm install using conservative local, read-only assessment of supplied evidence. Without an authoritative source they do not verify settlement, access a private ledger, or execute recovery. Existing configured local/remote subsystem integrations remain available.

The relationship

• PAYLOAD = the parent company.
• VEYLINE = production infrastructure for x402 + MCP. The flagship brand.
• CALLX402 BY PAYLOAD = the x402 response/action layer, powered by Veyline. The entry action into Veyline's production infrastructure, not the flagship name. Nothing here renames Veyline.

Discovery path: a developer searching for x402 finds callx402, uses it, and learns Veyline. Payload is not affiliated with the x402 Foundation.

What it does

• Diagnose an x402 or MCP failure
• Rescue a failed transaction (auth-gated)
• Route a paid agent job to the cheapest viable path
• Resolve settlement state from on-chain evidence
• Execute under an explicit budget, with fail-closed safety rules

Behavioral usage language (not trademark claims):

• "Need to diagnose x402? callx402."
• "Need to rescue a transaction? callx402."
• "Need to route a paid agent job? callx402."
• "Need settlement certainty? callx402."
• "Need to execute under a budget? callx402."

Quickstart

1. Install

npm install -g callx402

Or locally in a project: npm install callx402 (the binary is then at node_modules/.bin/callx402).

Fallback, install direct from GitHub:

npm install Payloadhq/callx402

Local development:

git clone https://github.com/Payloadhq/callx402

cd callx402 npm install npm link # exposes the callx402 command

2. First run: what works with zero setup

callx402 status

callx402 'complete this job for under $1'

status is the honest starting point: a per-subsystem reachability report. On a bare npm install it reads 0/15 subsystems reachable, which is expected (see step 3). The intent line plans in plain language and stops before execution, so it is always safe to run; use single quotes so your shell does not eat $1.

Free read-only checks against the live Payload rail (no account, no keys):

curl https://payload-rail.fly.dev/v1/callx402/actions

curl 'https://payload-rail.fly.dev/v1/callx402/quote?action=diagnose'

These return the paid action catalog with prices and a free price quote for one action. Invoking a rail action is paid per action via checkout (machine front door: https://payloadhq.github.io/agents.json); nothing here pays anything.

3. Self-hosted runtime (advanced, optional)

By default every subsystem command routes to the hosted rail — no setup needed. If you prefer to run everything on your own machine, set CALLX402_LOCAL=1 and point CALLX402_V2_ROOT at the v2.0.0 tree (the x402 Paid API Starter Kit, a separate product):

export CALLX402_LOCAL=1

export CALLX402_V2_ROOT=/path/to/x402-paid-api-starter-kit/v2.0.0 callx402 status # now: 15/15 reachable, 0/15 enabled

Without CALLX402_LOCAL=1, these commands use the hosted rail instead — that is the standard path and needs nothing installed beyond the npm package.

(The default is a x402-paid-api-starter-kit/v2.0.0 directory sitting next to your callx402 checkout.)

Subsystems are disabled by default; status names the flag that enables each one. Set a flag, then run its command:

export PAYLOAD_MCP_DOCTOR=1

callx402 diagnose --target 'https://api.example.com/x402/pay'

More examples (each needs its subsystem flag enabled; run callx402 status to see the flag names):

callx402 rescue --incident inc_123

callx402 route --goal 'fetch 100 product prices for under 0.50 USD' callx402 resolve --evidence '{"txHash":"0xabc..."}'

Note the single quotes: the goal text contains $-style amounts that a shell would expand inside double quotes.

Alternative to the local tree: run in remote mode against your own callx402 server (server/index.js):

export CALLX402_MODE=remote

export CALLX402_REMOTE_URL=http://127.0.0.1:8787

JavaScript SDK

const { callx402 } = require('callx402');

const result = await callx402({ intent: 'complete this job for under $1', maxBudget: 1.00, networks: ['base'], assets: ['USDC'], approvalThreshold: 5.00, idempotencyKey: 'job-42', });

Python SDK

import callx402

result = callx402.callx402( intent="complete this job for under $1", max_budget=1.00, networks=["base"], assets=["USDC"], approval_threshold=5.00, idempotency_key="job-42", )

HTTP server

CALLX402_PORT=8787 node server/index.js

curl -X POST http://127.0.0.1:8787/call \ -H 'Content-Type: application/json' \ -d '{"intent":"complete this job for under $1","maxBudget":1.00,"dryRun":true}'

Full HTTP surface: server/openapi.yaml (served live at GET /openapi.json).

Commands

Subsystem commands (diagnose, rescue, route, resolve, doctor, monitor, preflight, inspect) need the v2.0.0 tree plus the matching feature flag (see "Full subsystem commands" above); without them they exit 3 and do nothing. status, intent mode, and config work with zero setup.

Execution modes

callx402 works out of the box. There are two modes:

A bare npm install callx402 gives you the hosted mode — no separate tree, no config, no keys. The v2 tree is never required for standard use.

How payment works

Hosted paid actions settle through Payload's signed-redemption flow, not a generic x402 facilitator:

1. Get a free quote for the action: the exact price, before any payment.
2. Call the action and read the x402 v2 402 challenge: USDC on Base, the amount, and the payTo address.
3. Pay the quoted amount to payTo from your own wallet.
4. Redeem the original quote with the paym