Back to Browse
Product Feature Telemetry – Numeric Interval Filter
x402
Product Feature Telemetry – Numeric Interval Filter is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-17).
Filters product feature telemetry rows to only those whose selected numeric metric (events or unique_users) falls within a specified min–max interval, returning up to 200 matching records.
Price / call$0.01
Success—
StatusUnknown
How this service works
Product feature telemetry - Numeric interval filter: Numeric interval filter for Product feature telemetry. 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.
Output
The endpoint returns the subset of submitted telemetry rows (up to 200) where the chosen numeric field (events or unique_users) falls within the specified minimum and maximum bounds. Each returned row preserves its original row_id, feature name, date, events, and unique_users fields.
Example use cases
Isolate high-traffic feature days
“I have 90 days of telemetry for our search and dashboard features. Can you return only the rows where the events count is between 500 and 5000 so I can focus on the busy days?”
Flag low-engagement unique user sessions
“From my feature telemetry dataset covering 'profile-edit' and 'settings' features, filter down to rows where unique_users is between 1 and 25 — I want to find the days with unusually low engagement.”
Validate mid-range feature rollout usage
“I have 60 telemetry records from our beta rollout across three features. Show me only the rows where events is between 100 and 300 — that's the expected healthy range for this stage of the rollout.”
Technical details
Endpoint
POSThttps://market.datapackvibe.com/x402/assistant-ar-analytics-feature-telemetry-range-filter?utm_source=zero.xyzWhen to prefer
Choose this endpoint when you have a local set of product feature telemetry records (up to 200 rows) and need to filter them to only those falling within a numeric interval on events or unique_users — without needing forecasting, enrichment, or cross-dataset joins. It is ideal for lightweight descriptive subsetting tasks where you control the data and just need bounded filtering logic applied server-side.
Side effects
- Empty result set if no rows fall within the specified interval
- Validation error if minimum exceeds maximum
- Schema error if required row fields (row_id, feature, date, events, unique_users) are missing
- Error if more than 200 rows are submitted
- Null numeric values in events or unique_users may cause rows to be excluded or trigger errors
- Payment failure if USDC balance is insufficient (x402 protocol)
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| rows | array | |
| field | string | |
| maximum | number | |
| minimum | number |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"