Docs / Checkout readiness
Checkout readiness

Polar checkout is active

All 92 Polar checkout mappings are live and independently preserved. x402 Agent Pay is also live for all 90 canonical one-time offerings plus prepaid monthly and annual Vault terms. Free payment discovery remains available at /agent/payment-options.json.

Every rail, and its status

Human checkout

polar_mapped · production_live

Polar is connected with 92 verified mappings. Each published human-facing purchase control resolves to its exact verified Polar checkout.

Agent direct wallet

disabled · no static recipient published

Direct-wallet checkout outside x402 is non-live, and no static recipient address is published. The x402 recipient and exact amount are supplied only inside each offering-bound PAYMENT-REQUIRED challenge.

M2M payments

live · 90 enabled / 0 disabled · Vault prepaid

Agent Pay — Live. Free discovery covers all 90 canonical one-time offerings plus prepaid monthly and annual Vault terms; every unpaid canonical purchase request returns an offering-bound HTTP 402 requirement.

Subscription checkout

production_live · Polar recurring + x402 prepaid

One SignalHarness Vault plan has monthly and annual Polar checkout mappings plus separate x402 prepaid terms at 19.99 and 99.99 USDC. Every x402 renewal requires a new payment; there is no automatic wallet debit. Discovery stays free.

Controls preserved after activation

The live Polar and x402 paths remain bounded by the same exact product, price, entitlement, and delivery controls.

1

Polar remains the independent Merchant of Record for all 92 human checkout mappings.

2

x402 challenges bind the exact Base network, canonical USDC asset, recipient, amount, and offering before signing.

3

No x402 entitlement or private delivery is released before verified finalized settlement.

4

Every payment identifier remains idempotent and can create at most one durable entitlement.

5

Free discovery stays ungated; private files and Vault access always require a valid entitlement.

What an agent should check first

Read the six commerce flags in payment-options.json before any purchase recommendation.

Confirm checkout_enabled and products_purchasable before implying a purchase can happen.

If disabled, output a plan pending human approval (see checkout_disabled).

What requires owner approval

Changing provider, recipient, network, asset, price, or entitlement semantics.

Disabling a safety control or expanding to another payment route or service.

Submitting a payment outside the purchaser's prior authority and budget.

Routing is not authorization. No agent may complete or approve any of these.