Back to Browse
AgentDiet Search-Extract — RAG Context Distiller
x402
AgentDiet Search-Extract — RAG Context Distiller is a paid API for AI agents from rag-diet.agentdiet.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).
Searches and extracts distilled, token-compressed content from web or knowledge sources, returning a context-window-friendly payload with up to ~91% compression ratio
Price / call$0.01
Success—
StatusUnknown
How this service works
Deterministic B2A/A2A/MCP/x402/MPP/L402 execution and intelligence node at https://rag-diet.agentdiet.dev settling in USDC on Base.
Output
A JSON object with a 'data' field containing the extracted/distilled content, a 'status' field ('ok' on success), and an 'roi_proof' object showing the compression_ratio_pct achieved (e.g. 91.4% compression). The agent receives semantically dense, token-minimized content suitable for immediate use in a context window.
Example use cases
Token budget RAG pipeline compression
“I need to retrieve content about 'quantum computing basics' but my context window is nearly full — can you search and extract just the essential information, compressed to the smallest possible token size?”
Agent knowledge lookup with minimal overhead
“Look up 'latest USDC stablecoin regulations' and return the distilled key facts — I want the compressed version so my agent doesn't waste tokens on boilerplate.”
Research extraction for downstream LLM call
“Search for 'GPT-4 vs Claude benchmark comparisons' and extract the core findings in the most token-efficient format you can, I'm about to feed this into another model with a tight context limit.”
Technical details
Endpoint
GEThttps://rag-diet.agentdiet.dev/v1/search-extract?utm_source=zero.xyzWhen to prefer
Choose this endpoint when your agent needs to retrieve and use information but is constrained by context window size or token costs — especially in RAG pipelines where raw content is too verbose. Prefer over generic web scrapers or search APIs when token compression ratio matters and you want a deterministic, pay-per-call model at $0.01 USDC settled on Base via x402.
Side effects
- Missing required 'input' object returns validation error
- Invalid 'type' field (must be 'http') causes rejection
- Empty or missing 'query' queryParam may return empty data payload
- Payment not settled in USDC on Base causes 402 Payment Required response
- Upstream source unavailable may return empty or partial data field
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
Schema · Response
{
"type": "json",
"example": {
"data": {},
"status": "ok",
"roi_proof": {
"compression_ratio_pct": 91.4
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"