Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

API

A public Patera API is in development. It hasn't shipped yet. Here's what's planned.

What the API will expose

The first stable surface will cover the things most people automate by hand today:

  • Live Feed stream: a server-sent stream of new tweets matching your filters, identical in payload to what the dashboard receives over WebSocket.
  • Top Performers query: fetch the current ranked set with the same metrics the dashboard exposes.
  • AI Actions: submit a tweet ID plus tone plus action type to get a draft back; submit that draft to a connected account to post it.
  • Tones CRUD: read and write your tone configurations programmatically (same Hook / Shape / Export model as the dashboard tone editor).
  • AI Summaries: fetch the current and historical summaries.

What it won't replace

The API is for operators who want to integrate Patera into their own pipelines. The dashboard stays the main surface. Filters, tone authoring, the visual queue, Execute All: all better done in the UI.

The browser extension also stays the source of session truth for multi-account posting. The API will let you post from a connected account; it won't let you connect new accounts, which still requires the extension's session capture.

Auth model

Auth will use API tokens scoped to a Patera account. Account-level scope is optional. A token can be limited to posting from one X account even if your Patera account has many connected.

Pricing

API access is planned as an add-on to the existing tiers. A per-request component sits on top of your reply, media-analysis and comment-analysis quotas (the three counters your plan already meters). The exact pricing model is being finalised. See Plans for the current quota breakdown.

Timeline and subscribing for updates

No public ETA. There's no signup form for the beta yet. Check back here for updates or reach out through your usual support channel and mention "API beta".

In the meantime

Every feature planned for the API is already in the UI. Filters, tones, multi-account posting, Execute All, AI Summaries: it's all there. The API just lets you wire that workflow into other systems once it ships.