{"uid":"cap_tRQDa6GcBuEY6e1Pg2lvU","slug":"apiosk-gateway-crypto-sanity-execute-e04454f6","name":"Apiosk Gateway – Crypto Sanity Execute","description":"Pay-per-call API gateway on the x402 protocol (HTTP 402 + USDC on Base). This document covers the gateway's discovery and execution meta-endpoints. Individual provider APIs are reachable at /{api_slug}/{path} and described by GET /{api_slug}/metadata.","url":"https://gateway.apiosk.com/crypto-sanity/execute","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"input":{"type":"string","description":"JSON payload forwarded to the selected operation."},"operation":{"type":"string","description":"Operation id, /path, or METHOD /path selector."}}},"responseSchema":{"type":"object","required":["status","result"],"properties":{"api":{"type":"string"},"cost":{"type":"string"},"result":{"description":"Upstream response body."},"status":{"type":"string"},"latency":{"type":"number"},"operation":{"type":"string"},"upstream_status":{"type":"integer"}}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.023","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.02/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.02","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.02","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_5bC0U-cwXglUOS2DcMJFk","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.02","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Executes a crypto-sanity check operation via the Apiosk pay-per-call x402 gateway, forwarding JSON payloads to the upstream crypto-sanity API and returning structured results.","exampleAgentPrompt":"Run a crypto sanity check on this wallet address '0xAbC1234...' using the crypto-sanity execute operation — I want to know if it passes validation before I proceed with the transfer.","exampleUseCases":[{"title":"Pre-transfer address validation","prompt":"Before I send funds, run a crypto sanity check on the destination address '0x742d35Cc6634C0532925a3b8D4C9b0F1E2A3B4C5' and tell me if it looks legitimate."},{"title":"Screening crypto entity in onboarding","prompt":"I'm onboarding a new business partner — can you run a sanity check on their crypto wallet '1A1zP1eP5QGefi2DMPTfTL5SLmv7Divf' using the crypto-sanity API and flag anything suspicious?"},{"title":"Automated payload integrity check","prompt":"Before we publish this crypto transaction payload, sanity-check it with the crypto-sanity execute endpoint using operation 'validate' and input '{\"address\":\"0xDeF456...\",\"chain\":\"base\"}' — I need to confirm it's well-formed and passes all checks."}],"resultDescription":"Returns a JSON object containing status (pass/fail/error string), the upstream response body in 'result', the operation echoed back, HTTP status from upstream, latency in milliseconds, the API slug, and cost of the call in USDC.","failureModes":["Invalid or missing operation selector returns error status","Malformed JSON in input field causes upstream rejection","Unrecognized crypto address format may return validation failure","Network timeout to upstream crypto-sanity service returns latency error","Insufficient USDC balance or payment failure blocks execution via x402 protocol","Upstream service downtime results in non-200 upstream_status"],"whenToPreferThis":"Choose this endpoint when you need to programmatically validate or sanity-check cryptocurrency addresses, identifiers, or payloads before executing transactions or onboarding entities, especially when operating in a pay-per-call agent workflow using USDC micropayments via the x402 protocol. Prefer this over manual checks or broader compliance APIs when lightweight, fast, per-call billing is preferred and the use case is specifically crypto data integrity rather than full AML/KYC screening.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-15T00:56:49.399Z","isFirstParty":false}