Free vs Pro

Every endpoint exists on Free — Pro removes ceilings rather than unlocking hidden routes. Account, chat, contact, group, media and status reads all work on Free, and so does sending plain text. The exceptions are the three history reads — GET /messages, GET /ai-context and GET /polls/{messageId} — which are Pro. When a call needs Pro, the server replies 402 with the missing feature named, so your client can show the right upgrade nudge.

Capability matrix

Which reads are free

Listing accounts, chats, contacts, and groups; reading anti-ban status; browsing the media archive; and inspecting the queue, sync, network, webhook, and key state are all GETs available on Free with a read-scoped key.

Three reads are Pro, all gated by localMessageCache: message history (GET /v1/accounts/{id}/messages), the AI-context transcript (GET /v1/accounts/{id}/ai-context) and poll results (GET /v1/accounts/{id}/polls/{messageId}). They return 402 on Free. Messages are still stored on every tier, so upgrading unlocks the archive instantly with no re-sync — and Free can receive messages live over the message.received webhook.

What a 402 looks like

A Pro-gated call returns 402 with the feature flag that gated it:

{
  "error": {
    "code": "license_required",
    "message": "Feature 'apiWriteEnabled' requires a Pro license",
    "feature": "apiWriteEnabled",
    "tier": "pro"
  }
}