Hey team - we’re running into a blocking issue with the Twitter (X) API while using Composio’s managed Twitter integration, and wanted to flag it + understand options. What’s happening • Both TWITTER_RECENT_SEARCH and TWITTER_FULL_ARCHIVE_SEARCH are failing • Error returned: UsageCapExceeded • This indicates the monthly product cap for the connected Twitter account has been reached Impact • Step that fetches tweets (up to 50 recent tweets) fails entirely • As a result, downstream steps (LLM filtering, drafting replies, posting) cannot execute • Retries or fallbacks don’t help since this is a hard monthly cap, not a rate limit Context • We are using Composio-managed credentials, not our own Twitter Developer account • So the quota appears to be tied to the shared / managed Twitter API plan behind Composio Questions 1. When does the Twitter usage cap reset for the managed integration? 2. Is there a way to: • Increase the quota? • Switch to a higher-tier managed plan? • Or bring our own Twitter API credentials to avoid shared caps? 3. Do you recommend any best practices to avoid hitting the cap so quickly (eg caching, lower frequency, etc.) when using managed integrations? Happy to provide logs or exact timestamps if useful. Thanks in advance - this is currently blocking production workflows.

Hey @DanielFrey, Twitter has strict API limitations, and you might've received a rate limiting error due to the same. As a workaround, you can use your own OAuth credentials to avoid rate limiting issues. Let me know if this works for you?

@Uday Thanks for the reply! Just to clarify - this doesn’t appear to be a short-term rate limit. We’re consistently receiving a UsageCapExceeded error (not a per-minute / per-window rate limit), and it’s happening across: • TWITTER_RECENT_SEARCH • TWITTER_FULL_ARCHIVE_SEARCH (fallback) From our understanding, this error indicates that the monthly product usage cap for the Twitter API has been exhausted on the managed integration, rather than a temporary throttling issue. A few follow-up questions to help us move forward: 1. Can you confirm whether the Composio-managed Twitter integration uses a shared monthly quota across customers? 2. If so, when does that monthly usage cap reset? 3. Is bringing our own Twitter OAuth / Developer credentials the recommended way to get: • A dedicated quota • Predictable limits for production workflows? 4. Are there any visibility tools (usage metrics, remaining quota) when using managed integrations? Happy to switch to our own credentials if that’s the intended path - we just want to make sure we’re solving the right problem (monthly cap vs rate limit). Thanks!

@DanielFrey, yes, due to high demand of our OAuth app, it is recommended to bring your own credentials to have complete access over your usage.

Thank you very much