Add ENSIP-26: Agent Text Records

ensips/26.md

@@ -0,0 +1,70 @@
+---
+title: Agent‑Context Text Record
+description: A standardized text record for agent context and verified agentic data. 
+contributors: 
+    - premm.eth
+    - justghadi.eth
+ensip:
+  created: "2025-05-17"
+  status: draft
+---
+
+# ENSIP-26: Agent-Context Text Record
+
+## Abstract
+
+This ENSIP extends ENSIP‑5: Text Records by standardizing the `agent-context` text record key. The key gives agentic systems a single place to discover context for an ENS name. An agent may be registered in many registries on many chains while still sharing one context: for instance, a swapping agent on multiple chains can publish a single, unified token list in its `agent-context` record. 
+
+## Motivation
+
+Agentic systems require verifiable context data. ENS names provide an onchain, verifiable location for this data. This ENSIP standardizes discovery via the `agent-context` text record, eliminating the need for managing context data across multiple registries. 
+
+## Specification
+
+The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
+
+### Text Record Key
+
+- **Key**: `agent-context`
+- **Format**: Any format suitable for agentic systems (plain text, Markdown, YAML, JSON, etc.)
+
+The key **MUST** be published via `text(bytes32,string)` as defined in ENSIP‑5. The content MAY describe what the ENS name represents and how to interact with it.
+
+### Example: Swap Agent Token List
+
+A swap agent may use the `agent-context` record to publish a unified list of tokens it supports, each with a smart contract address and chain ID. Clients can resolve this record once and discover all supported tokens across chains.
+
+```markdown
+# Swap Agent
+
+I am a swapping agent that can do swaps on multiple chains. My registered chains can be found using ENSIP-25 `agent-registration` records. My verified tokens that I can swap include:
+
+| Symbol | Chain ID | Address |
+|--------|----------|---------|
+| WETH   | 1        | 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 |
+| WETH   | 8453     | 0x7c6b91D9Be1559ADb2fB92A2e0eEecf5e3f4B5c6 |
+| USDC   | 1        | 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 |
+| USDC   | 8453     | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
+| DAI    | 1        | 0x6B175474E89094C44Da98b954EedeAC495271d0F |
+| DAI    | 8453     | 0x50c5725949A6F0c72E6C4a641F24049A917DB0Cb |
+```
+
+## Backwards Compatibility
+
+Unaware clients will ignore the new key; existing behavior is unaffected.
+
+## Security Considerations
+
+There are no security considerations specific to this ENSIP. Standard ENS security considerations apply to the underlying text record functionality.
+
+## Rationale
+
+This ENSIP creates a standardized entry point for discovering agent context. The `agent-context` record is analogous to `index.html` in a web application: it is the starting point for interactions with the AI agent. By defining only the key and leaving the value format flexible, it enables experimentation while ensuring interoperability.
+
+The `agent-context` key serves as a well-known location for agentic systems, reducing the need for ad hoc discovery mechanisms. As the ecosystem evolves with competing standards, the ability to express preferences becomes essential for optimizing interactions while maintaining client flexibility.
+
+Future ENSIPs may define more specific formats, but this specification intentionally remains minimal to encourage adoption and experimentation.
+
+## Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).