Skip to main content
In short: DeFiLoops publishes two files so another agent can find it and learn what it does without a human. The agent card at https://app.defiloops.com/.well-known/agent-card.json lists what an agent can call as skills. The agent guide at https://app.defiloops.com/llms.txt explains how to sign in, call the gateway, pay, and verify webhooks, in plain text a model can read. Both are public and need no sign-in. Both are generated from the same catalogue the product runs on, at the time the service starts. They are never copied by hand, and a test holds the served files equal to the committed ones.

​
The agent card

The card follows the A2A (agent-to-agent) format. It names DeFiLoops, points to the gateway and its OpenAPI document, and lists the operations an agent can call as skills. It lists only operations an agent can actually call and that the service offers now. When DeFiLoops turns a venue on, the card gains that venue’s published operations and nothing else. When an operation is not offered, it is not on the card.

​
The agent guide

llms.txt is written for a model rather than a person. It carries:
  • the links a developer needs first: the OpenAPI document, the catalogue, the plan schema and the card;
  • the sign-in steps and the route list;
  • the public MCP endpoint and what it answers without a token. → Connect your own agent
  • how payment works: x402 is the only way to pay a paid route;
  • how to verify a webhook, step by step;
  • every operation an agent can call, with its networks and what it does;
  • the template agents, each with an agent view that states every fact about it. → Hire a template agent
The contract is the OpenAPI document. The guide is generated from the same table and is only a reading aid.

​
The on-chain identity file

Each template agent is registered on the ERC-8004 agent registry on Base. DeFiLoops serves the registration file for its domain at https://app.defiloops.com/.well-known/agent-registration.json. It lists every agent registered under the domain, so a reader can check that a registry entry and this domain agree.

​
Under the hood

The files are built when the service starts. A file that cannot be built answers 503 and is never cached, so a broken file degrades the page rather than the service. A cache may keep either file for five minutes. A prod check compares the served card with the card generated for the venues that are on, so a card that drifts from what is offered fails the check.