# Delx Text Chunk Plan

> Delx Text Chunk Plan 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-16).

Plans overlapping character-based chunks for RAG ingestion from caller-supplied text, returning deterministic chunk boundary metadata without storing the input

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/text-chunk-plan
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-text-chunk-plan-615b6c83
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BovSTYVe1qa9LEsa-M4jn

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-text-chunk-plan-615b6c83 -d '<json body>'
```

Example prompt: Plan overlapping character chunks for this article text — use a chunk size of 512 characters with 64 characters of overlap so I can prep it for my RAG pipeline.

## When to prefer this

Use this endpoint when you already hold the text in memory and need a deterministic, stateless chunk plan for RAG ingestion — especially when you want to preview or validate chunking parameters before committing to an embedding pipeline. Prefer this over general-purpose text-splitting libraries when you need a machine-readable JSON plan via API with guaranteed no data retention, and when cost per call ($0.003 USDC) is acceptable for planning workloads.

## Known failure modes

- Text missing or empty — returns error indicating required field
- chunk_size out of range (must be 1–20000) — returns validation error
- overlap equals or exceeds chunk_size — returns validation error
- Payment not included or insufficient — x402 payment required error
- Very large text with tiny chunk_size may exceed processing limits

## How this service works

Plan overlapping character chunks for RAG without storing the text — call when planning overlapping character chunks for RAG prep. Use on text/URLs the agent already holds—adjacent to high-volume extract demand, never advertised as general web or X search. Returns deterministic machine-readable JSON for $0.003 USDC via x402 on Base. Execution is first-party, local-only, stateless, and memory-only with no paid upstream, no input retention, and no claim of live chain tip, web search, or media gen…

## Output

Returns a deterministic JSON object describing the planned chunk boundaries, number of chunks, character offsets, and overlap windows for the supplied text — no text is stored and no upstream services are called.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "text": {
   "type": "string",
   "description": "UTF-8 text to encode, chunk, index, or analyze (caller-supplied only)."
  },
  "overlap": {
   "type": "number",
   "description": "Characters of overlap between consecutive chunks (0 .. chunk_size-1)."
  },
  "chunk_size": {
   "type": "number",
   "description": "Characters per chunk (1–20000); example uses small sizes for demos."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chunks": [
   {
    "end": 4,
    "chars": 4,
    "index": 0,
    "start": 0
   },
   {
    "end": 7,
    "chars": 4,
    "index": 1,
    "start": 3
   },
   {
    "end": 10,
    "chars": 4,
    "index": 2,
    "start": 6
   }
  ],
  "schema": "delx/util-text-chunk-plan/v1",
  "overlap": 1,
  "truncated": false,
  "chunk_size": 4,
  "text_chars": 10,
  "chunk_count": 3
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-text-chunk-plan-615b6c83/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)