For developers and partners

Keep your wallet. Add a payment boundary.

Wrap your existing x402 fetch with free guard and settlement reconciliation. For a paid pilot, demonstrate a bounded safety check first, then agree which paid capability your users actually need.

Start the integration

One supported integration

Use the official TypeScript x402 client with a Base wallet and our first-call example. The default run verifies the payment challenge without paying; explicit paid mode allows exactly 0.001 USDC.

Download the integration demo

For payment protection: npm install @usesaferoute/x402@^0.18.1 @x402/core@^2.21.0

import { createGuardedX402Fetch } from "@usesaferoute/x402";
const safeFetch = createGuardedX402Fetch({
  payer: wallet.address,
  paymentFetch: existingX402Fetch,
  policy: { maxAmountAtomic: "1000000", allowedHosts: ["merchant.example"] }
});

Supply your existing wallet-bound payment fetch. Do not use this example as permission to pay an arbitrary merchant.

Read the integration contract

A pilot with a measurable outcome

Agree one supported flow, verify a delivered result, then measure independent repeat use. A free guard install is not a paid conversion. Eligible paid service fees can accrue the existing 25% partner share.

Discuss your integration

Paid settlement, delivered service result, and later trade execution are separate outcomes.