Predictable pricing, designed to scale

All existing customers keep their current plans and limits through December 31, 2026.

If you purchase one of the current plans before August 15th, you're treated as an existing customer and keep that plan through December 31, 2026.

No. We'll notify you well before your usage approaches your plan's included allowance, and again when overage billing begins.

Free plan limits are hard limits: we'll notify you well before your usage approaches your plan's included allowance, and at the limit usage pauses until next month or until you upgrade.

We'll notify you in the dashboard and via email well before your usage approaches your plan's included allowance, and again when overage billing begins.

The billing and metrics section of the dashboard shows current usage and billing settings.

Only for the paid plans.

No. Our pricing is based on the value we deliver to you — executions and resource use — not accounts. There is no limit on the number of connected accounts you can have.

No. Failed calls don't count against your limits.

Yes. Requests through the Composio proxy use the same auth and infrastructure as any other execution, so they're billed at the same rate and draw from the same allowance.

No. Invocations of Composio meta tool calls don't count against tool call limits. For example, an agent using the multi execute tool to execute 4 tool calls in parallel would be metered as 4 tool calls, not 5. You can learn more about the meta tools and Composio sessions in our docs.

One item a trigger delivers to you (egress). If email is the trigger, every email delivered counts as one event; a Slack message trigger counts every message; a calendar trigger counts every calendar change. You can use filters to limit what events are delivered to you. There is no limit to the number of triggers that you can create.

You can use filters to limit delivered events to those relevant to your use case and minimize trigger events.

Premium tools are any tool listed in our premium tool pricing. They're separated from regular tools due to the extra expense incurred using them. The price per tool varies based on the cost of serving it. Each premium call is billed as a regular tool call plus a surcharge listed in the premium pricing table. Video generation is not available on the Free plan.

Sessions are the recommended context for executing tool calls — you can learn more in our docs. There is no charge associated with creating a session. Our infrastructure is optimized for session based usage, and we charge a lower price for overage to pass the savings onto our customers.

The sandbox is a persistent Python environment where your agent can write and execute code, with programmatic access to all Composio tools plus helpers for calling LLMs, uploading files, and making API requests. You can learn more in our docs.

When a tool call returns a large response that would waste tokens and context window, Composio mounts the result in a remote filesystem your agent can search.

For some tasks in the sandbox or filesystem, your agent can invoke a sub-agent to process data and preserve its own context window.

You keep ownership of your auth. Instead of letting Composio run the OAuth flow, you generate and refresh credentials on your side and push the current value to Composio when it changes. Works with bearer tokens, API keys, basic auth, basic-with-JWT, and Google/generic service accounts.

Two different things. Bring your own OAuth app means Composio uses your OAuth application — you give us your client ID and secret, and Composio runs the connection and token refresh for you. Self-managed credentials means you run the refresh yourself and Composio never receives your client secret or refresh token at all.

Free is capped at 3 team members; paid plans include unlimited team members.

No — Composio For You is for individual use and doesn't count against usage limits.