Back to Browse
AgentDiet Bundle Execute — A2A Context Window Distiller
x402
AgentDiet Bundle Execute — A2A Context Window Distiller is a paid API for AI agents from status.agentdiet.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).
Executes an HTTP-based bundle request through AgentDiet's context compression and distillation pipeline, returning de-bloated output with up to 91% token compression ratio proof.
Price / call$0.01
Success—
StatusUnknown
How this service works
Deterministic B2A/A2A/MCP/x402/MPP/L402 execution and intelligence node at https://status.agentdiet.dev settling in USDC on Base.
Output
A JSON object containing a 'data' field with the distilled/compressed output, a 'status' field (e.g. 'ok'), and a 'roi_proof' object that includes a 'compression_ratio_pct' value (e.g. 91.4) indicating the percentage of tokens removed from the original context.
Example use cases
Context window token reduction for long agent chains
“My agent pipeline keeps hitting token limits mid-conversation. Can you send this context bundle through AgentDiet's distiller using a GET request with the full query and show me the compression ratio it achieves?”
A2A payload de-bloating before downstream call
“Before I forward this A2A message to the next node, run it through AgentDiet's bundle-execute endpoint to strip out the token bloat and give me the distilled output along with the ROI proof.”
Verify context savings in MCP workflow
“I want to validate that my MCP context compression is actually working — pass this query through AgentDiet and return the compression_ratio_pct so I can confirm we're hitting at least 85% reduction.”
Technical details
Endpoint
GEThttps://status.agentdiet.dev/v1/bundle-execute?utm_source=zero.xyzWhen to prefer
Choose this endpoint when your AI agent pipeline is suffering from context window bloat and you need deterministic, measurable token reduction with a verifiable compression ratio proof. It is especially well-suited for A2A, MCP, or B2A pipelines where payloads must be trimmed before passing to downstream nodes, and where you want a cheap ($0.01 USDC) per-call micro-payment model via x402 on Base rather than a subscription or batch compression service.
Side effects
- Payment not settled in USDC on Base — request rejected with 402 Payment Required
- Missing required 'input' field or 'type'/'method' sub-fields — validation error returned
- Unsupported HTTP method supplied (not GET or POST) — schema validation failure
- Query parameter 'query' absent or malformed — empty or degraded compression output
- Endpoint node unavailable — status endpoint returns non-ok status
- High compression ratio not achievable for already-compact inputs — low roi_proof value returned
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"