# Delx Commerce Pagination Plan API

> Delx Commerce Pagination Plan API is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-01).

Analyzes an API response object to generate a structured pagination plan, including mode, next reference cursor, stop condition, and recommended max pages.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/pagination-plan?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-commerce-pagination-plan-api-adabd9a5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qxnvr2pY6VSXgzu5ivAhP

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 delx-commerce-pagination-plan-api-adabd9a5 -d '<json body>'
```

Example prompt: I just got back a JSON response from an external API and I need to know how to paginate through the rest of the results — can you figure out the pagination mode, next cursor, whether there are more pages, and how many pages I should fetch at most?

## When to prefer this

Use this endpoint when an AI agent needs to autonomously paginate through multi-page API responses without hardcoding pagination logic. It is especially useful in agentic workflows where the response format is varied or unknown, and the agent needs a reliable, interpreted pagination plan rather than parsing raw headers or fields manually. Prefer this over custom parsing code when working with cursor-based APIs at scale.

## Known failure modes

- Malformed or non-standard response object may result in inability to detect pagination fields
- Response lacks pagination metadata, leading to null/empty next_reference
- Ambiguous response structure may produce incorrect mode detection
- Payment failure via x402 protocol will block the request before processing

## How this service works

Pay-per-result APIs for agents. No signup. Exact price. Verifiable delivery. USDC on Base + Solana via x402.

## Output

Returns a structured pagination plan including: pagination mode (e.g. cursor-based), the next reference value to use in the subsequent request, a boolean indicating whether more pages exist, the stop condition description (e.g. 'next reference absent'), and the recommended maximum number of pages to fetch.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "response": {
   "type": "object",
   "description": "Input field: response."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "mode": "cursor",
  "schema": "delx/util-pagination-plan/v1",
  "has_next": true,
  "next_reference": "abc",
  "stop_condition": "next reference absent",
  "max_pages_recommended": 100
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-pagination-plan-api-adabd9a5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from commerce.delx.ai](https://www.zero.xyz/host/commerce.delx.ai/llms.txt)