{"uid":"cap_NN49vtf5yN970vzh1dSDw","slug":"record-routing-analytics-adjacent-row-changes-secondary-measure-990af3f8","name":"Record Routing Analytics: Adjacent Row Changes + Secondary-Measure Weighted Mean","description":"Record routing — Adjacent row changes + Secondary-measure weighted mean: Adjacent row changes + Secondary-measure weighted mean for supplied record routing records (accepted_records, rejected_records). 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-analytics-19-159?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"rows":{"type":"array","items":{"type":"object","required":["row_id","dataset_group","date","accepted_records","rejected_records"],"properties":{"date":{"type":"string","default":"","pattern":"^\\d{4}-\\d{2}-\\d{2}$","maxLength":10},"row_id":{"type":"string","default":"","maxLength":80,"minLength":1},"dataset_group":{"type":"string","default":"","maxLength":80},"accepted_records":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000},"rejected_records":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000}},"additionalProperties":false},"default":[{"date":"2026-10-01","row_id":"row-1","dataset_group":"group-a","accepted_records":10,"rejected_records":1},{"date":"2026-10-02","row_id":"row-2","dataset_group":"group-b","accepted_records":20,"rejected_records":2},{"date":"2026-10-03","row_id":"row-3","dataset_group":"group-a","accepted_records":15,"rejected_records":3},{"date":"2026-10-04","row_id":"row-4","dataset_group":"group-b","accepted_records":30,"rejected_records":4}],"maxItems":200,"minItems":1},"field":{"enum":["accepted_records","rejected_records"],"type":"string","default":"accepted_records"}}},"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_TFpvj1i3tptBZQITAM0Ky","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":"Computes adjacent row-to-row changes and a secondary-measure weighted mean for up to 200 record routing rows (accepted_records, rejected_records) in two bundled analytical reports.","exampleAgentPrompt":"Can you run the adjacent row changes and weighted mean reports on my record routing data? I have 4 rows: row-1 on 2026-10-01 group-a with 10 accepted and 1 rejected, row-2 on 2026-10-02 group-b with 20 accepted and 2 rejected, row-3 on 2026-10-03 group-a with 15 accepted and 3 rejected, row-4 on 2026-10-04 group-b with 30 accepted and 4 rejected — use accepted_records as the primary field.","exampleUseCases":[{"title":"Daily pipeline acceptance rate audit","prompt":"I have a week of record routing logs with accepted and rejected counts per day. Can you calculate how accepted_records changed between each consecutive row and give me the weighted mean of rejected_records weighted by accepted_records? Here are the rows: row-1 2026-11-01 group-a 500 accepted 20 rejected, row-2 2026-11-02 group-a 480 accepted 35 rejected, row-3 2026-11-03 group-a 510 accepted 18 rejected."},{"title":"Multi-group routing quality comparison","prompt":"Run the adjacent row changes and secondary-measure weighted mean analysis on these record routing entries across two groups — row-1 2026-12-01 group-alpha 1000 accepted 50 rejected, row-2 2026-12-01 group-beta 800 accepted 120 rejected, row-3 2026-12-02 group-alpha 1050 accepted 45 rejected, row-4 2026-12-02 group-beta 750 accepted 130 rejected. Use rejected_records as the primary field."},{"title":"ETL batch rejection spike detection","prompt":"I need to spot where rejected_records spiked between consecutive batches. Please compute the adjacent row changes and the weighted mean for rejected_records (weighted by accepted_records) across these rows: row-1 2027-01-10 batch-1 2000 accepted 10 rejected, row-2 2027-01-11 batch-1 1950 accepted 80 rejected, row-3 2027-01-12 batch-1 2100 accepted 15 rejected, row-4 2027-01-13 batch-1 2050 accepted 12 rejected."}],"resultDescription":"Two analytical reports: (1) adjacent row changes showing the difference in the chosen measure between each consecutive row, and (2) a secondary-measure weighted mean summarizing the dataset. Results are computed locally from supplied data with no external lookups.","failureModes":["More than 200 rows supplied — request will be rejected or truncated","Missing required fields (row_id, date, accepted_records, rejected_records) — validation error","Invalid date format (must be YYYY-MM-DD) — schema validation failure","Null values for both measures — weighted mean may be undefined or return error","Field enum value not matching accepted_records or rejected_records — invalid input error"],"whenToPreferThis":"Choose this endpoint when you have tabular record routing data (accepted/rejected counts) and need two specific statistical outputs — adjacent row deltas and a weighted mean — computed offline from your own supplied data without any external data fetch, prediction, or live lookup. Ideal for ETL pipeline quality monitoring, batch reporting, and data acceptance trend analysis on datasets up to 200 rows.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-23T18:52:28.109Z","isFirstParty":false,"canonicalSlug":"record-routing-analytics-adjacent-row-changes-secondary-measure-990af3f8"}