A lightweight, XML-based schema that enables LLM agents to discover and construct URL-parameter-driven tasks on behalf of users.
v0.1 DraftAUI is a lightweight XML catalog, served at /.well-known/aui.xml, that describes URL-parameter-driven actions a site supports. Large sites can split full task definitions into optional detail files linked from the catalog. Things like searches, filters, form pre-fills, share intents, and configuration links.
The same file serves two audiences: agents parse the XML structure to understand available tasks and construct URLs, while humans can open it in a browser to review what an agent will have access to.
Only describes tasks driven by query parameters. Path-based routing is out of scope.
Descriptions and semantics are written for LLM comprehension, not human documentation.
Each task is self-contained. Agents can use one task or chain several together.
A catalog + detail pattern lets large sites split tasks across files. Agents load summaries first, then fetch details on demand.
A lightweight XML catalog with optional task detail files and an optional CSS companion. No SDKs, no auth flows.
Base URLs should be universal links where possible, opening native app experiences.
Users can open the file in a browser and understand what tasks an agent will access.
aui.xml at /.well-known/aui.xml, describing its URL-driven tasks with typed parameters, constraints, and examples.llms.txt or the well-known path.{origin}{base-path}?key=value&...For large sites with many tasks, AUI supports a catalog + detail pattern: the root aui.xml lists all tasks with lightweight summaries, while complex tasks link to separate detail files via an href attribute. Agents read the catalog first, judge relevance, then fetch only the details they need.
A trimmed AUI document for an online store:
<aui xmlns="https://agentuseinterface.org/schema/0.1" version="0.1">
<name>Example Shop</name>
<origin>https://shop.example.com</origin>
<description>An online electronics store.</description>
<tasks>
<task id="product-search">
<name>Search Products</name>
<description>Search the product catalog.</description>
<base-path>/search</base-path>
<parameters>
<param name="q" type="string" required="true">
<description>The search query.</description>
</param>
<param name="sort" type="enum">
<description>How to sort results.</description>
<options>
<option value="relevance">Best match.</option>
<option value="price_asc">Cheapest first.</option>
<option value="rating">Highest rated.</option>
</options>
</param>
</parameters>
</task>
</tasks>
</aui>
See the full example with three tasks, enum options, validation patterns, and intent-to-URL examples.
The AUI XML namespace is:
https://agentuseinterface.org/schema/0.1
A normative XML Schema Definition (XSD) is available for validation. Include it in your document:
<aui
xmlns="https://agentuseinterface.org/schema/0.1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="https://agentuseinterface.org/schema/0.1
https://agentuseinterface.org/schema/0.1/aui.xsd"
version="0.1">
AUI is intentionally narrow. Here's how it relates to other specifications:
| Specification | Scope | AUI Relationship |
|---|---|---|
llms.txt |
Site-level agent guidance | AUI is discovered via llms.txt. |
| OpenAPI | Full API description | AUI is narrower — URL parameters only, no request bodies, no auth. |
| RFC 6570 | URI template syntax | AUI adds semantics (descriptions, types, constraints) on top of the template concept. |
| MCP | Agent ↔ server tool calls | AUI is stateless and URL-only; MCP is for richer, bidirectional interactions. |
| AASA / Asset Links | App ↔ domain verification | AUI complements these by describing how to construct the URLs they verify. |