Skip to main content
This page records changes to the API and its MCP surface: new actions, changed arguments, changed answers, and anything that would make code written against an older description behave differently. The API is in beta, so it does change. Every response carries an x-goosy-api: beta header for as long as that is true. Pin the version of the API description you generated your client from, and re-generate it after an entry here touches an action you call. Subscribe with the RSS button above to hear about a change without checking.
​
API v1 · beta · retries, paging, key rotation
Safe retries, one way to page, and key rotation.
  • Send an Idempotency-Key header on an action that takes one, and a retry with the same key gets the first result back. The idempotency_key body field still works and is deprecated on the API (removed no earlier than 31 December 2026); over MCP the argument stays.
  • content.status, page.revisions and page.assets take cursor and answer next_cursor. truncated on content.status is deprecated in favour of next_cursor.
  • New action: keys.rotate replaces the key making the call, with an overlap during which the old key still works.
  • MCP tools now carry annotations (readOnlyHint, destructiveHint, idempotentHint), and every MCP result carries structuredContent.
Details: API conventions and MCP conventions.
​
API v1 · beta
Request ids, rate-limit headers and one error shape.
  • Every response carries an x-request-id — yours when you send one, ours otherwise — and it is recorded on the activity trail for the call.
  • Every call that counts against your key’s allowance answers RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset.
  • A refusal at the door now carries ok: false, code and message at the top level, like a refusal from an action. The nested error object keeps the same values and is deprecated: it may be removed after 31 December 2026, and every refusal carries Deprecation and Sunset headers until then.
The rules are in one place: API conventions and MCP conventions.
​
API v1 · beta
The API and MCP surface are available in beta.Every action lives at its own address under /api/v1/tools/, takes a bearer key, and answers ok. The same actions are available as MCP tools with the same names and the same arguments, so an assistant and a script see one surface, not two.The reference is generated from the API’s own description, so it always matches what the service does. Nothing has changed yet — this is where changes will be recorded from here on.