llms.txt and machine-readable docs
Agents read Sendwing best from sources made for them. Each of these is public and always matches the live product.
llms.txt
Section titled “llms.txt”https://sendwing.app/llms.txt follows the llms.txt convention: a short summary of what Sendwing does, every plan with its price and limits, the billing questions, and links to these docs. It’s small enough to read whole.
It’s built with the site from the same pricing data as the pricing page, so its prices are never older than the page’s.
The OpenAPI document
Section titled “The OpenAPI document”https://api.sendwing.app/openapi.json describes every REST route, its parameters, permissions and errors, and every webhook event. It’s generated from the same schemas the API checks requests against, so it doesn’t drift from what the API accepts. The API reference is built from it.
Point code-generating agents at it rather than at the reference pages: it’s the exact contract, in one file.
The MCP server’s guides
Section titled “The MCP server’s guides”An assistant connected over MCP can read how to write for Sendwing from Sendwing itself, with the get_guide tool or as MCP resources:
| Guide | Resource | Covers |
|---|---|---|
sendwing://guides/email |
How to write an email for Sendwing | |
| Workflow | sendwing://guides/workflow |
How to build a workflow |
| Segment | sendwing://guides/segment |
How to write a segment’s filter |
Which to use
Section titled “Which to use”| To | Use |
|---|---|
| Learn what Sendwing is and what it costs | /llms.txt |
| Write code against the API | The OpenAPI document |
| Write an email, workflow or segment through an assistant | The MCP guides |
| Act in a workspace, not just read about it | The MCP server, or the REST API with a key |