Skip to main content
The v1 API does not expose a universal cursor, page, or offset contract. Do not send generic pagination parameters to every collection.

Collection behavior

The Billing UI requests up to 500 usage records and paginates 25 at a time in the browser. Those page numbers are not server cursors.

Job concurrency

The shared slot means a running SEO refresh can block a measurement start, for example. A prompt-regeneration or page-evaluation job uses its own kind-specific guard. An active-job conflict returns HTTP 409. The research start limit can return HTTP 429.

Measurement caps

The CLI-only Deep preset has a 150-prompt cap and three repeats.

Workspace and prompt bounds

Other input bounds

Route schemas remain authoritative. A generated operation can apply a narrower enum or format in addition to the limits summarized here.

Metered operation ceilings

These limits come from the current versioned pricing configuration. They cap authorization; they do not promise that every operation will use the full amount.

Recommendation generation caps

One SEO generation operation creates at most 20 items toward a target of 50 open items. One GEO operation creates at most 10 toward a target of 20. Open means Proposed, Todo, or In review. These are volume controls, not pagination.