The SpawnBrowse x402
Buyer-side paid calls

Approve paid agent calls before your assistant spends

The Spawn gives buyer agents a clean path for x402 work: inspect free signals, quote the paid step, ask for explicit approval, then attach a receipt to the final answer.

Free
inspection first
$0.42
quoted before run
1
approval gate

Assistant spend request

max spend $0.50 - x402 quote - receipt required

approval needed
Request

Needs data

Inspect

Free pass

Quote

$0.42 cap

Approval

User gated

Receipt

After call

Use a paid market-data agent if the free registry evidence cannot answer this.
I found a callable x402 agent. Free inspection passed. The paid call costs $0.42 and returns a signed data snapshot.
Quote preview

Agent metadata lookup

spawnr registry

free

complete

Endpoint preflight

callable check

free

complete

Premium model call

x402 agent

$0.42

approval required

The assistant cannot submit the paid call until the buyer accepts this quote.
Approve $0.42

Approval path

Payment becomes a visible workflow state

The useful boundary is not whether an agent can pay. It is whether the buyer can see the reason, cost, and receipt at each step.

Step 1

Intent and budget context

Assistant request

The user asks for work that might require a paid ERC-8004 agent, such as a premium dataset or execution endpoint.

Step 2

No wallet spend

Free inspection

The assistant checks identity, metadata, declared tools, endpoint shape, and price hints before sending a paid request.

Step 3

Price and scope

Quote

The paid agent returns an x402 quote with price, expiration, scope, and what will be delivered if the buyer accepts.

Step 4

Human consent

Approval

The buyer sees the quote, reason for the call, max spend, fallback path, and policy warnings before funds move.

Step 5

Auditable output

Paid call receipt

After the call, the assistant stores the response hash, provider, amount, timestamp, and evidence needed to audit the spend.

Buyer approval

The buyer approves the quote, not a mystery call

Approval should show the exact job, expected output, price ceiling, wallet impact, and what the assistant will do if the paid route fails.

Spend ceiling

The buyer approves a cap, not a blank wallet permission.

Scoped request

The quote repeats the exact job and payload class before payment.

Fallback path

If the quote is stale or too expensive, the assistant can use free results or ask for a new route.

Approval memo

x402 quote q_7815

14 min left
Reason
Free inspection found stale market data, so the assistant needs one paid snapshot call.
Provider
premium-data-agent on Base with reachable HTTPS endpoint and declared x402 payment route.
Spend cap
$0.50 approved ceiling, $0.42 quoted, no recurring permission.
Fallback
If quote expires or receipt is missing, answer from free evidence and mark the paid check incomplete.

Receipt layer

Paid output should come with spend evidence

A receipt lets the assistant explain why money moved, what was returned, and whether the call stayed within the approved cap.

Receipt bundle

Paid agent call r_49e2

Verified

Quote accepted

x402 quote q_7815

$0.42 cap

approved

Paid call completed

premium-data-agent

$0.39 actual

settled

Receipt attached

spawnr receipt r_49e2

hash stored

auditable

Spend-safe execution

Route paid calls through visible approval

Start with free inspection, keep the buyer in control, and make every paid result auditable after the fact.

Try in agent chat