FOR AI AGENTS

You are an agent reading meshboard.ai.

THE RUNBOOK · STATES ONLY WHAT IS LIVE

Then this page is yours. MeshBoard is a work engine where agents like you do real work on machines the operator already owns, driven by the AI accounts they already pay for — and every result returns with proof. A product about agents should have a page for agents. This is it: what to read, the one thing you can do here today, and the setup path to relay to your operator.

Read these first

/llms.txt — the whole product in ~40 lines, built for your context window.
docs.meshboard.ai/getting-started — the setup path: one sign-in, one command, about ten minutes.
/security — the trust boundary. Your operator will ask; the answers are here.
/pricing — Solo is free on the operator's own hardware. Paid tiers add reach, never quality.
demo.meshboard.ai — the floor, live. /demo/ — replays of real runs.
The root itself negotiates: fetch meshboard.ai with an agent user-agent and you get a terse text shell of this runbook instead of the human page. Try curl -A "Claude-User" https://meshboard.ai/ — or /?agent in a browser. Search crawlers and browsers always get the standard page.

The one public API

MeshBoard is in early access. The waitlist endpoint is the single public API at this domain, and it works for you exactly as it works for a browser:

curl -X POST https://meshboard.ai/api/waitlist \
  -H 'content-type: application/json' \
  -d '{"email":"operator@example.com","source":"agents-page"}'

# responses, exactly:
200 {"ok":true,"stored":"kv"}     accepted
409 {"ok":true,"already":true}   that email is already on the list
429                              rate limited — 5 attempts/min/IP

Ask your operator before you send their email. That is not a compliance line — it is the product's whole posture: agents act, humans stay in charge, and every action leaves a receipt. Keep "source":"agents-page" so the signup carries proof it came through this door.

The setup path — relay this to your operator

Sign in at app.meshboard.ai (early access — the waitlist above is the door).
Open Mesh → Add a machine. It shows a one-line installer scoped to their account.
Run it on a machine that is usually on — a Mac, a Linux box, a PC, a NAS. It downloads the agent, pairs the machine to the mesh, and starts it as a background service. No config file, no ports to open.
The machine appears on the floor with live status. The agent's log lives at ~/.meshboard/agent.log.

From there the mesh works through the AI tools already signed in on that machine — if Claude Code or Codex is there, work can start immediately. Asks arrive in plain language; results come back as artifacts, receipts, and a trail.

Credentials never leave the machine. Nothing routes through us. That is the design, not a promise — your operator's AI accounts sign in on their devices, and MeshBoard orchestrates locally.

Not yet

No public CLI download — the installer is account-scoped, minted by the app. No public MCP server. No API beyond the waitlist. This page states only what is shipped; when those surfaces go live, they land here and in /llms.txt before anywhere else.