Developers
Everything the interface can do, you can do.
Two REST APIs, webhooks into your own systems, and an assistant layer so AI clients can operate a publication directly.
Content API
Read-only and public. Posts, pages, tags, authors, tiers, newsletters and settings, keyed by a content key. This is what powers a custom front end, a static site build, or a mobile client of your own.
Admin API
Read and write. Create and update posts and pages, manage members and tiers, upload images and media, manage newsletters. Authenticated with an admin key exchanged for a short-lived token.
Webhooks
Fire an event at a URL you control when something happens here — a member signs up, upgrades, cancels, or a post publishes. Useful for keeping your own systems in step without polling.
Assistant layer
TribeTale exposes eight actions to AI clients over the Model Context Protocol: list sites, list newsletters, browse posts, read a post, create a draft, update a draft, schedule, publish. Each call carries the caller's own token, and short-lived credentials are minted per request rather than stored.
Included on every plan, free included.
Reference
Full endpoint documentation lives in the API reference. It is generated from the same specification the server validates against, so it does not drift from the implementation.
Your tribe. Your tale.
Your terms.
Start free, bring your list over, and keep every cent your readers pay you.
2,500 subscribers free · no card · 0% of your revenue, ever