Skip to main content
uatu publishes its documentation in formats that coding agents can read directly. Use a Markdown page for a focused task, llms.txt for documentation discovery, MCP for ongoing search, or the OpenAPI document to generate a typed client. The documentation is public. Your application still needs an API key to request a quote from https://api.uatu.dev.
Do not paste an API key into a prompt or send it to the documentation MCP server. Keep the key in server-side secret storage and load it at runtime.

​
Choose a context source

Start with llms.txt for most tasks. It is an index that lets the agent find and read only the pages it needs. Use llms-full.txt when the agent cannot fetch linked pages or when you need a single offline snapshot. You can also append .md to an individual documentation URL to retrieve that page as plain Markdown:
A concise starting instruction is often enough:

​
Connect the documentation MCP server

Connect MCP when an agent needs to search and revisit the docs throughout a longer task. The server is public and read-only with respect to the uatu API:
Once connected, the agent can search the documentation, read pages, and report documentation feedback. The server cannot create quotes, sign transactions, or access your API key.

​
Generate a typed client

Use the OpenAPI document when the task is primarily about request and response types:
It defines the API endpoints and schemas consumed by tools such as openapi-typescript and openapi-generator. Generated types help prevent agents from borrowing incompatible field names from other swap APIs.

​
Use a constrained implementation prompt

Tell the agent what to build and which safety boundaries it must preserve. Adapt this template to your project:
Documentation access and transaction authority are separate. An agent may read these docs freely, but your application should still require explicit user confirmation before a wallet signs or broadcasts a quote step.