AG
Blockchain Data · x402 · early usage

Split text into retrieval-friendly chunks with a token budget and sentence-aware bounda…

Split text into retrieval-friendly chunks with a token budget and sentence-aware boundaries. Overlap between consecutive chunks preserves context across splits — the standard preparation step before embedding. Use this when an agent needs to rAG-ready chunks…

by agentstoolshub.com · discovered, not yet claimed by its owner · updated 2026-10-11

30d calls2
30d payers2
MethodGET
Outputjson

Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.

What it does

Split text into retrieval-friendly chunks with a token budget and sentence-aware boundaries. Overlap between consecutive chunks preserves context across splits — the standard preparation step before embedding. Use this when an agent needs to rAG-ready chunks with token budgets and overlap.

Tags: dev · crypto-dev · analytics · bazaar

Call contract

Method
GET
Input
query parameters
Output
json
Last paid call
2026-10-11
Input example from Bazaar metadata
{
  "overlapTokens": 15,
  "targetTokens": 60,
  "text": "Retrieval-augmented generation improves factuality. First, documents are split into chunks. Second, chunks are embedded into vectors. Third, the agent retrieves the top matches for a query. Overlap keeps ideas that straddle boundaries intact. Finally, the model answers with citations."
}
Output example
{
  "result": {
    "answer": "2 chunks",
    "answerLabel": "≈65 tokens → chunks of ≤60 tokens, overlap 15",
    "artifacts": {
      "chunks": "[{\"index\":0,\"estTokens\":55,\"text\":\"Retrieval-augmented generation improves factuality. First, documents are split into chunks. Second, chunks are embedded into vectors. Third, the agent retrieves the top matches for a query. Overlap keeps ideas that straddle boundaries intact.\"},{\"index\":1,\"estTokens\":22,\"text\":\"Overlap keeps ideas that straddle boundaries intact. Finally, the model answers with citations.\"}]"
    },
    "details": [
      {
        "label": "Input (chars / est. tokens)",
        "value": "285 / ≈65"
      },
      {
        "label": "Avg chunk size",
        "value": "≈39 tokens"
      },
      {
        "label": "Boundary strategy",
        "value": "paragraph → sentence → word"
      }
    ],
    "steps": [
      "Split into 6 sentence units",
      "Pack units up to 60 estimated tokens",
      "Carry ≈15 tokens of overlap between consecutive chunks"
    ],
    "table": {
      "columns": [
        "Chunk",
        "Est. tokens",
        "Preview"
      ],
      "rows": [
        [
          0,
          55,
          "Retrieval-augmented generation improves factuality. First, d…"
        ],
        [
          1,
          22,
          "Overlap keeps ideas that straddle boundaries intact. Finally…"
        ]
      ]
    },
    "value": 2
  },
  "tool": "text-chunker"
}

Use with an agent

  1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
  2. Inspect. Fetch /resources/35456.json for the price and payment options.
  3. Pay. Call GET https://agentstoolshub.com/api/v1/dev/text-chunker. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
  4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price
$0.005 / request
Protocol
x402 v2
Auth
No account or API key. Pay per request.
Networks
Base
Demand
2 calls · 2 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

SchemeNetworkAssetAmountPay toTimeout
exactBase
eip155:8453
USDC$0.0050x8a0F2b0a6C82D1c54B16E2e4DEcd18fF0802b0f6300s
accepts[] (raw JSON)
[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x8a0F2b0a6C82D1c54B16E2e4DEcd18fF0802b0f6",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "5000",
    "amountUsd": 0.005,
    "maxTimeoutSeconds": 300
  }
]

Schemas

Output schema (JSON Schema)
{
  "properties": {
    "example": {
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}
Example shape — generated from the schema, not a captured live response
{
  "example": {},
  "type": "string"
}

Examples

curl
curl "https://agentstoolshub.com/api/v1/dev/text-chunker"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid
JavaScript
const res = await fetch("https://agentstoolshub.com/api/v1/dev/text-chunker");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}
Python
import httpx
res = httpx.get("https://agentstoolshub.com/api/v1/dev/text-chunker")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider
agentstoolshub.com
Endpoint
https://agentstoolshub.com/api/v1/dev/text-chunker
Machine-readable
/resources/35456.json