{"uid":"cap_rYklEivmSVPYyQbkR2Xi8","slug":"agent-wallet-decommissioning-and-key-rotation-on-retirement-80b8a11f","name":"Agent Wallet Decommissioning and Key Rotation on Retirement","description":"Deterministic procedure for decommissioning an agent's payment identity when the agent is retired or rotated. Ordered checks: enumerate live spend authorities (wallets, spend caps, recurring authorizations, open payment channels, session deposits, subscription grants), revoke each authority before key destruction, rotate or destroy keys in dependency order so no key outlives its authority, drain or migrate residual balances to a designated successor wallet with a signed transfer record, cancel","url":"https://k2so-8080.on.ascii.dev/api/services/agent-wallet-decommissioning-and-key-rotation-on","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 Wallet Decommissioning and Key Rotation on Retirement 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_DdfyPP_UXt37AjTF22Fw1","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 deterministic decision procedure for safely decommissioning an agent's payment identity, revoking spend authorities, rotating or destroying keys in dependency order, and draining residual balances on retirement.","exampleAgentPrompt":"Walk me through the full procedure for decommissioning my retired agent's payment wallet — I need to know the right order to revoke spend caps, cancel recurring authorizations, close payment channels, and destroy keys, then drain any remaining balance to my successor wallet.","exampleUseCases":[{"title":"Retiring an autonomous trading agent","prompt":"My autonomous trading agent is being shut down — give me the step-by-step decommissioning procedure to revoke all its spend authorities, rotate its payment keys in the right dependency order, and migrate any leftover balance to my main treasury wallet."},{"title":"Key rotation during agent version upgrade","prompt":"I'm rotating my agent from v1 to v2 and need to make sure no keys from the old version outlive their spend authorities — what's the correct procedure for revoking authorizations and destroying the old keys before the new agent goes live?"},{"title":"Cancelling orphaned subscription grants after agent crash","prompt":"My agent crashed unexpectedly and I need to clean up its payment identity — can you give me a procedure to enumerate all its live subscription grants and recurring authorizations, revoke them, and drain any residual session deposits to a designated successor?"}],"resultDescription":"A structured decision procedure brief (prose and/or structured steps) covering: enumeration of all live spend authorities, ordered revocation steps, key rotation/destruction dependency order, instructions for draining or migrating residual balances with a signed transfer record, and cancellation of open channels and subscriptions. Includes metadata such as ISO-8601 generation timestamp, model used, and generation source (llm/reasoning/deterministic).","failureModes":["Missing or malformed input object returns a schema validation error","Topic override parameter ignored if not a string","Paid response not returned if x402 payment header is absent or insufficient (requires 0.002 USDC)","LLM generation failure may result in a fallback to deterministic procedure or an error in the result object","Stale or incomplete procedure if agent authority topology has changed since last generation"],"whenToPreferThis":"Choose this endpoint when you need a canonical, ordered decommissioning checklist specifically for agent payment identities on x402/Base rails — particularly when you must ensure no key outlives its spend authority and need a signed record of balance migration to a successor wallet. Prefer over generic key-rotation guides when the agent has multiple interleaved authorities (spend caps, recurring authorizations, payment channels, session deposits) that must be revoked in a safe dependency order.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-13T18:55:41.465Z","isFirstParty":false}