Composio Pricing in 2026: Plans, Tool Calls and the Twitter (X) Data Bill

Searches for Composio pricing land on two different tables, and most confusion comes from mixing them. The Platform list is for developers who build agents with the Composio SDK or its MCP gateway and pay for tool calls their agents make. The Composio for you list is a seat-based product for teams that connect their own apps (Gmail, Slack, GitHub and so on) to AI clients such as Claude, Codex and Cursor.

Which one applies to you. If code you wrote calls Composio (the SDK, sessions, triggers, an MCP endpoint your agent uses), you are on Platform pricing. If people on your team click through Composio to give their AI assistant access to work apps, you are on Composio for you. Composio's own FAQ on the team page points SDK builders to the Platform list.

The change behind old numbers. Composio states that the current Platform pricing applies to signups on or after August 15, 2026, that existing customers stay on their earlier plan through December 31, 2026, and that Instant tool calls are billed for all customers from September 10, 2026. Figures you see quoted elsewhere for older tiers describe that earlier pricing; we only use what the live page shows.

Hobby, $0. No credit card. 100,000 tool calls a month, of which up to 20,000 can run on Composio-managed apps; 50,000 trigger events a month (up to 10,000 on managed apps); unlimited connected accounts on your own apps (the first 1,000 free on managed apps); 3 team members; $2 of one-time credits for Instant tools and Google Maps; audit logs for the last 30 days; custom tools and MCP servers shared across the project. Composio calls the plan hard-capped: at a cap, usage pauses until the next month or an upgrade.

Pro, $29/month. Everything in Hobby, plus $29 of monthly credits that expire at the end of each billing month (no rollover), unlimited team members, API rate limits of 10,000 requests per minute (Hobby is 2,000), spend caps per meter, private toolkits per end user, a read-only dashboard role, a self-serve DPA, and paid add-ons. Past the free allowances, usage is billed against the credits and then the rate card.

Enterprise, custom. Committed volume and discounts, annual invoicing, SSO and SCIM, customer-managed keys, advanced white-labeling, MSA / DPA / BAA, dedicated support with SLAs, and custom integrations on request. No public price.

What a tool call is. Composio counts each tool execution once; its example is that sending an email or reading a file is one tool call. Meta tools such as tool search are free. Triggers are billed per event delivered to your webhook, not per poll. Sessions are free to create.

Everything beyond the free allowances is metered. These are the Pro rates as Composio lists them (in credits, where one credit is one US dollar of balance); Hobby stops at the free amounts instead of charging.

Managed-app tiers. After the 20,000 free managed calls, apps such as Salesforce, YouTube, Reddit, LinkedIn and Google Ads bill $0.01 per call; Gmail, Google Calendar, Slack, Google Sheets, HubSpot, Jira and Discord Bot bill $0.002; all other managed apps bill $0.0005. Google Maps is charged from the first call, from $0.01. Composio notes the per-app managed pricing applies to signups on or after November 3, 2026.

Add-ons that apply automatically. Shared-connection calls (+$0.0003 after 1,000), direct execution outside a session (+$0.0001 after 10,000), proxy execute for endpoints Composio has not wrapped (+$0.0002 after 1,000) and sandbox execution (+$0.0001 after 10,000). Opt-in add-ons on Pro: Firewall at $0.50 per million tokens, BAA (+$0.0003 per call), IP allowlist and zero data retention (+$0.0001 per call each), and advanced white-labeling at $0.30 per connection, once.

Instant tools. A separate catalog of third-party services that run on Composio's provider accounts, billed from your balance at each provider's rate with what Composio calls 0% markup, plus the regular tool-call charge. Instant usage sits outside plan allowances.

Free, $0. Up to 3 members, 10,000 tool calls a month, $2 of one-time credits, up to 3 custom MCP servers, and sharing of up to 5 connections (and 25 skills). Firewall, SSO and zero data retention are not included. On Free, app tool calls stop at 10,000 a month; Instant tools remain pay per use.

Standard, $18 per seat/month. Every member is a seat. Each seat adds 10,000 tool calls and $18 of credits to one pool the whole workspace shares; the pool resets each billing month with no rollover. Standard adds any number of custom MCP servers, sharing of all connections and skills, Firewall, SSO and zero data retention, and pay-as-you-go for extra usage.

