Composio Platform API
56
AI ReadinessFoundational (C)56/100
Official vendor OpenAPI document · agent-readyDeveloper ToolsCi CdapiKey86 EndpointsREST
For Agents
Connect AI agents to third-party SaaS tools through Composio: link accounts, configure auth, execute toolkit actions, subscribe to triggers, and inspect logs.
Use for: I want to connect a user's Gmail account to my agent, Execute a Slack send-message action on behalf of a connected user, List all toolkits available in Composio, Set up a trigger for new GitHub pull requests
Not supported: Does not host the LLM, run the agent loop, or store conversation memory - use for connecting agents to third-party SaaS tools and managing auth, execution, and triggers only.
The Composio Platform API powers Composio's tool-use platform for AI agents. It exposes endpoints for managing connected accounts to third-party SaaS tools, configuring auth flows, executing toolkit actions, subscribing to triggers, and orchestrating MCP servers. Agent builders use it to give an LLM authenticated, scoped access to hundreds of external tools without writing per-vendor OAuth code, and to inspect execution and trigger logs for debugging.
Install Jentic One Beta
Connect the Composio Platform API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Composio Platform API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcomposio.dev%2Fcomposio" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcomposio.dev%2Fcomposio" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Composio Platform API.
Link a user account to a third-party SaaS toolkit through a hosted OAuth flow
Execute a toolkit action against a connected account on behalf of an agent
Subscribe to triggers so an external SaaS event invokes an agent webhook
Manage auth configurations so multiple agents share one OAuth client per toolkit
Rotate webhook subscription secrets and event filters
Inspect action execution and trigger logs for debugging an agent run
Manage organization projects, members, and per-project API keys
Use Cases
Patterns agents use Composio Platform API for, with concrete tasks.
★ Multi-Tool Agent Account Linking
Give end-users a single onboarding flow that connects their Slack, Gmail, GitHub, and Notion accounts to your agent. The /api/v3/auth_configs endpoints define reusable OAuth clients, /api/v3/connected_accounts manages each user's linked account, and /api/v3/connected_accounts/link returns a hosted link the user follows to grant consent. Agent builders use this to skip building per-vendor OAuth flows.
Create a connected-account link for user u_42 to connect their Gmail, then poll /api/v3/connected_accounts/{nanoId}/status until it reports active
Tool Execution from an LLM
Run a toolkit action selected by the LLM against the user's connected account. Composio handles the auth injection, parameter validation, and response normalization so the agent only needs to choose the action and pass the inputs. This removes the integration burden when an agent's plan involves multiple SaaS tools in a single chain.
Execute the slack_send_message tool with channel #ops and text 'Deployment complete' on behalf of connected account ca_8821
Event-Driven Agents via Triggers and Webhooks
Wake an agent on real-world events such as a new email, a Stripe charge, or a GitHub PR. Triggers subscribe to upstream SaaS events and Composio forwards them to a webhook subscription registered at /api/v3/webhook_subscriptions with a rotatable secret. Engineering teams use this for incident-response and notification agents that should not poll.
Subscribe a webhook with URL https://app.example.com/hooks for github_pull_request_opened events and rotate its signing secret
Operations and Debugging
Inspect why an agent run failed by pulling structured logs of action executions and trigger deliveries. /api/v3/internal/action_execution/logs and /api/v3/internal/trigger/logs return the inputs, outputs, and errors for each call. Platform teams use these endpoints to build observability dashboards over agent activity.
Retrieve the last 50 action execution log entries and return the ones whose status is not 'success'
Agent-Driven Composio Operations via Jentic
Let an AI assistant manage Composio itself: provision projects, rotate API keys, and audit connected accounts. Through Jentic the agent searches by intent, loads the schema for the relevant Composio operation, and executes the call without the developer wiring auth or pagination. This is useful for platform teams running many agents on Composio.
On the prompt 'rotate the API key for project nano_77 and report the new key fingerprint', call the regenerate-api-key endpoint and return the rotated key prefix
Key Endpoints
86 endpoints — the composio platform api powers composio's tool-use platform for ai agents.
METHOD
PATH
DESCRIPTION
POST
/api/v3/connected_accounts/link
Generate a hosted link to connect a third-party account
GET
/api/v3/connected_accounts
List connected accounts
GET
/api/v3/connected_accounts/{nanoId}/status
Check the status of a connected account
POST
/api/v3/auth_configs
Create a reusable auth configuration for a toolkit
POST
/api/v3/webhook_subscriptions
Create a webhook subscription
POST
/api/v3/webhook_subscriptions/{id}/rotate_secret
Rotate the signing secret for a webhook
GET
/api/v3/internal/action_execution/logs
Inspect recent action execution logs
GET
/api/v3/internal/trigger/logs
Inspect recent trigger delivery logs
POST
/api/v3/connected_accounts/link
Generate a hosted link to connect a third-party account
GET
/api/v3/connected_accounts
List connected accounts
GET
/api/v3/connected_accounts/{nanoId}/status
Check the status of a connected account
POST
/api/v3/auth_configs
Create a reusable auth configuration for a toolkit
POST
/api/v3/webhook_subscriptions
Create a webhook subscription
POST
/api/v3/webhook_subscriptions/{id}/rotate_secret
Rotate the signing secret for a webhook
GET
/api/v3/internal/action_execution/logs
Inspect recent action execution logs
GET
/api/v3/internal/trigger/logs
Inspect recent trigger delivery logs
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Composio Platform API
- Foundational (C)56/100
48
Foundational Compliance63
Developer Experience & Jentic Compatibility40
AI-Readiness & Agent Experience88
Agent Usability50
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
48
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: D+Signals: 4
91%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
4%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
74%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
73%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
40
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
14%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
45%
Summary Coverage
Coverage of summaries across operations/tags/info.
88
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: ASignals: 1
88%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Composio Platform API by hand means learning its API key scheme, standing up connected accounts and auth configs, and wiring your own webhook subscriptions and execution logs. Through Jentic you install once, import the Composio Platform API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Composio puts the connected account and subscription ids in the URL path (/connected_accounts/{nanoId}/status, /webhook_subscriptions/{id}/rotate_secret), so a rule can pin your agent to a specific connected account or subscription. You choose the operations it may call, so you can allow reading account status and execution logs while leaving secret rotation out unless you add it.
Credential isolation
Your Composio API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'link a connected account' or 'check execution logs', and Jentic returns the matching Composio operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Composio Platform API through Jentic.
What authentication does the Composio Platform API use?
The API supports several API-key headers depending on context: x-api-key for project keys, x-org-api-key for organization-scoped calls, x-user-api-key for user-scoped calls, and a cookie-based authToken for the dashboard session. Through Jentic the appropriate key is stored encrypted in the vault and injected at execution time.
Can I link a user's third-party account with the Composio API?
Yes. Create an auth config via POST /api/v3/auth_configs for the toolkit you want, then call POST /api/v3/connected_accounts/link to generate a hosted link the user follows to grant consent. The resulting connected account is referenced by its nanoid in subsequent action calls.
How do I execute a toolkit action through the Composio API?
Resolve the action under the Tools resource, then submit its inputs against the user's connected account. Composio injects the connected-account credentials, validates inputs against the action schema, and returns a normalized response that the agent can pass back to the LLM.
What are the rate limits for the Composio Platform API?
Composio applies plan-tier rate limits with bursts handled per project key. The free tier is in the low hundreds of requests per minute and paid tiers scale up; agents should respect HTTP 429 responses, which Jentic surfaces as structured errors rather than retrying silently.
How do I subscribe to a SaaS event through Jentic?
Run the Jentic search query 'subscribe to a Composio trigger', load the returned operation (POST /api/v3/webhook_subscriptions), and execute it with the URL, event types, and secret. Rotate the secret periodically via POST /api/v3/webhook_subscriptions/{id}/rotate_secret.
Can I inspect why an action execution failed?
Yes. GET /api/v3/internal/action_execution/logs returns the recent execution log entries with inputs, outputs, and error details. GET /api/v3/internal/action_execution/log/{id} fetches a single entry for deep inspection.
Can I limit what my agent is allowed to do with the Composio Platform API?
Yes. Jentic One runs self-hosted, so your own rules decide which Composio operations and credentials the agent may use. Because Composio puts the connected-account nanoId and subscription id in the URL path, you can pin the agent to a specific connected account or webhook subscription. You choose the operations it may call, so you can allow reading connected-account status and action execution logs while leaving webhook secret rotation out unless you add it.
GET STARTED