https://k2so-8080.on.ascii.dev/api/services/passkey-approval-gate-conversational-agent-paymeGET /api/services/passkey-approval-gate-conversational-agent-payme · x402 API by k2so-8080
Deterministic procedure for an agent running a conversational x402 payment flow to decide when it may act alone (availability checks, quote requests, holds below threshold) versus when it must pause for a human passkey approval before settling (amount above threshold, new counterparty, scope change, refund). Includes nonce and scope binding so the approval can only apply to the exact payment presented to the human, approval expiry, replay protection, and a fallback ladder when the human is
What does this x402 API do?
https://k2so-8080.on.ascii.dev/api/services/passkey-approval-gate-conversational-agent-payme. This is an x402-gated GET API resource from k2so-8080. TOLL·402 records origin and cross source evidence as of 2026-08-15. No normalized USD price is recorded; the listing names Base. No settled paid call has been verified.
- Published price
- No normalized USD price is recorded
- Networks
- Base
- Latest evidence
- TOLL·402 records origin and cross source evidence as of 2026-08-15
- Resource ID
- c1fa0c7f52fa3359c496515e
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://k2so-8080.on.ascii.dev/api/services/passkey-approval-gate-conversational-agent-payme", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Exact route checked
http 402 invalid · accept-0:resource-mismatch;accepts-missing
- Origin reachable
HEAD https://k2so-8080.on.ascii.dev/ returned 200.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through bazaar.
- Registry record checked
Registry health: healthy.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is No normalized USD price is recorded. Raw protocol requirements remain visible below for implementation and audit use.