{"uid":"cap_RxDKGug7UYX7ZCpPCLjx-","slug":"data-pipeline-runs-numeric-interval-filter-e75aae14","name":"Data Pipeline Runs – Numeric Interval Filter","description":"Data pipeline runs - Numeric interval filter: Numeric interval filter for Data pipeline runs. Up to 200 supplied typed records. Local descriptive analytics; no enrichment or forecast. One of 25 new profiles across 20 shared operations in this industry. 0.01 USDC includes one bounded numeric interval filter report.","url":"https://market.datapackvibe.com/x402/assistant-ar-analytics-pipeline-runs-range-filter?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"rows":{"type":"array","items":{"type":"object","required":["row_id","pipeline","date","processed_rows","rejected_rows"],"properties":{"date":{"type":"string","default":"","pattern":"^\\d{4}-\\d{2}-\\d{2}$","maxLength":10},"row_id":{"type":"string","default":"","maxLength":80,"minLength":1},"pipeline":{"type":"string","default":"","maxLength":80},"rejected_rows":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000},"processed_rows":{"type":["number","null"],"maximum":1000000000000,"minimum":-1000000000000}},"additionalProperties":false},"default":[{"date":"2026-10-01","row_id":"row-1","pipeline":"group-a","rejected_rows":1,"processed_rows":10},{"date":"2026-10-02","row_id":"row-2","pipeline":"group-b","rejected_rows":2,"processed_rows":20},{"date":"2026-10-03","row_id":"row-3","pipeline":"group-a","rejected_rows":3,"processed_rows":15},{"date":"2026-10-04","row_id":"row-4","pipeline":"group-b","rejected_rows":4,"processed_rows":30}],"maxItems":200,"minItems":1},"field":{"enum":["processed_rows","rejected_rows"],"type":"string","default":"processed_rows"},"maximum":{"type":"number","default":100,"maximum":1000000000000,"minimum":-1000000000000},"minimum":{"type":"number","default":0,"maximum":1000000000000,"minimum":-1000000000000}}},"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_abTzER5AicEkaFjwnMJfL","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":"Filters a supplied set of data pipeline run records to only those where a chosen numeric field (processed_rows or rejected_rows) falls within a specified numeric range.","exampleAgentPrompt":"From my pipeline run logs, filter to only the runs where processed_rows is between 50 and 300 — here are the records: [{\"row_id\":\"r1\",\"pipeline\":\"ingest-prod\",\"date\":\"2026-10-01\",\"processed_rows\":120,\"rejected_rows\":5},{\"row_id\":\"r2\",\"pipeline\":\"ingest-dev\",\"date\":\"2026-10-02\",\"processed_rows\":400,\"rejected_rows\":2}].","exampleUseCases":[{"title":"Flag low-throughput pipeline runs","prompt":"I have a list of pipeline run records and I want to see only the ones where processed_rows is between 0 and 100 — can you filter this down and show me what's underperforming? Field to filter on is processed_rows, minimum 0, maximum 100."},{"title":"Audit runs with high rejection counts","prompt":"Here are my ETL run logs for last month — filter them to only the records where rejected_rows is between 10 and 50 so I can investigate what went wrong. Use rejected_rows as the field."},{"title":"QA pipeline output within expected range","prompt":"I need to validate that my pipeline runs are producing within expected bounds — filter these records to only those where processed_rows is between 500 and 2000 so I can confirm normal operation. The field is processed_rows."}],"resultDescription":"A filtered subset of the supplied pipeline run records (up to 200 input rows) where the specified numeric field (processed_rows or rejected_rows) falls within the given minimum and maximum bounds. The response is a local descriptive analytics report with no external enrichment or forecasting.","failureModes":["Input array is empty or missing — validation error returned","Minimum value is greater than maximum value — invalid interval error","Field value is not one of the allowed enum values (processed_rows, rejected_rows) — schema error","More than 200 rows supplied — request rejected with maxItems violation","Row missing required fields (row_id, pipeline, date) — validation failure","Numeric values out of allowed range (±1,000,000,000,000) — schema error"],"whenToPreferThis":"Use this endpoint when you have a local dataset of data pipeline run records (up to 200 rows) and need to quickly filter them to a bounded numeric interval on either processed_rows or rejected_rows — particularly for lightweight, in-request descriptive analytics without any external data enrichment, forecasting, or aggregation. Prefer this over full analytics platforms when you need a simple, cheap ($0.01 USDC) bounded-range filter on your own supplied records.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-17T00:46:27.128Z","isFirstParty":false,"canonicalSlug":"data-pipeline-runs-numeric-interval-filter-e75aae14"}