Chunk text with overlap
Use to split a document into bounded Unicode-code-point windows with configurable overlap. Exact source slices use UTF-16 offsets, so adjacent windows can be verified without losing source characters. Not tokenization or grapheme segmentation. At most 2,000 chunks and 500,000 returned UTF-16 units.
text · Operation ID: text-chunk
Choose this operation when
- Create bounded code-point windows with verifiable UTF-16 source offsets.
Outside this profile
- Tokenizer-accurate token budgets or semantic passage segmentation.
Exact release references
Static JSON contract · Markdown reference · Fixed example response
Complete input schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"text": {
"type": "string",
"maxLength": 100000
},
"maxChars": {
"default": 1000,
"type": "integer",
"minimum": 1,
"maximum": 10000
},
"overlapChars": {
"default": 0,
"type": "integer",
"minimum": 0,
"maximum": 9999
}
},
"required": [
"text"
],
"additionalProperties": false
}
Complete output-envelope schema
{
"type": "object",
"required": [
"operation",
"version",
"result",
"provenance"
],
"properties": {
"operation": {
"const": "text-chunk",
"type": "string"
},
"version": {
"const": "0.29.0",
"type": "string"
},
"result": {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"type": "object",
"properties": {
"offsetUnit": {
"type": "string",
"const": "UTF-16 code units; zero-based, end-exclusive"
},
"originalCodeUnits": {
"type": "integer",
"minimum": 0,
"maximum": 100000
},
"originalCodePoints": {
"type": "integer",
"minimum": 0,
"maximum": 100000
},
"chunkCount": {
"type": "integer",
"minimum": 0,
"maximum": 2000
},
"chunks": {
"maxItems": 2000,
"type": "array",
"items": {
"type": "object",
"properties": {
"index": {
"type": "integer",
"minimum": 0,
"maximum": 1999
},
"start": {
"type": "integer",
"minimum": 0,
"maximum": 100000
},
"end": {
"type": "integer",
"minimum": 0,
"maximum": 100000
},
"codePoints": {
"type": "integer",
"minimum": 0,
"maximum": 10000
},
"text": {
"type": "string",
"maxLength": 20000
}
},
"required": [
"index",
"start",
"end",
"codePoints",
"text"
],
"additionalProperties": false
}
}
},
"required": [
"offsetUnit",
"originalCodeUnits",
"originalCodePoints",
"chunkCount",
"chunks"
],
"additionalProperties": false
},
"provenance": {
"type": "object",
"required": [
"inputSha256",
"outputSha256",
"deterministic",
"externalRequests"
],
"properties": {
"inputSha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"outputSha256": {
"type": "string",
"pattern": "^[a-f0-9]{64}$"
},
"deterministic": {
"const": true
},
"externalRequests": {
"const": 0
}
}
}
},
"additionalProperties": false
}
Fixed example
One accepted fixed example, not a custom-input trial. No operation runs when this static page is requested.
Example input
{
"text": "Agents need exact source offsets for retrieval.",
"maxChars": 20,
"overlapChars": 5
}
Example response
{
"operation": "text-chunk",
"version": "0.29.0",
"result": {
"offsetUnit": "UTF-16 code units; zero-based, end-exclusive",
"originalCodeUnits": 47,
"originalCodePoints": 47,
"chunkCount": 3,
"chunks": [
{
"index": 0,
"start": 0,
"end": 20,
"codePoints": 20,
"text": "Agents need exact so"
},
{
"index": 1,
"start": 15,
"end": 35,
"codePoints": 20,
"text": "ct source offsets fo"
},
{
"index": 2,
"start": 30,
"end": 47,
"codePoints": 17,
"text": "ts for retrieval."
}
]
},
"provenance": {
"inputSha256": "fbd009549808504641990274a3acdffd9280cad74caa8c7614b5cea66a9be5f1",
"outputSha256": "7b3184db21762bfcd8b96cd0555cb3af852650c154c8d79c1145d6d37d48dd2a",
"deterministic": true,
"externalRequests": 0
}
}
Bounds and precision
JavaScript IEEE-754 numbers; use strings for large integer IDs/exact decimals where the schema accepts strings. No lossless numeric parsing.
{
"global": {
"requestBytes": 131072,
"responseBytes": 524288,
"jsonDepth": 32,
"jsonNodes": 20000,
"requestsPerMinute": 60,
"paidAttemptsPerMinute": 20,
"idempotencyHours": 24
},
"operation": {
"requestBytes": 131072,
"responseBytes": 524288,
"jsonDepth": 32
}
}
Complete schemas, descriptions and cross-field validation may impose additional limits.
Proposed price and protocol definitions
{
"unit": "one successful operation call",
"proposedNominalUsd": "0.005",
"sixDecimalTokenBaseUnits": "5000",
"subscription": false,
"includesPayerWalletOrNetworkFees": false,
"liveQuoteVerified": false,
"condition": "Actual SDK challenge is authoritative only within the caller's explicit authorization; configured six-decimal token peg is an operator assertion, not a conversion guarantee."
}
Protocol definitions: x402, mpp. MPP uses Tempo charge. Paid MCP execution is unsupported. All runtime readiness is not evaluated in this build.
API path templates, not endpoints on this documentation host
{
"x402": "/v1/x402/text-chunk",
"mpp": "/v1/mpp/text-chunk"
}
Required headers
{
"Content-Type": "application/json",
"Idempotency-Key": "random 16–128 character operation identifier"
}
Actual SDK challenge amount, asset, network, recipient and wallet costs must pass independent authorization. Preserve identical key, body, protocol and credential on retries; on PAYMENT_UNCERTAIN stop and reconcile.
Execution profile and provider conditions
{
"deterministic": true,
"externalRequests": 0,
"maxExternalRequests": 0,
"resultSnapshotPersisted": false,
"fixedExampleIsIllustrativeSnapshot": false,
"requiresPayment": true,
"supportsMcpExecution": false
}
Deterministic supplied-input operation with no external requests or stored request/result bodies. Payment infrastructure retains payment metadata and hashes.
Failure handling
- HTTP 400: Malformed JSON, missing/invalid idempotency key, or payment identifier mismatch Correct the request before payment
- HTTP 402: Payment challenge or rejected payment Use official protocol SDK; inspect payment outcome before another payment
- HTTP 409: Idempotency conflict, duplicate proof, or PAYMENT_UNCERTAIN Keep original key, body, and proof; reconcile uncertainty with operator; never blindly repay
- HTTP 413: Input or generated output too large Reduce input; no payment attempted for validation failure
- HTTP 415: Unsupported media type or compression Send uncompressed application/json
- HTTP 422: Schema or service-specific semantic validation failure Correct input using returned error code; no payment attempted
- HTTP 429: Request/payment-attempt rate exceeded Wait for rate limit window; preserve existing payment identity
- HTTP 503: Payment configuration/provider/state unavailable, or live DNS preparation failed before settlement Check readiness; DNS preparation failures may retry the identical key/body/credential only; uncertainty requires reconciliation
Declared requirements
Before any paid call, refresh the live operation contract and POST the complete bounded budgeted plan to the separate API's /preflight. Unknown requirements block selection; compatible preflight is not permission to spend.