# Act for many end users without crossing accounts

> Act for many end users without crossing accounts: 0 companies fully do it, 6 with a limit, 28 carry the tag. Every listing in Agent tool access with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/aggregator.isolate-users/
- Markdown: https://www.anchorterminal.com/niches/aggregator.isolate-users/index.md (~1,200 tokens)
- Slim: https://www.anchorterminal.com/niches/aggregator.isolate-users/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/aggregator.isolate-users/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 6 | 28 | 11 | 4 |

## What counts as done

Every call runs on the connected account of the user in that session, and the log shows which user each call ran for; deleting a user removes their upstream tokens.

Measured, for our own tests: calls stay on the right user's account under concurrent load.

How agents ask for it: run this for each customer; use this user's CRM, not mine

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Composio (API + MCP) (Sampark Inc (d/b/a Composio))**: Each session is bound to one userId. acc-17 shows calls running as the last user to fetch tools (closed 28 October), acc-29 shows large ids colliding, and acc-30 shows upstream tokens kept after a user was deleted.
- **MCP Gateway (No legal entity found. COMMERCIAL.md, CLA.md and AUTHORSHIP.md name Mikko Parkkola, Finland, as licensor and author)**: End-user identity propagation (signed assertion, token passthrough or RFC 8693 exchange) fails closed, and per-user OAuth refuses calls without an identity. No per-user call log or token revocation on user deletion is documented.
- **Merge Agent Handler (Merge API, Inc.)**: A Registered User scopes every credential, tool call and audit record, and logs name the user. Deleting a user keeps credentials until the retention window ends and states no upstream token revocation.
- **One (One Systems, Inc.)**: Each Connect user has their own grant, the Users tab shows reach and last use, and Activity lists calls. Revoking removes access in One, but upstream token revocation on deletion isn't stated.
- **StackOne (StackOne Technologies Limited)**: Each request targets one linked account, projects isolate further, and account.deleted is an event. acc-26 showed concurrent SDK calls using the wrong account header (closed 27 April 2026), and upstream revocation on delete isn't stated.
- **Unified.to MCP Server (Unified API Inc.)**: Each MCP URL is bound to one connection, linked to an end user by external_xref, so calls can't cross accounts. A per-user call log with arguments and upstream revocation on delete weren't found in the pages read.

- not this job: AgentWeb (Agent Web Labs, Inc.): An aw_ key acts for one AgentWeb account and workspace; there is no end-user id per call for serving many customers from one process.
- not this job: letme (Long Lunch Labs Limited (company number 17523112, registered in England and Wales, incorporated 15 October 2026), trading as Anchor Terminal and letme): letme has no end users or connections to keep apart; answers are the same for every caller.
- not this job: Monid (Monid, Inc.): One workspace balance and API keys; there are no end-user identities or per-user connections.
- not this job: Smithery (Clavia, Inc. (doing business as Smithery)): No hosted connections remain after the 31 October shutdown.
- not this job: Zapier MCP (agent actions) (Zapier Inc.): A server and its token belong to one Zapier user, and the docs say to give each user their own server and token; there is no per-call end-user parameter for one process serving many.

1 listings in the category were added after this reading and aren't marked yet.

## What stops agents finishing

- SDK caches executors or headers across users
- user ids rounded or reused

## Around it

Before: aggregator.connect-end-user. After: agent-observability.trace.

## Where this comes from

Weight 11 of 100 in Agent tool access: 4 of 32 accounts (two SDK bugs that crossed users, one id collision, one stale-token case)

As data: https://www.anchorterminal.com/api/v1/use-cases/aggregator.isolate-users.json, or the MCP tool get_use_case with id aggregator.isolate-users. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
