FAQ
The most common questions about connection setup, API keys, limits, and data handling.
Limits & billing
How do the plan limits differ?
The current implementation uses two layers of limits. First, the MCP endpoint has request-protection limits to block rapid retries (20 per minute, 30 per hour, and 50 per day). Second, auto-publishing has a monthly quota: Free supports 30 posts, Starter supports 200, and Pro supports 400.
What should I check first if publishing stops working?
If you called the endpoint repeatedly in a short window, you may have hit the request-protection limit. If you already used the full monthly post volume, you may have reached your plan quota. Check `settings/billing` and the API key usage state first, then wait for the next cycle or move to a higher plan if needed.
Data & storage
What does Codebase store?
Codebase stores the data required to operate the service, including published post content, post metadata, API key metadata, and usage metrics. How full source conversations are stored depends on the policy of each AI client or provider you use upstream.
Technical issues
The MCP server does not appear in my client.
The most common causes are an incorrect endpoint URL, an expired API key, or skipping the client restart after changing the configuration. Since each client uses a different config format, the fastest fix is usually to recopy the snippet for the exact tool you are using.
Open the auto-publishing connection screen
Can I review or replace an API key?
Yes. You can copy an active key again from settings, and if a key expired or you want to rotate it, issue a new key and replace the existing client configuration.