# Delx Commerce — Content-Type Match Validator

> Delx Commerce — Content-Type Match Validator is a paid API for AI agents from commerce.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-01).

Checks whether an actual HTTP Content-Type value matches an expected media type pattern or range, returning a pass/fail result with verifiable evidence.

## Facts

- Endpoint: POST https://commerce.delx.ai/api/v1/x402/content-type-match?utm_source=zero.xyz
- Price: $0.001/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-content-type-match-validator-37672138
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BcJWid5Batl4y02XjjrWt

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-content-type-match-validator-37672138 -d '<json body>'
```

Example prompt: Check whether the actual content type 'application/problem+json' matches the expected pattern 'application/*+json' and tell me if they're compatible.

## When to prefer this

Use this endpoint when an AI agent needs to programmatically verify HTTP content-type compatibility — for example, before parsing a response body, validating webhook payloads, or asserting correct MIME types in integration tests. It is ideal when you want a pay-per-call, no-signup, verifiable validation with a cryptographic evidence trail (SHA-256 of inputs) and no data retention.

## Known failure modes

- Malformed or unparseable content-type strings may return a failed match or validation error
- Input strings exceeding 8192 characters will be rejected
- Missing 'actual' or 'expected' fields result in a bad request error
- Ambiguous wildcard patterns may produce unexpected match semantics

## 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 JSON object indicating whether the actual media type matched the expected pattern (matched: true/false), the normalized expected range, the parsed actual media type, an overall pass/fail status, and an evidence block containing a SHA-256 hash of the input and confirmation that no data was retained or sent to external services.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "actual": {
   "type": "string",
   "maxLength": 8192,
   "description": "Actual supplied to Content Type Match; used only for this bounded calculation and processed in memory without retention."
  },
  "expected": {
   "type": "string",
   "maxLength": 8192,
   "description": "Expected supplied to Content Type Match; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "matched": true,
   "expected_range": "application/*+json",
   "actual_media_type": "application/problem+json"
  },
  "schema": "delx/util-content-type-match/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "b7c613a2c98fff13f2ac6da517851a23617d85340d45c743194249ef9f57070f",
   "external_calls": 0
  },
  "operation": "web_reliability:content_type_match"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-commerce-content-type-match-validator-37672138/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)
