Pricing
Starter access for MCP tools, REST endpoints, Chat, Assets, and Magazine — by waitlist approval.
Two meters, both weekly: Chat runs on a usage allowance; API and MCP share one request budget with an hourly rate limit.
Starter
starter- 1K/hr rate limit
- Weekly Chat usage allowance
- 30 days History
- Webhooks
- MCP + REST access
Enterprise
enterprise- 100K/hr rate limit
- Extended limits
- Full History
- Webhooks
- MCP + REST access
Ready for early access?
Sign in to join the waitlist for Starter access and higher plans.
Sign In to JoinFrequently Asked Questions
Two independent meters, both resetting Monday. Chat is capped by a weekly model-usage allowance — at typical use it lasts roughly 60–80 messages per week. API and MCP share one weekly request budget (plus a per-hour rate limit), whether they arrive as REST calls or MCP tool calls.
Starter access is available through the waitlist after approval. It includes 2,500 API/MCP requests per week, a 1,000 per hour rate limit, a weekly Chat usage allowance, webhooks, 30 days of history, and MCP + REST access.
There's one self-serve plan today — Starter — plus Enterprise with custom limits. Paid plans aren't open yet: join the waitlist for Starter or contact sales for Enterprise, and we'll email you when it launches.
We're not charging anyone yet. Paid plans are billed through Paddle, our merchant of record. Paddle shows the available payment methods at checkout.
API/MCP requests beyond the hourly rate limit or the weekly request budget receive a 429 status code. Chat blocks new messages once the weekly allowance is spent. Both unlock again Monday. Enterprise plans are custom.
No, one API key works for both MCP tools, REST endpoints, and Chat.