# Get each person to authorise their own account

> Get each person to authorise their own account: 0 companies fully do it, 7 with a limit, 25 carry the tag. Every listing in Agent tool access with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/aggregator.connect-end-user/
- Markdown: https://www.anchorterminal.com/niches/aggregator.connect-end-user/index.md (~1,250 tokens)
- Slim: https://www.anchorterminal.com/niches/aggregator.connect-end-user/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/aggregator.connect-end-user/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 | 7 | 25 | 22 | 8 |

## What counts as done

A hosted connect link the agent can hand over, a call that waits for or reports completion, a connection that is only marked active after a working test call, and no credential text in the model's context.

How agents ask for it: connect my Gmail; link the customer's HubSpot; sign me in to Outlook for the agent

## 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.

- **AgentWeb (Agent Web Labs, Inc.)**: agentweb_start_connection returns a URL for the person and agentweb_poll_connection waits for a final state, so no credential passes through chat. The docs don't say a connection is tested before it is marked active.
- **Composio (API + MCP) (Sampark Inc (d/b/a Composio))**: session.authorize or COMPOSIO_MANAGE_CONNECTIONS returns a Connect Link and the status reads active once done. acc-18 (open) shows invalid API keys created as ACTIVE, and acc-01 shows a consent flow asking for birth date and address that the user abandoned.
- **Merge Agent Handler (Merge API, Inc.)**: Magic Link is a signed URL the agent can hand over, with a callback or a done page, and credentials are stored per user. There is no documented wait or status call, and no test call before the connection counts.
- **One (One Systems, Inc.)**: One Connect lets a product's users connect their own apps on One's consent page, with reconnect_required after a revoke. The pages read show no status call an agent can wait on, and nothing says a connection is tested before use.
- **StackOne (StackOne Technologies Limited)**: An Auth Link or connect session token gives the end user a hosted link with expiry, and account.created fires by webhook when they connect. The agent waits on a webhook, not a call, and validation before active isn't stated.
- **Unified.to MCP Server (Unified API Inc.)**: The authorization URL takes success_redirect, failure_redirect, scopes and external_xref, and the end user picks an integration on Unified's page. Completion arrives by redirect to your app, not a call an agent can wait on.
- **Zapier MCP (agent actions) (Zapier Inc.)**: manage_zapier_connections returns a URL to add an app connection and Zapier holds the credentials, but connections belong to one Zapier account, and acc-15 shows the OAuth token exchange returning an HTML 500 while the client looked connected.

- 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): No connect link or end-user accounts; letme needs no key and stores no credentials.
- not this job: MCP Gateway (No legal entity found. COMMERCIAL.md, CLA.md and AUTHORSHIP.md name Mikko Parkkola, Finland, as licensor and author): No hosted connect link for end users; backend OAuth and identity propagation are configured by the operator in gateway.yaml.
- not this job: Monid (Monid, Inc.): No end-user connections; every run uses the provider's account behind Monid.
- not this job: Smithery (Clavia, Inc. (doing business as Smithery)): Managed identity, the connect layer, shut down on 31 October 2026. acc-28 had already shown strict OAuth servers rejecting its client with invalid_client.

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

## What stops agents finishing

- consent screen asks for personal data and the person abandons it
- OAuth server rejects the aggregator's client
- token exchange outage
- a human must click the link

## Around it

Before: chat.user-request. After: aggregator.run-app-action.

## Where this comes from

Weight 22 of 100 in Agent tool access: 8 of 32 accounts, tied highest; auth failures and abandoned consent flows recur across Zapier, Composio and Smithery

As data: https://www.anchorterminal.com/api/v1/use-cases/aggregator.connect-end-user.json, or the MCP tool get_use_case with id aggregator.connect-end-user. 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
