Build on Gujo

Gujo Developers explains how programs and agents can work with the products in your Gujo account.

Three ways in

Way	Use it when	Credential
Account API	A script or app reads your library, products, orders or subscriptions	Account API key
MCP	An agent such as Claude or Cursor should do the same through tools	Sign in (OAuth). For CI and scripts, an account API key with the mcp.read ability
gujoctl	You sign in from a terminal and install products you bought	Key from device sign-in (you don't create one yourself)

All three run on the same account API. One MCP tool is one account API endpoint, and gujoctl calls the same endpoints. Key abilities and error codes are therefore the same whichever way you call.

• Creating keys, abilities and errors: Authentication and API keys.
• Connecting an agent: Connect MCP.
• Installing from a terminal: gujoctl.
• Paths, abilities and input fields of every endpoint: API reference.

Product guides

• App distribution feeds: the Sparkle appcast feeds and download URLs desktop apps update from.
• Design Gallery: the screen gallery at design.gujo.ai, the design MCP and agent tokens.

First request

curl https://api.gujo.ai/api/library \
  -H "Authorization: Bearer $GUJO_API_KEY"

Getting started walks through every step from creating a key to connecting MCP.

Formats for agents

• Add .md to any page address to get its raw Markdown. A request with an Accept: text/markdown header gets the same.
• The index of all pages is /llms.txt and the full text is /llms-full.txt.
• The machine-readable account API spec is /openapi.json (OpenAPI 3.1).

Changes are collected in the Changelog.