Composio

PASS consensus from 2 PASS, 1 PARTIAL.

The quickstart covers API keys, a session, in-chat Connect Link authentication, and execution; the optional manual-auth Markdown URL returned 404. The credentials-to-connection-to-invocation path is fully documented (COMPOSIO_API_KEY from dashboard settings, session creation, runtime Connect Link, then session.execute()), but Python session creation is written two contradictory ways: quickstart and how-composio-works use composio.sessions.create(user_id=...) while authentication, the Anthropic provider page, llms.txt, and the AI-generator note appended to every page use composio.create(user_id=...), and the Python SDK reference for the Composio class documents neither a sessions property nor a create method. The quickstart page, provider guides (OpenAI, Anthropic), and authentication docs together provide an unambiguous path: install the SDK, create a session with composio.sessions.create(), call session.tools() for meta tools, and execute via session.execute() or a provider handle_tool_calls helper.

PASS consensus from 2 PASS, 1 PARTIAL.

Starter and Hobby allow 2,000 requests per minute, Growth allows 10,000, and Enterprise is custom on both current and v3 pages. One table gives all four plans exactly , Starter 2,000 requests/1 minute, Hobby 2,000 requests/1 minute, Growth 10,000 requests/1 minute, Enterprise Custom with no window , and the legacy v3 page at /reference/v3/rate-limits.md carries a byte-identical table, so the fixed-window rule and the quotas do not disagree anywhere in the docs. Exact per-minute API rate limits are documented for Starter/Hobby/Growth/Enterprise, but the main marketing pricing page (composio.dev/pricing) uses entirely different plan names (Free/Pro/Enterprise) and the pro-tools page uses yet another naming scheme (Totally Free/Ridiculously Cheap/Serious Business) with a contradictory 'Free: 100/min standard tool calls' rate limit that does not square with the rate-limits page's 'Starter: 2,000/min'.

PASS consensus from 2 PASS, 1 PARTIAL.

Errors gives backoff, Rate Limits supplies Retry-After and plan quotas, and Proxy Execute separately identifies upstream 429 responses. Retry-After is defined precisely as "Seconds until the window resets (only on 429 responses)", X-RateLimit-Remaining and X-RateLimit-Window-Size are documented for pre-emptive throttling, the 429 body is shown verbatim, and /docs/extending-sessions/proxy-execute.md separately covers the upstream 429 case with "Composio doesn't retry automatically." The rate-limits and errors pages document the 429 response format, the Retry-After header, the X-RateLimit-* headers, and three specific recovery steps (monitor remaining, honor Retry-After, cache static data). The errors page additionally recommends exponential backoff.

PASS consensus from 2 PASS, 1 PARTIAL.

The linked creation and receiving pages cover the full path, while the trigger section root URL returned 404. The whole chain is covered end to end: inspect the trigger type's config schema, composio.triggers.create() with the slug and trigger_config, composio.triggers.set_webhook_subscription() to register the project webhook URL and capture the secret, the V3 envelope shown as literal JSON, and both an SDK parse(verify_secret=...) path and a from-scratch HMAC implementation with a stated 300-second replay tolerance. The triggers documentation covers the complete path: creating a trigger (composio.triggers.create()), registering a project webhook (composio.triggers.set_webhook_subscription()), receiving events, and verifying signatures via parse()/verifyWebhook() with HMAC-SHA256, all with Python SDK code examples for FastAPI and Flask.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The Python SDK reference executes composio.tools.execute() without the required version or opt-in flag, while the agent quickstart uses current sessions. The package name, the Python 3.10-or-newer floor, a class-by-class reference with source links, and a complete runnable Anthropic tool-calling example are all present, but the Installation section of that reference page is an empty heading in the markdown mirror and its Quick Start demonstrates composio.tools.get() / composio.tools.execute() direct execution, which the same site's AI-generator note describes as the lower-level alternative to the recommended composio.create(user_id) session entry point. The Python SDK reference documents installation (uv add composio or pip install composio, Python 3.10+), initialization with an API key, tool discovery (composio.tools.get()), tool execution (composio.tools.execute()), and the session API (composio.sessions.create()), all consistent with the session-based concepts described in how-composio-works.