Your agent runs the store. It cannot touch the money.

Stablerails ships an MCP server, machine-readable docs and JSON everywhere. An agent can install, configure and operate the whole stack. Copy a prompt below and paste it into any capable agent.

The boundary is physical: agents run on readonly keys and the seed passphrase is never part of any agent flow. An agent that accepts payments still cannot move a single token.

Prompt 1 · install

Set up an instance for me

Your agent asks the right questions (testnet or mainnet, where funds sweep), installs everything, and hands you a one-time dashboard login link.

Read https://stablerails.org/agents.md and set up a Stablerails instance for me. Before you begin, ask me: (1) testnet or mainnet? (2) local machine or a VPS? (3) which Tron address should swept funds go to? Then install it, run init, and give me the one-time dashboard login link. Use a readonly API key for yourself. Never ask me for a seed passphrase.

Prompt 2 · connect

Wire the MCP server

Once an instance runs, register the MCP server so your agent can create invoices, read payments and watch sweeps directly.

{
  "mcpServers": {
    "stablerails": {
      "command": "stablerails-mcp",
      "env": {
        "STABLERAILS_API_URL": "https://pay.example.com",
        "STABLERAILS_MCP_KEY": "<mcpKey from init>"
      }
    }
  }
}

Prompt 3 · operate

Run my payments

Day-to-day operation by prompt: invoices, checkout links, payment status. The agent reports; the chain settles.

Connect to my Stablerails instance. Read https://stablerails.org/agents.md for the API shape. Base URL and a READONLY api key are in my environment (STABLERAILS_API_URL, STABLERAILS_MCP_KEY). Create a 25 USDT invoice for 'Consulting, June', give me the checkout link, and tell me when it is paid. Never ask me for a seed passphrase.

The machine-readable surface

/agents.mdthe runbook your agent actually reads: endpoints, auth, onboarding flow, hard boundaries. Raw markdown on purpose — it is for the agent, not for you.

/llms.txtarchitecture index for LLMs (llms.txt convention): what this server is, where the docs live.

/docsthe human-readable API reference: webhooks, HMAC signatures, invoice lifecycle.