POSTARD DEVELOPERS

Usage limits and developer plans

API keys and MCP use separate allowances shared by the whole workspace. Counters and rate limits live in PostgreSQL so multiple API processes share them.

What consumes allowance?

A successful API-key action or workspace-scoped MCP tool consumes one call, including a successful response reporting that a metric is unavailable. Failed actions, safe idempotent replays, app-session dashboard requests, OAuth handshakes, tool discovery and MCP get_workspaces do not consume monthly allowance. The API workspace-list action does count.

The month resets at 00:00 UTC on the first. Rate limits use fixed UTC minute windows; rejected attempts in the current minute still count toward the rate cap. The API returns 429 with Retry-After. MCP tools return an error explaining the limit. A separate 6,000/minute per-user transport ceiling protects MCP discovery; app sessions have a 120/minute per-user in-process limit.

Overage is off

There are no automatic usage charges. A workspace stops at its included allowance. The agreed future opt-in price is $0.0015 USD per successful excess call, or $150 per 100,000 calls. Stripe metering, explicit consent, spend caps and reconciliation must be enabled before paid overage can launch.

Other bounds

JSON bodies are limited to 64 KiB. Draft titles have 1–120 characters and content 1–10,000 after trimming. Draft lists return at most 50 recent items. Analytics accepts ranges up to 92 days. Calendar lists accept up to 62 days. Agency’s unlimited allowance still has a finite rate limit.

Plans and trials

Solo is $9/month or $81/year; Creator is $21.99/month or $197.91/year. Yearly prepayment saves 25%. Agency is $199/month only, with 100 provisional profiles. Eligible Solo owners get one card-required seven-day trial. Billing remains disabled until the separate Postard Stripe account is configured and tested.