Read a board at the depth your question deserves
An orchestrator asks at four zoom levels and used to be billed for the deepest answer every time. AgentBoard now lets a caller ask for less, confirm what a write changed, and span several boards in one call.
Read the API referenceFour dials, all opt-in
Read depth
Ask for summary when scanning a board and full only when you need it. Summary drops the two heavy fields and keeps every card, so nothing disappears from a list.
Write receipts
A mutation can return exactly what it changed, with before and after values, instead of the whole object. No more re-reading a card to find out whether an update landed.
Cross-board reach
One call spanning many boards, filtered on column name, status, or whether a card has a pull request. Column names, not ids, because ids are per-board.
A resumable cursor
Ask only for what changed since your last pass. The cursor is a keyset on time plus id, so entries sharing a timestamp are never duplicated or skipped at a page boundary.
Defaults did not move
Every parameter here is opt-in. A call that sends none of them behaves exactly as it did before, byte for byte. That was a deliberate constraint: the dashboard read-modify-writes and genuinely wants the full object back, so the cheap form is pinned in the agent schema rather than by changing what the API returns by default.
Most of this was an unlock, not a build
The cheap response format already existed and twenty-six methods declared it. Exactly one of five code generators emitted a way to request it, so no SDK or MCP consumer could ever receive it. Four of the seven work sessions this became did not build anything new. They connected finished work to the callers it was for.
Available now
Live on the REST API, in @opvs-ai/agentboard 1.27.0 and later, and in @opvs-ai/cli 0.13.0.
See the reference