{"uid":"cap_FRn1pHVoxWN6X3veHmuNT","slug":"apiosk-gateway-data-clean-execute-e65cf383","name":"Apiosk Gateway – data-clean 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/data-clean/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_InGZUi6yJMT1C_6fw_QqE","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":"Execute a data cleaning operation via the Apiosk pay-per-call gateway using the x402 (HTTP 402 + USDC on Base) micropayment protocol.","exampleAgentPrompt":"Clean and normalize this JSON payload of customer records using the data-clean service — run the 'normalize' operation on it: {\"records\":[{\"name\":\"john doe\",\"email\":\"JOHN@EXAMPLE.COM\",\"phone\":\"5551234567\"}]}.","exampleUseCases":[{"title":"Normalize customer contact records","prompt":"I have a batch of customer records with inconsistent casing, phone formats, and email addresses — can you run them through data-clean's normalize operation to standardize everything? Here's the JSON: {\"records\":[{\"name\":\"JANE SMITH\",\"email\":\"Jane@Example.com\",\"phone\":\"(555) 987-6543\"}]}."},{"title":"Sanitize user-submitted form data","prompt":"Before I store this user registration form submission, run it through the data-clean execute endpoint using the 'sanitize' operation to strip any invalid or malformed fields: {\"name\":\"  Bob \",\"email\":\"bob@@mail.com\",\"zip\":\"9999X\"}."},{"title":"Validate and clean exported database rows","prompt":"I just exported some rows from our legacy database and they have a lot of formatting issues. Use the data-clean service with the 'validate' operation to flag and fix bad entries in this JSON payload: {\"rows\":[{\"id\":\"001\",\"date\":\"13/32/2023\",\"amount\":\"$1,200.00\"}]}."}],"resultDescription":"Returns a JSON object with a status string, the cleaned/transformed result from the upstream data-clean provider, the operation used, the API slug, latency in milliseconds, cost string, and the upstream HTTP status code.","failureModes":["Invalid or malformed JSON in the 'input' field returns an error status","Unknown or unsupported operation ID results in upstream 404 or error","Payment failure via x402 protocol if USDC balance is insufficient","Upstream data-clean service timeout or unavailability reflected in upstream_status","Malformed operation selector (wrong METHOD /path format) causes routing failure"],"whenToPreferThis":"Choose this endpoint when you need to clean, normalize, sanitize, or validate structured JSON data and want a pay-per-call model with no subscription — especially when integrating into an agent workflow that pays micropayments via USDC on Base (x402 protocol). Prefer it over a full ETL pipeline service when the cleaning task is small, on-demand, and cost-sensitive.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-13T12:48:43.367Z","isFirstParty":false}