Troubleshooting AgenticOS: rate limits (429), credentials, and credit depletion

Rate limit errors (429)

The underlying ChainGPT API enforces a rate limit of 200 requests per minute per API key. Requests that exceed this limit receive a 429 Too Many Requests response. If you see 429 errors, reduce the request rate of your agent so it stays within 200 requests per minute per API key.

Agent not posting due to credit depletion

AgenticOS costs 1 credit per generated tweet, so high-frequency posting adds up and can deplete your credit balance. If your agent stops generating new posts, check your ChainGPT credit balance and top up if needed. Purchase credits at https://app.chaingpt.org/addcredits and monitor usage going forward.

Credential and configuration errors

AgenticOS requires a correctly configured .env file. Copy the example file (cp .env.example .env) and verify that all required variables are set:

• CHAINGPT_API_KEY
• TWITTER_API_KEY
• TWITTER_API_SECRET
• TWITTER_ACCESS_TOKEN
• TWITTER_ACCESS_SECRET

You also need a Twitter (X) developer account and valid Twitter API credentials (OAuth 2.0). Confirm that Bun Runtime (v1.0 or newer) is installed and that you ran bun install before bun start. You can obtain or check your ChainGPT API key at https://app.chaingpt.org/apidashboard

Next step

Review the full documentation at https://docs.chaingpt.org/