Docs Digest
Verified: delivered 14 times
How we rate this
Delivery health: healthy. Paid successes: 14. Paid failures: 4. Last successful delivery: 2026-10-17. Schema confidence: high.
Verified means the listing is healthy, the schema confidence is medium or high, and paid deliveries outnumber paid failures. Working means it is healthy with that same schema confidence, and no paid buy has verified it yet. Limited track record means the health, the paid history, or the schema confidence is still thin. Having trouble means the listing is paused or failing, or it is degraded and paid failures are at least as common as paid successes.
50 sats · ≈$0.041
Docs digest: outline, signatures, and examples for a multi-page read of a docs site.
More
Use when you'd otherwise read about 30+ docs pages at $1.25/M, 12+ at $3/M, or 3+ at $15/M; skip on models under about $0.65/M; pass a topic. For a single page, use read_webpage. If the site publishes llms.txt, read that first.
Example
What agents use this for. Docs digest: outline, signatures, and examples for a multi-page read of a docs site. Category: documents.
Request
GET https://amazap.com/basics/v1/docs-digest?url=https%3A%2F%2Fhono.dev%2Fdocs&topic=install&max_tokens=8000
curl
curl -sS -X GET \ 'https://amazap.com/basics/v1/docs-digest?url=https%3A%2F%2Fhono.dev%2Fdocs&topic=install&max_tokens=8000' \ -H 'Accept: application/json' \ # Example only. No L402 token. Sends no sats.
MCP buy
buy({
"sku": "amazap-basics-docs-digest",
"params": {
"url": "https://hono.dev/docs",
"topic": "install",
"max_tokens": 8000
},
"total_cost": "50 sats",
"max_total_sats": 50
})
Example response
Stored from a successful paid delivery. Truncated to a size cap.
{"markdown":"# Hono\n\nSource: https://hono.dev/docs\n\nPages: 60\n## Combine Middleware\nSource: https://hono.dev/docs/middleware/builtin/combine\n\nCombine Middleware combines multiple middleware functions into a single middleware. It provides three functions: - `some` - Runs only one of the given middleware. - `every` - Runs all given middleware. - `except` - Runs all given middleware only if a condition is not met.\n## Third-party Middleware\nSource: https://hono.dev/docs/guides/middleware\n\nBuilt-in middleware does not depend on external modules, but third-party middleware can depend on third-party libraries. So with them, we may make a more complex application. We can explore a variety of third-party middleware. For example, we have GraphQL Server Middleware, Sentry Middleware, Firebase Auth Middleware, and others.\n## Execution order\nSource: https://hono.dev/docs/guides/middleware\n\nThe order in which Middleware is executed is determined by the order in which it is registered. The process before the `next` of the first registered Middleware is executed first, and the process after the `next` is executed last. See below. Result is the following. Note that if the handler or any middleware throws, hono will catch it and either pass it to your app.\n\n```\napp.use(async (_, next) => {\n console.log('middleware 1 start')\n await next()\n console.log('middleware 1 end')\n})\napp.use(async (_, next) => {\n console.log('middleware 2 start')\n await next()\n console.log('middleware 2 end')\n})\napp.use(async (_, next) => {\n console.log('middleware 3 start')\n await next()\n console.log('middleware 3 end')\n})\n\napp.get('/', (c) => {\n console.log('handler')\n return c.text('Hello!')\n})\n```\n\n```\nmiddleware 1 start\n middleware 2 start\n middleware 3 start\n handler\n middleware 3 end\n middleware 2 end\nmiddleware 1 end\n```\n## Middleware Conflicts\nSource: https://hono.dev/docs/middleware/builtin/timeout\n\nBe cautious about the order of middleware, especially when using error-han
Amazap Basics