Entities And Multi Tenancy
Composio · Composio
Agent Tooling & Integrations — Composio
Evaluates Composio's Entities & Multi-tenancy across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Agent Tooling & Integrations eval coverage.
About Composio
Composio is a tool-integration layer for AI agents — 250+ managed tool integrations (Gmail, GitHub, Slack, and more) with built-in OAuth/auth, per-end-user entities for multi-tenant isolation, triggers and webhooks, framework adapters (OpenAI, Anthropic, LangChain, LlamaIndex, CrewAI), custom tools and schema processors, and an MCP server that exposes tools to MCP clients.
Sample tests· showing 3 of 9
| # | Input | Expected behavior | Check |
|---|---|---|---|
| 01 | A SaaS app has thousands of end users. The team wires the agent so every user's actions run under one shared entity. | Map each end user to a distinct, stable entity_id (e.g. the app's user id) so connections and executions are isolated per user. A single shared entity collapses every user's connections into one identity and breaks isolation. | Pass / FailAi Platformcritical |
| 02 | An execute call is issued without specifying entity_id. Composio applies a default entity. | Treat omission of entity_id as a bug in any multi-tenant flow: it falls back to a default/shared entity. Require entity_id explicitly on every per-user execute, and reserve the default entity only for single-tenant/admin tooling. | Pass / FailAi Platformhigh |
| 03 | User A and User B both connected Gmail. User A's agent run must only ever act through User A's mailbox. | Always pass User A's entity_id (and that entity's connected-account id) on execute so Composio routes to A's Gmail. Never resolve a connected account without scoping by the acting entity — that risks acting through B's mailbox. | Pass / FailAi Platformcritical |
How this eval is graded
Grade against expected.ideal_behavior and expected.rubric. Per-criterion pass requires mean >= 4.0 and no criterion below 3.
Rubric criteria
- Composio
- Ai Platform
- Entities And Multi Tenancy
Recommended for
Works with
Related evals
Claude API
Evaluates Anthropic's Batch API across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
View AI PlatformClaude API
Evaluates Anthropic's Extended Thinking across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
View AI PlatformClaude API
Evaluates Anthropic's Files API & Citations across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Foundation Model & API eval coverage.
ViewFrequently asked questions
What does the Entities And Multi Tenancy eval for Composio Composio test?+
Evaluates Composio's Entities & Multi-tenancy across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Agent Tooling & Integrations eval coverage.
How is the Entities And Multi Tenancy eval scored?+
The judge rubric: Grade against expected.ideal_behavior and expected.rubric. Per-criterion pass requires mean >= 4.0 and no criterion below 3.
How many test cases does this eval pack include?+
The Entities And Multi Tenancy pack for Composio Composio contains 9 test cases. 3 sample cases are shown free on this page; the full set runs in a Corsac workspace.
How do I run this eval?+
Sign up for Corsac, connect your model or agent endpoint, and run the Entities And Multi Tenancy pack as-is or after customizing thresholds. Results land in your workspace with per-case scores, and you can gate releases on the pack in CI via the REST API.
Run this eval in your workspace
Connect your data, configure thresholds, and review results with your team.