# Delx Commerce — API Error Taxonomy Classifier

> Delx Commerce — API Error Taxonomy Classifier 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).

Classifies an HTTP error response body and status code into a structured error taxonomy, returning category, retryability, and a content hash.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/api-error-taxonomy?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-api-error-taxonomy-classifier-88ea19cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mD5tsW1osQG9OQkIQ6VD8

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-api-error-taxonomy-classifier-88ea19cb -d '<json body>'
```

Example prompt: I just got a 503 response from an upstream API with body 'Service Unavailable — please try again later'. Can you classify this error using the Delx error taxonomy and tell me whether I should retry?

## When to prefer this

Use this endpoint when an AI agent or automated pipeline needs to programmatically decide whether to retry an API call, escalate an error, or log it — especially when normalizing errors from diverse upstream services into a consistent taxonomy. Prefer this over manual error parsing when you need a verifiable, hashed record of the error response for audit purposes.

## Known failure modes

- Missing or malformed status_code field returns a validation error
- Empty body string may result in classification with limited confidence
- Unknown or non-standard status codes may produce an 'unknown' category
- Payment failure via x402 protocol results in 402 response before processing occurs

## 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 containing: the taxonomy schema version (e.g. 'delx/util-api-error-taxonomy/v1'), an error category string (e.g. 'upstream_transient'), a boolean retryable flag, a SHA-256 hash of the response body for verification, the echoed status code, and a flag indicating whether the body was returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "body": {
   "type": "string",
   "description": "Input field: body."
  },
  "status_code": {
   "type": "number",
   "description": "Input field: status_code."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-api-error-taxonomy/v1",
  "category": "upstream_transient",
  "retryable": true,
  "body_sha256": "93a8ba7fde7cf39ab2dea97fc62f4352331bc174e3c4fbed390d9a8153f4787c",
  "status_code": 503,
  "body_returned": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-api-error-taxonomy-classifier-88ea19cb/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)