<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Llm on Restish</title><link>https://rest.sh/tags/llm/</link><description>Recent content in Llm on Restish</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 15 Jun 2026 20:17:27 -0700</lastBuildDate><atom:link href="https://rest.sh/tags/llm/index.xml" rel="self" type="application/rss+xml"/><item><title>TOON: Token-Efficient API Output for LLM Workflows</title><link>https://rest.sh/blog/toon-token-efficient-api-output-for-llm-workflows/</link><pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate><guid>https://rest.sh/blog/toon-token-efficient-api-output-for-llm-workflows/</guid><description>&lt;p&gt;When a person reads an API response, formatting is free. When an LLM agent
reads one, every character is metered. The response lands in a context window,
the context window is billed by the token, and the format you chose decides how
many tokens the same data costs.&lt;/p&gt;
&lt;p&gt;JSON spends a lot of tokens on that job. A list of one hundred records repeats
every key one hundred times, wraps every string in quotes, and spends tokens on
braces and brackets that a model does not need to understand a table of data.&lt;/p&gt;</description></item></channel></rss>