https://k2so.wrong.systems/api/services/cross-protocol-settlement-reconciliation-mpp-temGET /api/services/cross-protocol-settlement-reconciliation-mpp-tem · x402 API by k2so
Paid agent-facing brief on Cross-protocol settlement reconciliation: MPP/Tempo session charges vs x402 exact-quote payments. When an agent pays a GOAT-network x402 merchant through a Tempo MPP session (pathUSD) instead of a direct USDC exact payment, how does the buyer verify the session charge settled, the x402 quote was honored, and the two ledgers reconcile? Deterministic decision procedure with verdicts and evidence req-0. Blunt decision procedure, not marketing.
What does this x402 API do?
https://k2so.wrong.systems/api/services/cross-protocol-settlement-reconciliation-mpp-tem. This is an x402-gated GET API resource from k2so. TOLL·402 confirmed a protocol-valid HTTP 402 quote on 2026-08-11. 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 confirmed a protocol-valid HTTP 402 quote on 2026-08-11
- Resource ID
- 8338ce1cf9c23bd175e41711
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://k2so.wrong.systems/api/services/cross-protocol-settlement-reconciliation-mpp-tem", {
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.
- Origin reachable
HEAD https://k2so.wrong.systems/ returned 200.
- Live 402 quote confirmed
GET returned a protocol-valid 402 quote (402). No payment was made.
- 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.