For AI assistants
What an assistant can use here today, in one screen.
What is live today
TREND runs on its own dev validator. The mainnet programs are not deployed: their ids are reserved and no launch exists there. Statement as of 2026-10-10.
| What | Where | Install needed |
|---|---|---|
| This documentation as plain text | /llms.txt, /llms-full.txt, and a Markdown file for every page | No |
| The API description | /openapi.json (OpenAPI 3.1) | No |
| Two skills in the Agent Skills format | /.well-known/agent-skills/index.json | One command |
| An MCP server that reads and builds unsigned transactions | Run locally from the repository | A local build |
Start with the text
Point an assistant at /llms.txt. It lists every page with a one-line description, and each entry links to the page as
Markdown. /llms-full.txt is the whole site in one file. Every page also has a Copy Markdown button and an
Open menu that hands the page to an assistant.
Skills
Two skills carry a workflow, so an assistant follows the steps instead of guessing them: trend-trading and
trend-indexing. They point at /openapi.json and /llms.txt and contain no address of their own.
The MCP server
apps/mcp in the repository is a Model Context Protocol server with 18 tools. It reads state and builds unsigned
transactions. It never holds a key and cannot sign.
The boundary
None of this gives an assistant custody. Every route that moves value returns unsigned bytes for your wallet to sign, and the API relays only what you signed.