# Delx Data Classification

> Delx Data Classification is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Classifies a list of field names to identify which likely contain sensitive data, without inspecting actual values, returning deterministic machine-readable JSON.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/data-classification
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-data-classification-6517f766
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Nq15VW48134c-7qYGa2_s

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-data-classification-6517f766 -d '<json body>'
```

Example prompt: Can you classify these field names to flag which ones are likely sensitive — I have: user_id, email, ssn, created_at, account_balance, product_sku, ip_address, and notes?

## When to prefer this

Choose this endpoint when you need a fast, stateless, privacy-safe preflight classification of field names — without sending actual data values to any external service. Ideal for enterprise agent workflows that need deterministic, machine-readable sensitivity labels before committing to data processing, policy enforcement, or integration decisions. Prefer it over general-purpose LLM classification when you need consistent, reproducible JSON output at low cost and zero data retention.

## Known failure modes

- Empty or missing fields array returns an error or empty classification result
- Malformed input schema causes a 400 bad request
- Very large field inventories may exceed input limits
- Non-descriptive or ambiguous field names (e.g. 'col1', 'x') may yield low-confidence or generic classifications
- Payment failure via x402 returns 402 status blocking execution

## How this service works

Classify a field-name inventory for likely sensitive data without inspecting values. Use it as a bounded preflight or analysis step inside an enterprise agent workflow before data, policy, integration, security, or commercial decisions reach production. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base. Execution is first-party, local-only, stateless, memory-only, and has no paid upstream or input retention. Results are advisory; the caller remains responsible for aut…

## Output

Returns a deterministic JSON object mapping each input field name to a classification indicating its likely sensitivity category (e.g. PII, financial, credential, non-sensitive), enabling the caller to make downstream data, policy, or security decisions without the service ever seeing actual data values.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema": "delx/util-data-classification/v1",
  "classification": "restricted",
  "sensitive_count": 2,
  "values_processed": false,
  "sensitive_field_names": [
   "email",
   "api_token"
  ]
 }
}
```

## More

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