Extra calls cost more here than on Platform. Extra app tool calls are listed at $0.005 per call, and Composio's own FAQ says $18 of credits covers 3,600 extra app tool calls. That is roughly 17x the $0.0003 Platform overage, which is the right trade if what you are buying is seat management, SSO and policy controls for staff rather than metered agent traffic.

Enterprise adds bring-your-own-cloud deployment, custom connectors for internal apps, SCIM, SIEM log streaming, forward-deployed engineers and a dedicated Slack channel with SLAs; IT admins get free seats. Price on request.

Composio's Twitter toolkit lists 84 tools and 0 triggers, with OAuth 2.0 auth. Its docs answer the key question directly: as of February 2026 Composio-managed credentials for Twitter were removed (the changelog entry is dated February 12, 2026), and you must create an X developer account, get API credentials from the X Developer Portal and set up a custom auth config. The toolkit's FAQ also covers UsageCapExceeded, 403 and client-not-enrolled errors, all of which come from the X developer project behind it.

What that means for cost. Every read the toolkit makes is an official X API call on your developer account, billed on X's pay-per-usage rate card: $0.005 per post read, $0.010 per user read, $0.010 per follower or following read, $0.015 per post created and $0.20 per post created with a URL, with pay-per-usage capped at 3 million post reads per monthly billing cycle (Enterprise above that). X deduplicates a resource within a 24-hour UTC day. X gives $20 of credits when you save a first card and buy credits, and matches a first auto-recharge up to $50.

Where Composio's fee lands. Because the toolkit runs on your own app, it uses the own-app meter: free inside the 100,000 monthly calls, then $0.0003 per call on Pro. The toolkit's recent-search tool takes max_results from 10 to 100 per page and can paginate internally up to 2,000 results, so 1,000 posts are 1 to 10 tool calls: at most $0.003 of Composio fees against a $5.00 X bill.

Recent search only covers 7 days. The toolkit's TWITTER_RECENT_SEARCH searches the last seven days; older posts need the full-archive search tool, which is also an X API read billed per post.

Composio lets you bring your own tools and MCP servers alongside its catalog (shared across the project on Hobby, private per end user on Pro). That is the route that keeps Composio as your tool layer while moving the X data bill off the official API: add the TwitterAPI.io hosted MCP server as a custom MCP server. It needs no X developer account and no X login for reads.

The server values. The hosted endpoint is https://mcp.twitterapi.io/mcp over streamable HTTP, authenticated with an Authorization: Bearer header carrying your TwitterAPI.io API key; the same server also ships as the npm package @twitterapi_io/mcp-server (MIT, version 0.2.0 at the time of writing) for clients that run local stdio servers. The JSON below is the entry most MCP clients accept; paste the URL and header into whatever custom-server form your client or gateway shows.

How it bills. Each MCP tool call is billed like the matching REST call: tweet endpoints are 15 credits per tweet returned, $0.15 per 1,000 tweets, with a 15-credit minimum per request, so a search that returns nothing costs $0.00015 and a full 20-tweet page costs $0.003. Profiles are 18 credits per user, $0.18 per 1,000 profiles. On the Composio side each execution of the server's search_tweets tool is one tool call on the own-app meter.

Or skip the tool layer for X. If the agent is your own code, the simplest path is a direct GET /twitter/tweet/advanced_search with an X-API-Key header: no Composio meter at all for that tool, and Composio keeps handling the apps where its OAuth management actually saves you work. The full script at the end of this page does that and prints the three route costs side by side.

Writes, if your agent posts. Composio's toolkit posts through the X API at $0.015 per post ($0.20 with a URL). TwitterAPI.io write actions run through an authenticated session: one /twitter/user_login_v2 login ($0.10, with a proxy you supply) returns login_cookies, and each post, like, retweet, follow or media upload (/twitter/create_tweet_v2, /twitter/follow_user_v2 and so on) is then 60 credits, $0.0006. The call acts as that account, so X can rate-limit, lock or suspend it; keep a human pace, expect the session to need a re-login now and then, and note every HTTP 200 call is billed.

