page

Call page.checkpoint

Say what has changed on a site and where it stands now — 'what did you change?', 'what have we got saved?', 'can I go back to before that?', 'why did the last build fail?', 'what version is this on?'. No site id is needed — it works on the site the member has open on screen. It reports where the site's source stands: the checkpoint it is at (current_source_ref — every edit is made from it), the ledger of checkpoints newest first with each one's build status and revision, and the newest build with its failure log tail when it failed. A checkpoint is made by every change to the site's files and by the member's save; use this to name a checkpoint for page.rollback, a revision for page.republish_revision, or to read why the last build failed. Not for undoing a change — that is page.rollback.

Every result names the workspace it ran in. Say which workspace the answer is about. When the account has more than one workspace and none is selected, this tool refuses with workspace_ambiguous and lists the choices — offer them, never pick one.

post/api/v1/tools/page.checkpoint

Request

  • Base URL: https://app.goosybear.ai
  • URL: https://app.goosybear.ai/api/v1/tools/page.checkpoint
  • Auth: HTTP bearer

Headers

x-request-idstring

Your own id for this request, echoed back and recorded on the audit trail. 1–128 characters from A–Z a–z 0–9 . _ : -, starting with a letter or digit; anything else is replaced by a generated id.

Request body

site_idstring uuid

Optional site UUID. You are NOT shown the id of the site open on screen — it never appears in your context, so there is nothing to copy and nothing to look up. OMIT IT ENTIRELY and this call reads that on-screen site; that is the PRIMARY path, not a fallback, and the turn's own surface resolves it server-side. Pass it only when the member explicitly named a DIFFERENT site and you took its id from page.list. Never pass a board, board-item, thread or any other id that merely happens to be nearby — those name different objects and will be refused.

workspacestring

Which workspace to run in — its slug. Omit to use your default. With more than one reachable workspace and no default, the call is refused and the choices are listed.

Response

The call was admitted and dispatched. ok says whether the tool succeeded — a refusal the tool itself produced is still a 200, exactly as it is a successful JSON-RPC result over MCP.

OR

Changes

No recorded changes to this operation across all 6 revisions of this API.