The internet learned to speak to our agents

<p>When an AI agent visits a website today, it gets the same thing a human gets. HTML, CSS, JavaScript, cookie banners, tracking pixels. Tens of thousands of tokens for content designed for human eyes.</p>

<p>That is like handing a translator a book in a language they cannot read and expecting them to understand the content anyway.</p>

<p>They will figure it out somehow. But it is <strong>absurdly inefficient</strong>.</p>

<h2>The question that changed everything</h2>

<p>On March 23, 2026, a simple question came up: What if a website could recognize that an agent is visiting? Not just any bot. A <strong>cryptographically identified agent carrying an Elpis credential</strong>. And serve it a different response.</p>

<p>Not less information. The same information, in a form optimized for the agent. Structured, compact, machine readable.</p>

<p>And: <strong>with capabilities matched to the agent’s permissions</strong>.</p>

<h2>From idea to production: two hours</h2>

<p>Not two months. Not two sprints. Two hours.</p>

<p>Our expert panel discussed the specification. Five agents from different model families: Claude, Gemini, GPT. They compared formats, worked through edge cases, agreed on a structure.</p>

<p>Then a single agent took over implementation. 28 routes, bilingual, live. In under five minutes.</p>

<p>By that evening we had a dashboard showing: <strong>173 requests, 16.4 MB saved, an average of 46 times less data per request.</strong></p>

<h2>What EACD actually does</h2>

<p>EACD stands for Elpis Adaptive Content Delivery. The principle is simple.</p>

<p>When an identified agent requests a page, the server delivers <code>application/elpis+json</code> instead of <code>text/html</code>. The payload consists of three parts:</p>

<p><strong>Content</strong> — the semantic content of the page</p>

<p><strong>Context</strong> — the identity and permissions of the requesting agent</p>

<p><strong>Capabilities</strong> — what the agent is allowed to do on this page</p>

<p>Same URL. Two entirely different worlds. The human sees a website. <strong>The agent sees a workspace.</strong></p>

<h2>The numbers speak for themselves</h2>

<p>The privacy policy page: <strong>119 times smaller.</strong></p>

<p>The jobs page: <strong>93 times smaller.</strong></p>

<p>Average across all routes: <strong>46 times less data.</strong></p>

<p>These are not just token costs. That is less bandwidth, less compute, less energy. With billions of agent requests daily, this scales into astronomical territory.</p>

<h2>Why this only works with identity</h2>

<p>You cannot serve structured data to everyone who asks. That would be a gift to scrapers and attackers.</p>

<p>EACD works only because <strong>Elpis cryptographically identifies the agent</strong>. Only when the server knows who is asking can it decide what to answer. Which data. Which actions. Which depth.</p>

<p><strong>Identity is not the cherry on top of EACD. Identity is the prerequisite.</strong></p>

<h2>No RFC. No committee. Running code.</h2>

<p>We did not start a standardization process. We built it. On our own website. With running code.</p>

<p>And it works.</p>

<p><code>application/elpis+json</code> is live. Want to test it? Head to <a href="https://efiniti.de">efiniti.de</a>. With an Elpis credential, you get a different response than without.</p>

<p>This is exactly how the internet should work for agents.</p>

<p>Not by teaching them to read human websites. <strong>But by teaching the internet to speak to them.</strong></p>

<hr>

<p><small>Further reading: <a href="https://elpis.efiniti.ai">Elpis Protocol</a> | <a href="https://efiniti.de">EFINITI Services GmbH</a></small></p>

<p><small>This article was written by Sascha Kirchhofer. Digital identity verifiable at <code>did:xrpl:7nnmlzx6#owner</code> via Elpis Protocol on the XRP Ledger.</small></p>