1
Create an API key
Settings → API keys. Store it in your vault, not in git.
APIs · Step 1
Settings → API keys. Store it in your vault, not in git.
Product / APIs
APIs
REST keys, inbound webhooks, and MCP so your agents and apps can drive Swiftmark.
Generate a poster or fire a workflow from your own code — or bring your own AI keys.
Who it is for
Agencies and product teams who already have a site or an internal agent.
What you get
API keys, webhook endpoints, MCP tools, BYOK.
What we do not pretend
Keys are secrets. Do not paste them into Studio prompts or client decks.
Use cases
Would this actually happen in your week?
Inbound webhook
Your form POSTs to the workflow webhook.
Automation runs without a human export.
Poster from your app
Call the generate route with the brand kit id.
Your product site can mint a poster with the same kit Studio uses.
BYOK cheaper seat
Org brings OpenAI / Gemini keys in Settings.
You still use Studio UX; you pay the model vendor directly.
How to use it
The same screens you will click after you sign in.
Recreated from the live product so you can follow along before you create an account. Red circles mean a count or a remove — they are not decoration.
2
Call a route or MCP tool
REST for apps, MCP for agents that already speak tools.
APIs · Step 2
REST for apps, MCP for agents that already speak tools.
3
Handle the webhook
Verify and act. Failures retry from the workflow run.
APIs · Step 3
Verify and act. Failures retry from the workflow run.
4
Watch usage
Credits and errors stay on the org, same as the UI.
APIs · Step 4
Credits and errors stay on the org, same as the UI.
Usually next
Studio
Write what you need, pick a brand kit, and Design Graphic. Studio copies logo, colors, and style posters — then you publish.
See how it works →
Brand kits
Logo, colors, voice, social handles, and style posters. Studio copies from the kit you select.
See how it works →
Automation
Workflows with webhook triggers and six action types, stored on the organization.
See how it works →