/
Developer
Get a key
Knowledge base
Start here
Context
Topics & Planner
Self-serve setup
Phantom
Back to app
Interface →
Capability →
The grid
REST
Plain HTTP · the publish loop
665 tools
Set up →
MCP
The full surface, for agents
665 tools
Set up →
CLI
letterstory, in your terminal
665 tools
Set up →
Content
Read, draft, and publish articles: the words themselves.
49
all tools
49
all tools
49
all tools
Collections
A publication with one config file. run_collection sources, writes, gates and publishes one post.
44
all tools
44
all tools
44
all tools
Canvas & visuals
Canvas style templates, semi-structured compositions, stickers, and table/venn visuals.
21
all tools
21
all tools
21
all tools
Flows
Run editing passes over an article and read the results back.
2
all tools
2
all tools
2
all tools
Seers
Point a seer at a repo, Notion, a spec URL or a news query and turn what it finds into drafts. Connect with a GitHub PAT (set_github_connection) or a Notion secret (set_notion_connection).
28
all tools
28
all tools
28
all tools
Arenas
Research agents that turn a topic into a sourced, fact-checked outline, alone or before a kernel writes.
22
all tools
22
all tools
22
all tools
Writing kernels
Submit a topic/brief to an external writing kernel and get a finished draft written back.
40
all tools
40
all tools
40
all tools
Connectors
Push finished articles out to Webflow, Framer, or Google Docs.
32
all tools
32
all tools
32
all tools
Phantomstory
Sites Letterstory hosts as independent publications: create, configure, add a domain, rebuild. Publish with run_collection.
34
all tools
34
all tools
34
all tools
Mailers
Outbound email. Mailers: domains, warm-up, reply forwarding, suppression. Prospects: lists from CSV or a description. Sequences: multi-step emails with a review queue.
58
all tools
58
all tools
58
all tools
Strategy
Positioning, competitors, and onboarding that steer the writing.
106
all tools
106
all tools
106
all tools
Insights
Search Console performance and The Story's momentum feed. Connect Search Console first in Settings → Integrations → Google Search Console (https://app.letterstory.com/settings?tab=integrations).
58
all tools
58
all tools
58
all tools
Shredder
Run outside content through shredder endpoints: each sentence is rewritten across LLM providers, structure untouched.
16
all tools
16
all tools
16
all tools
Ledes
Turn a prospect's context into scored cold-email opening lines from your editable library.
20
all tools
20
all tools
20
all tools
Landings
Landing pages and when to cite them. Collections with auto-mention link to them in new articles.
5
all tools
5
all tools
5
all tools
The Site
One model of a customer's whole marketing site keyed by host and path: map a host, walk the tree, read what was noticed, and propose, accept or dismiss changes.
33
all tools
33
all tools
33
all tools
Account
API keys, organization profile, branding assets, members, and pending invites.
97
all tools
97
all tools
97
all tools
The grid
Capability
2 tools
Flows
Run editing passes over an article and read the results back.
All 2 tools
POST
get_webhook
Get the webhook destination configured for this API key. `article.published` and `article.finished` (a draft is complete and awaiting review — same fact list_articles's phase='finished' filter reads) notifications are POSTed here. Each delivery is a notification carrying ids, not the article itself — fetch it with get_published. Full headers, payload fields, and retry behavior: /docs/webhooks.
webhook:read
POST
set_webhook
Configure the webhook destination for this API key. Pass webhook_url=null to disable notifications. Pass a webhook_secret to enable HMAC-SHA256 signatures on outgoing deliveries (header: x-letterstory-signature). Deliveries carry an x-letterstory-event header (article.published or article.finished) to tell event types apart, plus x-letterstory-delivery-id for idempotency. Each delivery carries ids only, not the article — fetch it with get_published. Sent once with a 10s timeout and NOT retried on failure; pair with a periodic list_published check as a safety net. Full payload fields per event: /docs/webhooks.
webhook:manage