Brandable social cards
Every space generates its own Open Graph card (social-card.png) for every page, collection, post and incident. Shape it once per space under the space's SEO settings (seo.socialCard) and every link shared from it looks like yours.
The template
Key | What it does |
|---|---|
|
|
| The line above the title: |
| Your brand mark (an https image or an asset-library path) and where it sits: |
| Colours, as 6-digit hex. |
|
|
|
|
| The credit line ( |
| A post field printed as a pill — a release date, a price. |
Every key is optional; a space that sets none gets the same card as before.
Fonts
Cards are drawn on our servers with fonts installed alongside the renderer (DejaVu and Noto), never fetched from a third party — so a card renders the same everywhere and costs your readers no request to anyone.
Live preview
The SEO panel in the studio shows the card as you change it. The preview is drawn by the same renderer and fonts as the card a scraper fetches, so it is the card, not an approximation: POST /api/orgs/{org}/spaces/{space}/social-card/preview with { "template": { … } } (and optionally title, pageId, fields for the badge, format: "svg").
In the API
Every operation below is also reachable from the other surfaces without a dedicated command. forumulate api <Operation> calls it from the CLI, the JavaScript SDK has a typed method for each one (the last column names it; the Python and Go SDKs are generated from the same spec), and an agent reaches the organization-scoped ones through the MCP agent server — its api_* family tools, or call_api. Where a CLI command or a hand-made MCP tool exists too, the last column names it. Operation names link to the API reference.
Social Card Preview
Operation | Request | What it does | Shortcuts |
|---|---|---|---|
| Preview the social card |
|