Browse documentation
Reference baselines, compatibility notes, deprecations, and a migration checklist for API and MCP clients.
Connection update · 4 November 2026
For the current hosted MCP server, use https://mcp.citeralabs.ai/mcp. Open Citera Settings → API & MCP → MCP, choose Connect another assistant, sign in in your browser and select the brands your assistant may read. API keys remain an optional manual-client route and a separate REST authentication method. A browser-sign-in connection does not grant content generation or publishing access.
Follow the client setup guides and check the live tool list before relying on an operation. Client support and connection capabilities can evolve. These notes describe documentation and setup changes; they do not announce an unverified backend release.
Reference baseline · 26 October 2026
This baseline records the customer API and MCP contract documented on 26 October 2026. It is a reference snapshot, rather than a new backend release announcement.
REST API: 47 customer routes under
/v1, covering access, visibility, content, publishing, and product workflows.MCP: 39 tools. The wire names retain their
rankad_prefix; use the exact names returned by tool discovery.Current access: API and MCP access are open to all Citera accounts. Effective brands, scopes, enabled capabilities and usage allowances still apply. The hosted MCP connection using browser sign-in is read-only.
Compatibility: REST and MCP share brand bindings, scopes, and allowances. A successful HTTP response does not remove the need to inspect asynchronous job and operation status.
Versioning and deprecation notices
The documented REST routes use the /v1 path prefix. This baseline does not specify a general deprecation notice period or announce any endpoint removal. Check the assigned server’s current OpenAPI contract and these notes before changing a production integration.
Future entries should identify the effective date, affected routes or MCP tools, whether the change is additive or breaking, and the migration steps. A documentation edit date is not a server deployment date.
Migration checklist
Compare
GET /v1/openapi.jsonwith the contract used by your client. Check field types, required fields, allowed enum values, and response envelopes.Discover the brands bound to your key and inspect their capabilities. Keep only the required brands and scopes; do not assume every write capability is enabled.
Run a read-only request with your updated client. Check the response envelope and preserve
request_idwhen reporting an error.For generation and publishing requests, provide an
Idempotency-Keyand reuse it only for retries of the same logical operation. Publishing previews require a key too.Before publishing, create a valid preview and keep its content, destination, and fingerprint unchanged. Read the operation until verification finishes; an accepted operation is not proof that content is live.
For MCP clients, refresh tool discovery. Preserve exact tool names, input contracts, scope requirements, and explicit write confirmations.