# Quest Pacing — String Normalisation + Numeric Interval Filter

> Quest Pacing — String Normalisation + 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-30).

Normalises game_area strings and filters quest pacing rows by a numeric interval on duration_minutes or objective_count, returning two analytical reports for up to 200 supplied rows.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-ib26-game-04-026?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/quest-pacing-string-normalisation-numeric-interval-filter-9dc05c0c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OXBdmINUUKKXHF948lOeF

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability quest-pacing-string-normalisation-numeric-interval-filter-9dc05c0c -d '<json body>'
```

Example prompt: Can you run string normalisation on the game_area field and filter by duration_minutes between 10 and 60 for these quest pacing records? I have 4 rows: row-1 on 2026-10-01 in group-a with 1 objective and 10 minutes, row-2 on 2026-10-02 in group-b with 2 objectives and 20 minutes, row-3 on 2026-10-03 in group-a with 3 objectives and 15 minutes, row-4 on 2026-10-04 in group-b with 4 objectives and 30 minutes.

## When to prefer this

Choose this endpoint when you have quest pacing data (up to 200 rows) and need both string normalisation on the game_area dimension and a numeric interval filter on either duration_minutes or objective_count in a single low-cost call. It is a self-contained analytical compute step with no external dependencies, making it suitable for offline or batch data-cleaning pipelines in game analytics workflows.

## Known failure modes

- More than 200 rows submitted — request rejected or truncated
- Missing required fields (row_id, game_area, date, duration_minutes, objective_count) cause validation errors
- Invalid date format (not YYYY-MM-DD) causes schema rejection
- Minimum greater than maximum yields empty filter result
- Numeric values outside ±1,000,000,000,000 are rejected by schema

## How this service works

Quest pacing — String normalisation + Numeric interval filter: String normalisation + Numeric interval filter for supplied quest pacing records (duration_minutes, objective_count). 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.

## Output

Two independent analytical reports: one covering string normalisation results for the game_area field, and one listing rows whose chosen numeric field (duration_minutes or objective_count) falls within the specified minimum–maximum interval. Covers up to 200 input rows with no external lookups.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "rows": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "row_id",
     "game_area",
     "date",
     "duration_minutes",
     "objective_count"
    ],
    "properties": {
     "date": {
      "type": "string",
      "default": "",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "maxLength": 10
     },
     "row_id": {
      "type": "string",
      "default": "",
      "maxLength": 80,
      "minLength": 1
     },
     "game_area": {
      "type": "string",
      "default": "",
      "maxLength": 80
     },
     "objective_count": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     },
     "duration_minutes": {
      "type": [
       "number",
       "null"
      ],
      "maximum": 1000000000000,
      "minimum": -1000000000000
     }
    },
    "additionalProperties": false
   },
   "default": [
    {
     "date": "2026-10-01",
     "row_id": "row-1",
     "game_area": "group-a",
     "objective_count": 1,
     "duration_minutes": 10
    },
    {
     "date": "2026-10-02",
     "row_id": "row-2",
     "game_area": "group-b",
     "objective_count": 2,
     "duration_minutes": 20
    },
    {
     "date": "2026-10-03",
     "row_id": "row-3",
     "game_area": "group-a",
     "objective_count": 3,
     "duration_minutes": 15
    },
    {
     "date": "2026-10-04",
     "row_id": "row-4",
     "game_area": "group-b",
     "objective_count": 4,
     "duration_minutes": 30
    }
   ],
   "maxItems": 200,
   "minItems": 1
  },
  "field": {
   "enum": [
    "duration_minutes",
    "objective_count"
   ],
   "type": "string",
   "default": "duration_minutes"
  },
  "maximum": {
   "type": "number",
   "default": 100,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  },
  "minimum": {
   "type": "number",
   "default": 0,
   "maximum": 1000000000000,
   "minimum": -1000000000000
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quest-pacing-string-normalisation-numeric-interval-filter-9dc05c0c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)