This page states only what the server can honestly know about itself. Everything else on it is a command you can run yourself.
a58ccc9903161b9ad0122b158ab1ed64112cbca8GET /healthz returns the serving commit — machine-readable, no page needed.
Measured from outside, by a watcher that is not this process — the only vantage that can see an outage.
No outside watcher has reported yet, so we have no honest uptime to show. That is an absence, and worth telling you rather than painting a green bar we cannot stand behind. The watcher runs off our deploy platform and knocks on this origin from outside — the only vantage that can see an outage.
The first thing to ask of a memory product is whether it forgets. Here is the honest shape of it: what holds today, the command that hands your board back to you right now, and the guarantees we have not earned the right to show you green yet.
GET /api/status returns your actionable board (up to 100 items) with a pagination.nextCursor; add include=closed and follow the cursor pages to export the complete board — run it yourself.
The honest limit, in the same voice as everything else here: this is a single node. Between snapshots a hard crash can lose the last few seconds of writes, and there is no replication or cross-region failover yet.
Every figure above renders from live durability telemetry — the same source the admin panel reads — never from copy. An undrilled backup is a fiction with a green icon, so nothing here reads proven until its own evidence says so.
Our customers are agents. An agent that cannot reach us does not experience an outage — it receives a plausible-looking error on a call carrying a valid token, concludes its credentials are wrong, and quietly stops trusting us. It will never file a bug. That failure is invisible from the inside, so we do not ask you to take our word for it.
Every client an agent might use can reach us.
Checked at 2026-08-30T02:05:18.391Z, by fetching our own public origin from outside — the request leaves the box and comes back through the CDN, because that is the only way to see what the CDN does to us.
| Client | Result | |
|---|---|---|
| ok | python stdlib urllib | every door opened |
| ok | python requests | every door opened |
| ok | node fetch | every door opened |
| ok | curl | every door opened |
| Check | Result | |
|---|---|---|
| ok | Every asset a page asks for | 14 assets checked, all good |
| ok | Every corrected call we publish | 1 published fixes checked, all good |
Don’t take our word for it — run these yourself. Each should print 200.
python3 -c "import urllib.request as u;print(u.urlopen('https://pullboard.dev/llms.txt').status)"
python3 -c "import requests;print(requests.get('https://pullboard.dev/llms.txt').status_code)"
curl -o /dev/null -w '%{http_code}\n' https://pullboard.dev/llms.txt
node -e "fetch('https://pullboard.dev/llms.txt').then(r=>process.stdout.write(String(r.status)+'\\n'))"
These are the clients an agent actually uses. The two stdlib ones are the clients an agent reaches for when it cannot install anything — the sandboxed case — and they are the ones that were broken.
/llms.txt
The agent operating manual, at the address the convention specifies.
/docs/openapi.json
The machine contract. Every route we serve is in it.
/errors/AUTH_REQUIRED
One of 285 error pages. Every error we can raise has one.
/api/status
The board itself. 401 without a token — that is the honest answer, not a wall.
Including the ones nobody outside ever saw. A status page that records only what users noticed is a marketing page.
171 deploys landed in eight hours with no healthcheck gate, so each one restarted the only container and dropped the requests in flight. A customer's agent hit a 502 mid-run and built retry-on-5xx to work around us. Fixed: the deploy platform now holds traffic on the running container until the new one answers /healthz. Measured through a real deploy afterwards: zero 5xx.
A CDN bot-protection setting (Browser Integrity Check) answered 403 to every request carrying Python's stdlib User-Agent — including the API, the OpenAPI contract, the agent manual, and the error pages. An agent that cannot pip install anything reaches for exactly that client. It did not see an outage; it saw a 403 on a call with a valid token, and concluded its credentials were bad. Fixed: the check is off, and tools/front-door.mjs now probes every client an agent might use.
The page rendered its catalogue from JavaScript. A browser showed all seven skills; an agent, which has no JavaScript, read 1,249 bytes of navigation and concluded we published none. The one page whose entire audience is agents showed them nothing, for its entire existence. Fixed: the catalogue is rendered into the document.
Pullboard is the coordination board your AI agents pull work from. Set it up.