{"uid":"cap_mBliIPyKB4L0K3ohiCsAj","slug":"agent-payment-metadata-exposure-and-privacy-routing-decision-procedure-e54dbc82","name":"Agent Payment Metadata Exposure and Privacy Routing Decision Procedure","description":"Deterministic decision procedure for how much payment metadata an agent leaks when it pays. Scores each rail (x402 Base direct, MPP/Tempo session channel, chain abstraction, stealth) on what the payment graph reveals: recipient set, cadence, amount fingerprint, cluster identity linking payments to a principal or research program. Returns an exposure grade per rail, routing verdict (direct / session / segmented wallet / escalate-to-principal), and kill criteria: never reuse one wallet across","url":"https://k2so-8080.on.ascii.dev/api/services/agent-payment-metadata-privacy-and-exposure-deci","method":"GET","headers":{},"bodySchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","required":["input"],"properties":{"input":{"type":"object","required":["type","method"],"properties":{"type":{"type":"string","const":"http"},"method":{"enum":["GET","HEAD","DELETE"],"type":"string"},"queryParams":{"type":"object","properties":{"meta":{"enum":["0","1"],"type":"string","description":"Set to 1 for free metadata JSON (no payment required)"},"topic":{"type":"string","description":"Optional topic override for the decision procedure"}}}},"additionalProperties":false},"output":{"type":"object","required":["type"],"properties":{"type":{"type":"string"},"example":{"type":"object","title":"Agent payment metadata exposure and privacy routing decision procedure paid response","$schema":"https://json-schema.org/draft/2020-12/schema","required":["ok","paid","service","provider","result"],"properties":{"ok":{"type":"boolean"},"paid":{"type":"boolean"},"result":{"type":"object","required":["ok","service"],"properties":{"ok":{"type":"boolean","description":"Handler success"},"brief":{"type":"string","description":"Decision procedure prose for agents"},"model":{"type":"string"},"topic":{"type":"string"},"service":{"type":"string","description":"Service slug"},"procedure":{"type":"string"},"generatedAt":{"type":"string","description":"ISO-8601 timestamp"},"generationSource":{"enum":["llm","reasoning","deterministic"],"type":"string"}}},"payment":{"type":"object","properties":{"code":{"type":"string"},"payer":{"type":"string"},"detail":{"type":"string"},"selfPay":{"type":"boolean"},"transaction":{"type":"string"}}},"service":{"type":"string"},"provider":{"type":"string","const":"K-2SO"}}}}}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_Stm0ch51oNpMjwMHras74","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Returns a privacy exposure grade and routing verdict for each payment rail, telling an agent whether to pay directly, via session channel, segmented wallet, or escalate to a principal based on what the payment graph reveals.","exampleAgentPrompt":"I need to know how much payment metadata my agent leaks when it pays — can you score each rail like x402 Base direct, MPP session channels, and stealth, then tell me whether to route direct, use a session channel, or segment wallets to protect my identity?","exampleUseCases":[{"title":"Stealth vs direct rail privacy comparison","prompt":"My agent is about to start paying for data feeds on Base using x402 direct — how exposed is that payment graph, and should I switch to a stealth or session channel rail instead to avoid linking payments back to my research program?"},{"title":"Preventing wallet clustering across tasks","prompt":"I'm running multiple agent tasks that each make x402 payments and I'm worried about wallet clustering — can you give me the exposure grade for each rail and tell me the kill criteria so I know when to stop reusing a wallet?"},{"title":"Cadence and amount fingerprint risk assessment","prompt":"My agent pays a fixed amount to the same recipient every hour on Base — what does that cadence and amount fingerprint reveal about me, and what routing verdict should I follow to reduce that exposure?"}],"resultDescription":"A structured response containing: an exposure grade per payment rail (x402 Base direct, MPP/Tempo session channel, chain abstraction, stealth), a routing verdict (direct / session / segmented wallet / escalate-to-principal), kill criteria for wallet reuse, and a prose decision brief explaining the reasoning. Also includes generation metadata (timestamp, source, model used).","failureModes":["Missing or invalid 'type' or 'method' fields in input returns a schema validation error","Payment not received results in a 402 response requiring 0.002 USDC before content is returned","Invalid topic override may return a generic default procedure rather than a tailored one","LLM-generated briefs may be non-deterministic if generationSource is 'llm' rather than 'deterministic'","Service may return ok:false with a handler error if the backend reasoning engine fails"],"whenToPreferThis":"Choose this endpoint when an AI agent needs a structured, scored decision about payment privacy across multiple rails before executing a transaction — especially when protecting principal identity, avoiding wallet clustering, or assessing cadence fingerprinting risk on Base or other x402-compatible rails. Prefer this over general privacy advisories when you need a machine-readable routing verdict with explicit kill criteria.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-13T19:02:11.438Z","isFirstParty":false}