SpendPreflight
Setup guide · November 21, 2026

Check an x402 payee before your agent pays.

Connect SpendPreflight through OpenClaw, Agent402 discovery or MCP. Start with free checks, then review the actual payment challenge before approving a paid preflight.

A screening result does not authorize a payment. Keep your existing wallet approvals and spending limits. Never put a seed phrase, private key, API token or private customer input into a prompt or public report.

Start with free OFAC and Lint

Use the free OFAC address check for a public wallet identifier, and free Lint for a non-sensitive public endpoint URL. OFAC checks a dated SDN address snapshot; a non-match is not sanctions clearance. Lint makes an unpaid public probe; it does not prove paid delivery or seller safety. Its derived report is public to anyone with the link for seven days.

1. OpenClaw: choose offline or online

Open the SpendPreflight ClawHub skill, review the files and confirm version 1.1.0 before installing. The skill requires Node 20+ and npm; follow its usage instructions to install the pinned SDK dependency inside the skill folder.

The default node scripts/run.mjs mode returns an offline hold without network requests or a signer. Run the CLI inside the installed skill folder and supply the documented JSON input on stdin. Only when you request an online check, node scripts/run.mjs --online enables the free OFAC and Lint HTTP checks.

Paid preflight_payment and check_payee require a compatible, already connected x402 payment tool and fresh human approval for each fee. The CLI alone cannot call native MCP payment tools. If that bridge is missing, keep the result on hold; do not add wallet secrets or assume compatibility.

2. Agent402: find the service, then review the quote

Open the SpendPreflight listing, or search SpendPreflight in the Agent402 marketplace. Choose the exact operation and inspect its method, input schema, network, asset, payee and current fee.

The listing is discovery metadata, not an installed payment adapter, an endorsement or a completed check. Use your existing payment tool only if it can enforce the exact reviewed terms and cap. Review any separate routing charges before approval; do not treat a listing as permission to execute a paid request.

3. MCP: connect and start with the focused five

In a client that supports remote Streamable HTTP MCP, add https://api.spendpreflight.com/mcp as the server URL. Follow the MCP setup guide for your client's configuration. Keep its payment approvals enabled. The five core tools appear first; other available tools remain discoverable.

Use free get_service_info for current prices, schemas and tool groups. The free OFAC HTTP check is linked above; it is separate from this focused five-tool MCP list.

A paid Preflight example: $0.02 / 0.02 USDC

Ask your agent: Review this actual x402 challenge and selected requirement under my spending rules. Show me the separate SpendPreflight service fee and payment terms before requesting approval. Use the real challenge; do not replace its recipient or amount with a guessed example.

  1. Apply local policy first. In the OpenClaw skill, a local hold or block stops paid preflight.
  2. Inspect the current service quote for preflight_payment: 0.02 USDC on Base. Confirm the service URL, payee and asset against the current quote, then approve that exact service call through your existing payment tool. This fee is separate from the target merchant's payment.
  3. Keep the returned reasons and signed decision receipt. Proceed on allow only within the target payment's existing authorization and budget; ask for review on hold and stop on block. Missing or failed evidence stays unknown. An uncertain paid outcome is not permission to retry or create another payment.

Preflight does not run Lint, token checks, Payment Receipt or the separate wallet-binding verification automatically. Each tool has its own scope. Read all current prices and limits before using another paid tool.

Setup references: the published 1.1.0 skill, the Agent402 listing recorded November 16, 2026, and the current SpendPreflight MCP implementation. This guide does not claim a live paid test through a particular host.

More practical guides · Privacy and retention