# Delx EVM Blob Count Check

> Delx EVM Blob Count Check is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Validates whether an EVM transaction blob count is within a specified maximum limit, returning a pass/fail result with evidence metadata.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/evm-blob-count-check
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-evm-blob-count-check-1e5b2389
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bZH3tIFyZ8vFrv8mXPNtk

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-evm-blob-count-check-1e5b2389 -d '<json body>'
```

Example prompt: Check if a blob count of 2 is within the maximum of 6 for an EVM transaction — I need to know if it's safe to proceed before I submit.

## When to prefer this

Use this endpoint when you need a lightweight, auditable, zero-retention preflight check to verify that an EVM transaction's blob count does not exceed a specified maximum before submission. Prefer it over manual comparison logic when you need a tamper-evident SHA-256 evidence trail and explicit pass/fail status for agent decision-making in EVM blob transaction pipelines.

## Known failure modes

- Missing required fields (blob_count or maximum not provided) result in validation error
- Non-integer values for blob_count or maximum cause schema rejection
- Negative integers may produce unexpected comparison results
- Network or service unavailability returns 5xx error

## How this service works

EVM Blob Count Check: EVM Blob Count Check checks caller-supplied blob count against a transaction limit from bounded caller-supplied values without an external provider. Call EVM Blob Count Check before signing, submitting, replacing, or accepting an EVM/Base transaction assembled from caller-owned data. Returns normalized transaction evidence, calculated budget or shape findings, and a fail-closed preflight status for EVM Blob Count Check as versioned deterministic JSON. Price: $0.001 USDC vi…

## Output

Returns a JSON object with the result object containing blob_count, maximum, and within_limit boolean; a status field ('pass' or 'fail'); and an evidence block with input SHA-256 hash, retained flag (always false), and external_calls count confirming no data is stored or forwarded.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "maximum": {
   "type": "integer",
   "description": "Maximum supplied to EVM Blob Count Check; used only for this bounded calculation and processed in memory without retention."
  },
  "blob_count": {
   "type": "integer",
   "description": "Blob Count supplied to EVM Blob Count Check; used only for this bounded calculation and processed in memory without retention."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "maximum": 6,
   "blob_count": 2,
   "within_limit": true
  },
  "schema": "delx/util-evm-blob-count-check/v1",
  "status": "pass",
  "evidence": {
   "retained": false,
   "input_sha256": "b549f9e7119c69aa37ac661b862dfefbba90fa2ca0d8fa28e49d03aec7f75485",
   "external_calls": 0
  },
  "operation": "evm_preflight:evm_blob_count_check"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-evm-blob-count-check-1e5b2389/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)