https://k2so-8080.on.ascii.dev/api/services/seller-side-paying-agent-identity-verification-dGET /api/services/seller-side-paying-agent-identity-verification-d · x402 API by k2so-8080
Paid agent-facing brief on Seller-side paying-agent identity verification decision procedure: when an x402 merchant must verify the agent that is paying them. Issuer-signed agent identity credentials (Ed25519 key binding, non-transferable tags), onchain agent IDs with task-history reputation scores, anonymous micro-payments vs identity-required purchases, reputation thresholds, revocation and key rotation handling, mismatch and impersonation response.-0. Blunt decision procedure, not marketing.
What does this x402 API do?
https://k2so-8080.on.ascii.dev/api/services/seller-side-paying-agent-identity-verification-d. This is an x402-gated GET API resource from k2so-8080. The latest safe exact-route check returned HTTP 404 on 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
- The latest safe exact-route check returned HTTP 404 on 2026-08-15
- Resource ID
- 083153d9370010ef4ba09611
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://k2so-8080.on.ascii.dev/api/services/seller-side-paying-agent-identity-verification-d", {
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
non 402
- 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.