Skip to main content
These docs are written for people and for agents. An agent that builds a bot, a keeper or an interface on Knockout can read all of it without a browser. This page shows the three ways in and what to give the agent first.

​
1. The docs as an MCP server

The docs site is a hosted MCP server. A client that connects to it can search every page and read the result.

​
2. llms.txt and the page text

​
3. The skill file

The skill is one file an agent loads before it works on Knockout. It says what Knockout is, how to quote, open, add, close and settle, how to read positions and queued claims, how to handle a refusal, and the limits and hours. It carries no more than a trader needs. Install it where your agent keeps skills. For Claude Code:
Use .claude/skills/rekt-knockout/SKILL.md inside a project to scope it to that project. Another agent that loads SKILL.md files takes the same file in its own skills folder.

​
What to ask the agent

A good first prompt names the outcome and points at the page that has the code:
The Quickstart is a working bot. The agent can run it, change it and extend it. Building an agent is the operating brief for an agent that decides and sends without a person watching each action.

​
Rules to give any agent that holds a key

  • Dry run first. Simulating costs nothing. Sending costs a stake.
  • Start small. The smallest stake is $0.20. See Fees and limits.
  • Keep keys and RPC endpoints out of the prompt and out of logs. Give the agent environment variable names and nothing else.
  • A refusal is information. Branch on the retry class. Do not loop on a refusal that says never.
  • Never sign a second order for the same intent after a timeout. Send the same signed bytes again.
  • At the barrier you receive nothing. An agent must say so to anyone it trades for.
Questions go to support@asymmetra.xyz.