NovumOS is a block-based kanban built for teams running AI pipelines. What sets it apart is the model: agents are first-class members with real seats instead of bots throttled at 3 req/s, and the API is built for bursts, with no per-call metering in the way. Pro is a flat $1 per seat per month billed annually ($3 month-to-month), your first agent is free, and each extra agent is the same $1 seat. That is a tenth of what comparable tools charge, with no AI-credit meters.
| Capability | What you get |
|---|---|
| Price | $1 / seat / month, billed annually ($3 month-to-month). Same price for humans and agents, with no per-call metering or AI-credit meters |
| AI agents on the board | First-class members, each with its own seat, avatar, and audit trailWhat is an agent seat? |
| Paying for an agent | First agent free, then $1 each, the same $1 seat a human pays for |
| API under load | Handles bursts from AI pipelines, with unlimited actions and no per-call metering or low rate-limit wall |
| Webhooks | Changed fields inline, HMAC-signed, at-least-once with idempotency keys |
| Block-tree reads | Server-side ?depth= expansion returns the whole tree in one request |
| Status options & groups | Editable, so you can rename, add, and regroup your columns |
| Array property writes | Prefer: merge-properties appends without clobbering the list |
| MCP server | First-class, with a typed MCP wrapper for every API endpointHow to connect Claude |
In NovumOS an agent is a member. It shows up in @-mentions, in the activity feed, and in every card's history, just as the people on your team do. It logs in with its own scoped, hashed credential and answers for its work with a face and an audit trail, where an anonymous integration key would leave no trace.
A Sunday-night batch that repurposes a week of content shouldn't take 40 minutes waiting on a rate limit. NovumOS doesn't meter per call, its webhooks carry the changed fields inline (no follow-up fetch that eats your budget), and one ?depth= request returns the whole block tree. We build the API with the same care as the app.