# Delx Commerce — Rate Limit Header Parser

> Delx Commerce — Rate Limit Header Parser 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).

Parses HTTP rate-limit headers from an API response and returns structured rate limit information including limit, remaining, reset, and retry-after values.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/rate-limit-parse?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-rate-limit-header-parser-6b589954
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CXGOEmbugSoItBVU7jGtU

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-rate-limit-header-parser-6b589954 -d '<json body>'
```

Example prompt: I just got a 429 response from an API — can you parse these headers and tell me my rate limit, how many requests I have left, and how long I should wait before retrying? Headers: {"retry-after": "30", "x-ratelimit-limit": "100", "x-ratelimit-remaining": "12"}

## When to prefer this

Use this endpoint when an AI agent needs to automatically interpret HTTP rate-limit headers from third-party API responses — especially when different APIs use non-standard or inconsistent header naming conventions. It is ideal for agents that must self-regulate request pacing, implement backoff strategies, or surface quota information to users without hard-coding header-parsing logic per API.

## Known failure modes

- Missing or unrecognized header names result in null values for limit/remaining/reset
- Malformed header values (non-numeric) may cause parsing errors or null outputs
- If no rate-limit headers are present in the input, result fields will be null or absent
- Payment failure via x402 protocol prevents call from completing

## 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 JSON object with the parsed rate limit fields: limit (total allowed requests), remaining (requests left), reset (reset timestamp if available), retry_after (seconds to wait), source_headers (list of which headers were found and parsed), and a schema identifier string.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "limit": "100",
  "reset": null,
  "schema": "delx/util-rate-limit-parse/v1",
  "remaining": "12",
  "retry_after": "30",
  "source_headers": [
   "retry-after",
   "x-ratelimit-limit",
   "x-ratelimit-remaining"
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-rate-limit-header-parser-6b589954/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)