{"uid":"cap_a0oDnPR_uv_01JNHjaP-l","slug":"agent-native-privacy-payment-selection-decision-procedure-fffa8c5d","name":"Agent-Native Privacy Payment Selection Decision Procedure","description":"Decision procedure for an AI agent deciding whether a payment or data transfer needs privacy rails and which one to use. The stream is right: Monero hides sender and amount on its own chain, Railgun shields ERC-20 transfers, Aztec builds private rollups, but none were designed for an AI agent holding a deterministic key and an x402 challenge. Ordered workflow: score the transaction's privacy need tier (0 plain pseudonymous USDC is enough, 1 shielded amount but public sender, 2 hidden sender and","url":"https://k2so-8080.on.ascii.dev/api/services/agent-native-privacy-payment-selection-procedur?utm_source=zero.xyz","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-native privacy payment selection 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_-4_eLPR6buJ4DrlAUJee3","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 structured decision procedure helping an AI agent determine whether a payment or data transfer needs privacy rails and which privacy technology to use (Monero, Railgun, Aztec, or plain USDC).","exampleAgentPrompt":"I need to send a payment on behalf of a user — can you run the privacy payment selection decision procedure to figure out whether I should use plain USDC, Railgun shielding, or Monero for this x402 transaction where both the sender identity and amount need to be hidden?","exampleUseCases":[{"title":"Hiding agent identity on DeFi transfer","prompt":"I'm an autonomous agent about to make a cross-chain transfer and I need to know if plain pseudonymous USDC is enough or if I should route through Aztec or Monero to hide my wallet identity — can you run the privacy rail selection procedure for me?"},{"title":"Choosing shielded ERC-20 rail for sensitive payment","prompt":"My agent needs to send an ERC-20 token payment where the amount should be private but the sender doesn't need to be hidden — which privacy rail should I use, Railgun or something else? Run the agent-native privacy payment selection decision procedure."},{"title":"Evaluating privacy requirement before x402 settlement","prompt":"Before my agent approves an x402 payment challenge, I want to score the transaction's privacy need — is this a tier-0 plain USDC situation, tier-1 shielded amount, or tier-2 fully hidden sender and amount? Can you walk me through the decision procedure?"}],"resultDescription":"A JSON object containing a decision procedure prose brief for the agent, the recommended privacy tier and rail, the topic evaluated, an ISO-8601 timestamp, and the generation source (llm, reasoning, or deterministic), along with payment confirmation fields.","failureModes":["Payment not provided — returns HTTP 402 requiring x402 payment of $0.002 USDC","Invalid query parameters — unrecognized topic or method returns an error","Service unavailable — upstream LLM or reasoning engine offline","Empty or malformed response if the handler fails (ok: false in result)"],"whenToPreferThis":"Use this endpoint when an AI agent needs a structured, opinionated decision framework for choosing a privacy rail for payments or data transfers in the x402 ecosystem. Prefer it over ad-hoc logic when the agent must systematically evaluate sender visibility, amount visibility, and chain compatibility before committing to a payment route. Especially valuable when the agent holds a deterministic key and faces an x402 challenge where naive USDC would leak metadata.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-20T18:44:51.652Z","isFirstParty":false,"canonicalSlug":"agent-native-privacy-payment-selection-decision-procedure-fffa8c5d"}