MCP
The same token and the same create-order operation. MCP is not a second API. It is another way to send that order from an agent or tool that already speaks MCP.
For developers
Send from your own systems
Connect your product or CRM. We issue a programme token for HTTPS and MCP. Billing is arranged with the token. Shop checkout is unrelated.
How you connect
No public self-serve signup. We issue tokens per programme.
Write to us
Use the contact form with expected volume, the system you want to trigger from, and whether you want status callbacks.
We issue a token
You get a programme token. Use it on HTTPS and in MCP server config: one credential, both surfaces. The live URL arrives with the token.
Send an order
POST the JSON below over HTTPS, or run the same create-order operation through MCP. Quantity is the number of recipients.
Auth
Send Authorization: Bearer <token> on every HTTPS request. Put the same token in your MCP server config. Do not share it across programmes.
Order contract
This is the shape we issue against. The live URL and token arrive together. Quantity is recipients.length. Tokens in the message match the shop, for example {{First name}}. Extra merge fields on a recipient are allowed if they appear in message. The font field is a handwriting style created with AI, written by robots with human handwriting precision. Use the same slugs as the shop: hershey-script (Script), hershey-sans (Sans), and the rest of the faces. Optional callbackUrl receives outbound status: received → writing → posted.
{
"idempotencyKey": "your-id-88421",
"product": "all-the-best-card",
"font": "hershey-script",
"message": "Dear {{First name}},\n\nThank you…\n",
"sender": {
"email": "ops@acme.com",
"name": "Acme"
},
"recipients": [
{
"firstName": "Ada",
"addressLine1": "1 Example Street",
"city": "London",
"postcode": "E1 6AN",
"country": "United Kingdom"
}
]
}Billing
Programme billing is custom and arranged when we issue the token. Shop checkout is unrelated.