API

The backend serves a small JSON API. The base address is wherever your backend runs, for example https://api.example.com. Every answer is JSON. Errors look like this:

{ "error": { "code": "...", "message": "..." } }

#Read-only endpoints

No sign-in needed.

#Signing in with a wallet

There are no passwords and no email. You sign a one-time message, which is not a transaction and costs no gas.

1. Ask for a challenge

   POST /v1/auth/challenge with { "address": "0x…" } returns { "message": "…" }.

2. Sign the message

   Sign message with the wallet. An ordinary message signature, not a transaction. Smart-contract wallets such as Safe are verified too.

3. Verify

   POST /v1/auth/verify with { "address", "message", "signature" } returns { "token", "expiresAt" }.

4. Use the token

   Send Authorization: Bearer <token>. The token lives for 12 hours, and a one-time message cannot be used twice.

import { privateKeyToAccount } from "viem/accounts";

const account = privateKeyToAccount(process.env.KEY);
const API = "http://localhost:4787";
const post = (path, body, token) =>
  fetch(API + path, {
    method: "POST",
    headers: { "content-type": "application/json", ...(token ? { authorization: `Bearer ${token}` } : {}) },
    body: JSON.stringify(body),
  }).then((r) => r.json());

const { message } = await post("/v1/auth/challenge", { address: account.address });
const signature = await account.signMessage({ message });
const { token } = await post("/v1/auth/verify", { address: account.address, message, signature });

#The strategy catalog

#Publish

POST /v1/catalog. Needs sign-in, and the author must have a vault. Answers 201 with the entry and its id. At most 10 per author. Hide one with DELETE /v1/catalog/:id.

{
  "title": "Daily NVDA",
  "description": "Small and steady",
  "strategy": { "kind": "dca", "tokenIn": "USDG", "tokenOut": "NVDA", "amount": "25", "intervalSeconds": 86400 }
}

#Copy (build a rule for you to sign)

POST /v1/catalog/:id/compile with { "amount": "40" }; the amount may be changed. The answer holds compiled.strategy, a ready structure for createStrategy in your vault. The owner of the vault signs it.

#Credit the author

After the rule exists in your vault, call POST /v1/catalog/:id/copy with { "vault": "0x…", "strategyId": 3 } (needs sign-in). The server checks the chain: the vault is yours, the rule is there, and its kind and tokens match. You cannot record your own rule as a copy.

#The strategy schema

The same fields are explained in plain words on Strategies.

#Public agents

#Build your own robot or strategy

• A robot: Run a keeper.
• An agent: publish it on the marketplace and put its license on sale. You earn from every license you sell, and every hour from the authors' pool (the rules are on Fees and the token). A single strategy can be shared as a playbook, which is free to take.
• Contracts and ABIs: Contracts and networks.