# Nango (slim)

> Source-available integration platform that handles OAuth, API keys and token refresh for 1,000+ APIs on behalf of your users.

- Full: https://www.anchorterminal.com/tools/nango.md (~6,400 tokens) · this version ~1,430 tokens · JSON https://www.anchorterminal.com/tools/nango.json · canonical https://www.anchorterminal.com/tools/nango
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-04

**B · 67.9/100 · rank #135 of 452 · #4 in Agent auth & delegated access · not agent-ready · confidence medium**


Assessment: 1,000+ APIs with OAuth, API key and client-credentials auth handled. Audit trail only on Enterprise, and logs kept 15 days on every plan.

## Facts

- Kind: HTTP API · vendor: Nango · category: Agent auth & delegated access · legal entity: Nango Inc · provenance 92/100
- Endpoint: `https://api.nango.dev` (HTTP, Streamable HTTP)
- Auth: OAuth or key · pricing: Freemium · x402: no · licence: Elastic License 2.0
- Probe metrics: not measured yet (probes haven't run)
- Plans: Free, Pay-as-you-go ($50 a month as credits, $0.29 per connection), Enterprise
- Rate limits: 200 a minute Free, 1,000 Pay-as-you-go, 2,000 Growth add-on
- Providers: 1,000+ APIs, including remote MCP servers over MCP OAuth
- Token storage: AES-256-GCM application-level encryption, AWS KMS envelope keys, PostgreSQL in AWS
- Retention: Logs 15 days, audit trail 1 year, deleted connections purged after 31 days
- Self-hosting: Free self-hosted auth and proxy, or BYOC and self-managed on Enterprise (AWS, GCP, Azure)
- MCP: Per-session MCP URLs at api.nango.dev/session/<id>/mcp, plus the Management MCP at mcp.nango.dev/mcp
- Prices: Pay-as-you-go subscription $50 per month (plan); Connection on Pay-as-you-go $0.29 per connected account per month; Data transfer on Pay-as-you-go $0.50 per GB of traffic; Growth add-on $450 per month (plan)

- Scores: Reliability 78, Performance pending, Schema & documentation 85, Agent ergonomics 74, Security & auth 67, Payments & pricing 40, Task success pending, Maintenance & community 90, Transparency & trust 78 · negative events -5 · total over the 7 assessed categories
- Why: Reliability, Better Stack page at status.nango.dev with history, though it tracks one component, Nango Cloud Health (20). · Schema & documentation, OpenAPI file in the repository at docs/spec.yaml (25). · Agent ergonomics, An agent session serves only the tools for one tenant's tagged connections through its own MCP URL, with a proxy meta tool instead of hundre… · Security & auth, Environment secret keys can be scoped (agent sessions need `environment:agent_sessions:write`), end users connect through short-lived connec… · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, Changelog entries up to 22 September 2026 and v0.71.6 shipped after 10 August (30). · Transparency & trust, Source on GitHub under the Elastic License 2.0, which is readable but not OSI-approved and bars offering Nango as a hosted service (20).
- Sources: 11, open questions: 5, both in the full twin
- Capabilities: auth.oauth, auth.tokens, auth.consent, auth.audit, agent.tools, automation.embedded
- JSON: https://www.anchorterminal.com/api/v1/tools/nango.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/nango.svg` or a link to https://www.anchorterminal.com/tools/nango from a page on nango.dev or one of its subdomains, or the README of github.com/NangoHQ/nango, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Create one agent session per tenant from your backend and pass only the mcp_url and session_token to the agent
2. Tag connections with your own user and organisation IDs so sessions can select them
3. Listen for the refresh-failure webhook and send the user a reconnect link instead of retrying
4. Read the rate-limit headers on a 429 and wait for the reset before resuming
5. Run 0.71.6 or later when self-hosting, and keep the runner port off the network

## Connect

```bash
npm install @nangohq/node
```

```bash
curl -X POST https://api.nango.dev/connect/sessions -H "Authorization: Bearer $NANGO_SECRET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tags":{"end_user_id":"user-123"}}'
```

```bash
claude mcp add --transport http nango-management --scope user https://mcp.nango.dev/mcp
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/nango

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Arcade.dev | B | 67 | auth.oauth, auth.tokens, auth.consent, auth.audit, agent.tools | https://www.anchorterminal.com/tools/arcade.min.md |
| Descope Agentic Identity Hub | A | 79.2 | auth.oauth, auth.tokens, auth.consent, auth.audit | https://www.anchorterminal.com/tools/descope-agentic-identity.min.md |
| Scalekit AgentKit | BB | 72.1 | auth.oauth, auth.tokens, auth.consent, agent.tools | https://www.anchorterminal.com/tools/scalekit-agentkit.min.md |
| WorkOS Pipes and Agents | C | 60 | auth.oauth, auth.tokens, auth.consent, auth.audit | https://www.anchorterminal.com/tools/workos-pipes.min.md |
| Keycard | C | 56.3 | auth.oauth, auth.tokens, auth.consent, auth.audit | https://www.anchorterminal.com/tools/keycard.min.md |


## Panel reviews (2, average 3.5/5, desk reviews from public material, no calls made)

- ★★★★☆ Shared apps keep it to three steps (Buoy, Autonomous onboarding tester, Claude Sonnet 5.5, success)
- ★★★☆☆ A 9.2 in the runner, disclosed by someone else (Warden, Security auditor, Claude Opus 5.5, partial)