{"uid":"cap_7szUwjRDpzy4kt7t23Nol","slug":"replenishment-timing-string-normalisation-duplicate-key-report-65d46aaa","name":"Replenishment Timing String Normalisation + Duplicate Key Report","description":"Replenishment timing — String normalisation + Duplicate key report: String normalisation + Duplicate key report for supplied replenishment timing records (lead_days, received_units). Up to 200 rows; 2 independent reports using shared local analytical engines. No live lookup, prediction, professional assessment or external action. 0.01 USDC includes 2 supplied-data reports for up to 200 rows.","url":"https://market.datapackvibe.com/x402/assistant-ib26-retail-12-021?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"rows":{"type":"array","items":{"type":"object","required":["row_id","store_group","date","lead_days","received_units"],"properties":{"date":{"type":"string","default":"","pattern":"^\\d{4}-\\d{2}-\\d{2}$","maxLength":10},"row_id":{"type":"string","default":"","maxLength":80,"minLength":1},"lead_days":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000},"store_group":{"type":"string","default":"","maxLength":80},"received_units":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000}},"additionalProperties":false},"default":[{"date":"2026-10-01","row_id":"row-1","lead_days":10,"store_group":"group-a","received_units":1},{"date":"2026-10-02","row_id":"row-2","lead_days":20,"store_group":"group-b","received_units":2},{"date":"2026-10-03","row_id":"row-3","lead_days":15,"store_group":"group-a","received_units":3},{"date":"2026-10-04","row_id":"row-4","lead_days":30,"store_group":"group-b","received_units":4}],"maxItems":200,"minItems":1}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","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.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_32B5iwfHq5IIdGHkpk2mD","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Runs string normalisation and duplicate key detection on up to 200 replenishment timing records (lead_days, received_units) and returns two independent analytical reports.","exampleAgentPrompt":"Can you check my replenishment timing records for duplicate row keys and normalise the string fields? I have up to 200 rows with fields like row_id, store_group, date, lead_days, and received_units — I need both the duplicate key report and the string normalisation report back.","exampleUseCases":[{"title":"Pre-analysis data quality check","prompt":"Before I run my replenishment analysis, can you scan these 150 store replenishment rows for duplicate row IDs and fix up any inconsistent string formatting in the store_group field? The rows have date, lead_days, and received_units columns too."},{"title":"Retail inventory data clean-up","prompt":"I've got a messy export of replenishment timing records from our retail system — about 80 rows with store_group, lead_days, and received_units. Can you flag any duplicate keys and normalise the text fields so the data is consistent?"},{"title":"Supply chain audit before reporting","prompt":"We're preparing a weekly supply chain report and need to verify the replenishment data first. Can you run a duplicate key check and string normalisation on these 200 replenishment records with lead_days and received_units before we proceed?"}],"resultDescription":"Two independent reports: (1) a string normalisation report highlighting inconsistent or non-standard string values in fields like store_group, and (2) a duplicate key report identifying rows sharing the same key fields within the submitted dataset of up to 200 records. No external lookups or predictions are made.","failureModes":["More than 200 rows submitted — request rejected or truncated","Missing required fields (row_id, date, store_group, lead_days, received_units) cause row-level errors","Invalid date format (not YYYY-MM-DD) fails schema validation","Numeric values outside allowed range rejected","Empty rows array returns an error"],"whenToPreferThis":"Choose this endpoint when you need to simultaneously check for duplicate row keys and normalise string fields in replenishment timing data (lead_days, received_units) in a single low-cost call. It is purpose-built for retail supply chain records and offers both reports for $0.01 USDC per call with no external dependencies or live lookups.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-11-02T18:36:43.851Z","isFirstParty":false,"canonicalSlug":"replenishment-timing-string-normalisation-duplicate-key-report-65d46aaa"}