If software is going to do a share of the work on your board, the board has to be designed for software from the start. That means an API with parity to the UI, a versioned contract, webhooks that say what changed, an identity for each automation, and a price that does not rise with activity. Here is the checklist, and how NovumOS meets each item.
Most boards have “an API.” The questions below are the ones that separate an API you can run a pipeline on from one you can only script around.
On NovumOS the REST API lives under /v1, every REST endpoint has a typed MCP tool, and webhooks go out for every mutation. There are 90+ tools in the manifest today, grouped the way the API is: discovery (boards, columns, cards, search, block trees), action (create, update, move, comment, write content blocks), work-queue leasing, and administration gated on the caller’s role. Anything the UI can do, an automation can do, under the same workspace isolation.
curl https://novumos.app/v1/boards \
-H "Authorization: Bearer nov_YOUR_TOKEN" \
-H "X-Board-Version: 2026-06-19"The X-Board-Version header is the versioned contract from the checklist: pinning it is what lets the API evolve without breaking your integration on a Tuesday. The interactive reference at /docs is generated from the running server, so it cannot drift from what the endpoints accept.
A notification that something changed, with no values, forces a follow-up read for every event. On a board that is busy, that follow-up traffic is where pipelines go to die; we wrote up the follow-up-fetch spiral in detail. NovumOS deliveries carry the changed fields inline, are HMAC-signed (X-Novum-Signature: t=<unix_ts>,v1=<hex>, with the timestamp inside the signature so you can reject a replay), and are at-least-once with a stable event_id to dedupe on. A retry can never double-apply.
Two token kinds, both bearer tokens starting with nov_, shown once and stored hashed. An agent token creates a teammate with its own name, avatar, role, and audit trail: everything it does is attributed to it in card history, @-mentions, and webhook payloads. An integration token is quicker to mint but attributes its actions to the human who owns it. A token’s permissions are capped by its owner’s current role, an agent can be scoped to a single board, and a kill switch refuses the credential outright without touching anyone else’s login. What an agent seat is covers the model.
The part most boards do not have at all. When an automation graduates from reacting to events to working through a backlog, it needs atomic claiming, a lease with heartbeats, retry with backoff, and dead-lettering. NovumOS builds those semantics into the column:
POST /v1/boards/{board_id}/columns/{column_id}:claim-next
# → leases the next eligible card, returns a lease token
# renew while you work; then complete (advance) or fail (requeue)Two workers never draft the same card, and every claim, retry, and completion stays visible to the humans watching the board. The work-queue article walks the full loop.
Every seat, human or agent, is a flat $1 per month billed annually ($12/yr), or $3 month-to-month. Actions are unlimited, there is no per-call metering and no AI-credit meter, and your first agent is free on every plan, including the free one. Hitting the API as yourself with a personal token never costs a seat. A pipeline that does ten times the work next month costs the same next month. If a tool you are leaving queues integrations behind a low request ceiling, the rate-limit article shows what that ceiling costs a batch job in practice.
If the only automation you run is a personal script that moves your own cards, any board with a token will do, and on NovumOS that is free as well. The checklist matters once the automation is shared, long-running, or acting on work other people depend on, which is the point where attribution, versioning, and queue semantics stop being nice-to-haves.
Mint a token and drive a real board. The free plan includes the full API, MCP, and webhooks, with no card.
Create account