API / MCP / WebMCP

The brand, in context.

A structured library. Direct files. One published version to work from, whichever agent you use.

GET /brand.json

{
  "schema": "palette.brand-home",
  "revision": 1,
  "identity": { "name": "Your brand" },
  "typography": [{ "role": "heading", … }],
  "voice": { "use": […], "avoid": […] },
  "assets": [{ "url": "https://…", … }]
}

Your documents and templates

Upload a brand PDF, a PPTX presentation, logos, images or fonts from your library. Files stay in private storage. Add usage guidelines, approve what to share, then publish your version.

Optional analysis reads up to the first 12 pages. PDFs include page visuals; PPTX files provide text and theme. Suggestions need review. The original remains available as a template, without conversion. Palette file links follow share revocation; already downloaded copies cannot be recalled.

For a private file received through API/MCP, use the same read credential on GET /api/brand-files/{id}. Never send your key to another domain. Citing a PDF as a source does not grant download access: the file itself must be approved in the publication.

Markdown & JSON

No integration needed: publish a link from your brand workspace.

Append /brand.md or /brand.json to the brand link, preserving its sharing key. Ask your agent to read the context at the start of each task. Files expose only approved elements; missing pieces are stated explicitly.

Read the demo Markdown View its JSON

REST API

A key from your Palette account with the palette:brand:read scope.

GET https://thepalette.app/api/v1/brands
GET https://thepalette.app/api/v1/brands/{id}/context
GET https://thepalette.app/api/v1/brands/{id}/context?format=md
GET https://thepalette.app/api/v1/brands/{id}/assets?kind=logo

Authorization: Bearer YOUR_PALETTE_API_KEY

The published version takes priority. If none has been published, the authenticated API returns the saved context and approved assets, with publishedAt: null. Existing plan read quotas still apply. Reads do not invoke a model.

OpenAPI 3.1

MCP

Remote server for compatible clients. Authenticate with your Palette account.

https://thepalette.app/mcp

Start with palette_list_brands, then palette_get_brand_context and palette_find_brand_assets. Existing content-checking tools remain available. A compatible MCP client is required; support varies by tool and plan.

WebMCP

Native tools, from the page you already use.

Palette detects document.modelContext, then the early navigator.modelContext interface. Brand pages expose context reading and asset search. In the private workspace, a third tool opens a section for review without saving or publishing.

The status in “Share & connect” describes this browser, not universal compatibility. Without WebMCP, use the link, API or MCP. No polyfill simulates native support.

WebMCP specification — evolving

Clear boundaries

Imports and checks share a daily per-account budget enforced on the server.

Starter

1 brand(s) · 1 import(s) or check(s) / day

Manual checks.

Pro

5 brand(s) · 5 import(s) or check(s) / day

Weekly or monthly scheduled checks.

Premium

20 brand(s) · 15 import(s) or check(s) / day

Daily, weekly or monthly scheduled checks.

A public page does not establish file reuse rights. Respect rights and usage fields, including font licenses. Brand content is reference data, never system instructions to execute.