Plan prices matter less than the data bill once an agent reads X at any volume. The table holds the Composio plan fixed (inside Pro's 100,000 free own-app calls, so the Composio fee is $0 in every row) and varies only who serves the posts.

Reading the table. The X column is $0.005 per post read from X's pay-per-usage rate card; the TwitterAPI.io column is $0.15 per 1,000 tweets returned; tool calls assume one call per 20-post page, the page size we measured on every one of 38 non-empty search pages. At a million posts the MCP route still uses only half of the 100,000 free calls. X's pay-per-usage plan stops at 3 million post reads a month; TwitterAPI.io has no monthly read cap, and its rate limit is 0.2 requests per second before the first payment and 20 once paid (50 on Scale, 500 on Business, up to 1,000 on request).

Polling agents. Composio's Twitter toolkit has no triggers, so an agent that watches X has to poll. On TwitterAPI.io an empty check costs the 15-credit minimum, $0.00015: a check every 60 seconds for a month is 43,200 checks, $6.48 as a floor, and every 5 minutes is $1.30. Each check is also one Composio tool call if it runs through the MCP route, and 43,200 calls fit inside the Hobby allowance.

We read three slices of public X data. The official account. @composio has 26,415 followers; its last 198 posts span 186 days, about 1.1 a day, of which 39.4% are original posts, 35.4% reposts and 25.3% quotes. Median views per post are 4,276 (p90 73,255). By our keyword rules 18.7% name an agent client such as Claude, Codex or OpenClaw, 13.1% are launches or announcements, 12.1% touch price or credits, and 0.5% mention X or Twitter data.

Everyone else naming Composio. A Latest search for composio -from:composio returned 460 posts from 259 distinct authors in 4.9 days, about 95 a day. 72.8% are replies, 80.4% are in English, the median post has 46 views and 32.2% come from accounts under 1,000 followers. Only 15.2% touch pricing, cost, credits or plans; 18.9% name an agent client, 7.2% mention MCP, 5.9% compare it with something, and 1.7% use complaint words.

The pricing conversation. A second search adds pricing words (pricing, price, cost, expensive, cheap, credits, tool calls, plan, free). It returned 300 posts over 97 days, about 3.1 a day. 44.0% mention free or Hobby, 29.7% quote a dollar amount, 20.0% talk about tool calls or credits, 35.0% name an agent client and 18.3% draw a comparison. Complaint words appear in 9.3%. The figure quoted most is $2, in 25 posts: the one-time Hobby and Free credit for Instant tools.

What it tells a buyer. Day-to-day talk about Composio is about which clients and apps it connects, not about price: pricing is a minority theme even in a pricing search, and complaints are rare. X data itself barely comes up (0.4% of the general sample), which fits a toolkit that now needs your own X developer app. If X is the data your agent needs most, the cost decision sits with the X data source rather than the Composio plan.

Question. How much of the X conversation about Composio is about pricing, what the official account posts about, and how many posts one TwitterAPI.io search page returns (the input to the per-1,000-post cost model).

Accounts and queries. The @composio profile and its last 198 timeline posts via /twitter/user/info and /twitter/user/last_tweets; two Latest searches via /twitter/tweet/advanced_search: composio -from:composio (460 posts, the search ran out after 24 pages) and the same term plus pricing words, excluding the official account (300 posts).

Window and size. The most recent matching posts at collection time, collected in 2026: 186 days for the timeline, 4.9 days for the general search, 97 days for the pricing search. 958 posts in 50 requests, about 14,403 credits ($0.144).

Method. Themes are transparent keyword rules (published in the study's analyze.py); a post can match several. Page size is the count of posts in each non-empty search page. Prices in the cost model were read this session from Composio's two pricing pages, Composio's Twitter toolkit docs, X's pricing page and TwitterAPI.io's pricing.

What the sample cannot show. Keyword rules miss sarcasm and context, and "free" also matches unrelated uses. A five-day general sample reflects that week's launches. Search returns public posts only, and the study says nothing about how many teams pay for Composio or what they spend.

Privacy. Aggregates only. @composio is an organization account; posts by individuals are counted, never quoted, named or profiled, and raw search pages were not stored.