Can an AI agent use Nango?
Nango connects apps to outside services and handles their logins.
Rank among the 246 products we drove
- Core work done
- tied #1
- 100%
- 10 of 10 core tasks
- Time to get in
- tied #42
- 4minutes
- Getting in on its own
- Steps on its own
- tied #35
- 3/ 5
- Find to Leave, no person
Yes. Our agent signed up for Nango on its own in a browser with an email and password, got an API key and used its API, MCP server and CLI.
The record
Level confirmed
Not yet
Level from one drive; a second must agree.
- Got in by
- Sign-up in a browser4 minutes
- Got as far as
- Pay: reaches the checkoutA card form for $50 a month
Connects by
API, CLI
Agent payments
None found
On its own · 132 doc pages read
Docs it can act on: llms.txt.
On its own · 4 minutes
Sign-up in a browser.
On its own · 10 of 10 core tasks
Did: create integrations and connect sessions through the API; fetch stored credentials for a connection.
Partly
Reaches the checkout. A card form for $50 a month.
Partly
Nothing to cancel. It deletes its data, but the login stays.
- On its own
- Partly
To reach L4: Delete its account, so its keys and login stop working.
See how it ranks in the MCP gateways category.
Own Nango? 7 things to fix. Get your findings, free
Checked 17 Nov 2026: llms.txt unchanged since the check before.
Find
How an agent connects
API, CLI and llms.txt found.
MCP server
27 of 28 testedA server for searching the docs only.
28 tools mapped in our drive
API
65 of 67 testedREST; agent sessions documented in a guide only.
67 operations mapped in our drive
OpenAPI
UnknownCLI
8 of 9 testednpm package nango 0.72.3, key in env vars, no login command.
9 commands mapped in our drive
SDK
45 of 51 testedNode @nangohq/node 0.72.3; other language SDK pages are placeholders.
51 methods mapped in our drive
llms.txt
YesAgent payments
None foundReached the card form and stopped: Pay-as-you-go, $50 a month. It checks out through a Stripe card form. No CAPTCHA at checkout.
Docs
In partCovers getting started, auth, error codes and code examples.
Describes each operation only in part: completeness 81 of 100.
15 of 17 documented ways to do the core work worked.
nango.dev/docs/getting-started/intro-to-nango
132 pages read
Changed since it was driven
Checked daily
- llms.txt: 3 links added and 2 removed
Get in
Getting in
Our agent tried 3 of 4 ways in; 1 worked without a person.
The way that worked
Sign-up in a browser4 minutes
- An inboxNeeded
- A browserNeeded
- A personNot needed
- Agent on a serverAPI, MCP, CLINoStops at sign-up: it works only in a browser.
- Assistant in its own browserLike ChatGPT agentPartlySigns up, confirms its email and does all of the core work, then stops: deletes its data, but the login stays.
- Signed agentNot checkedNot checked: the robots.txt on app.nango.dev asks crawlers to stay off the sign-up page.
Every way in
| Way in | What happened | Why |
|---|---|---|
| Sign-up in a browser | Worked | |
| Runs locally, no account | Stopped | |
| Sign-in for apps (OAuth) | Stopped | The consent page needs an account |
| Company single sign-on | Not tried | Not part of this drive |
- CrawlersThe robots.txt on app.nango.dev asks crawlers to stay off sign-up. Nothing to fix.
Use
What an agent can do with Nango
All 10 core tasks done, and 16 of 17 others.
Core tasks
- done there
- offered, not tried
| Task | Result | Through |
|---|---|---|
| Set up an integration with an external API | Done | API: done thereMCP: done there |
| Let an end user connect their account through a connect session | Done | API: done thereMCP: done there |
| Fetch a connection's refreshed credentials | Done | API: done thereMCP: offered, not tried |
| Run an action or tool on a connected account | Done | API: done thereMCP: done there |
| Create a scoped agent session with a toolset | Done | API: done there |
| Deploy a pre-built sync or tool template | Done | API: done thereMCP: done thereCLI: done there |
| Read synced records from an external API | Done | API: done there |
| Receive and forward external API webhooks through Nango | Done | API: done there |
| Make an authenticated request to an external API through the proxy | Done | API: done thereMCP: done there |
| Build a custom tool or sync function in code | Done | API: done thereCLI: offered, not tried |
Surface audit: 167 documented operations: 156 run, 9 blocked by sandbox or plan limits and 2 left out because they spend money or reach real people. Of the 156 run, 148 passed and 8 didn't; 6 behaved differently from the docs. By surface, 65 on the API, 45 in the SDK, 27 on the MCP server, 8 in the CLI and 11 elsewhere, such as sign-in and webhooks.
Holds up
94of 100
- Reliability100
- Handles mistakes89
The mean of the two, 94.5, with a half rounded to the even number.
Docs match
91of 100
- Docs accuracy96
- Docs completeness81
Docs accuracy counts 70%, completeness 30%.
Surface tested
90of 100
148 of 165 passed: the 167 documented operations less the 2 that spend money or reach real people
What it can't do, and why
- Get the first key without a browser Sign-up, email confirmation and the first key are only in the web app.
- Sign in to the management MCP with OAuth The sign-in server rejects a loopback address with a different port.
- Pay for a plan Only a card form in the dashboard; no billing API.
- Delete the account No self-serve deletion; requests go by email to the vendor.
- Use extra environments, roles, SSO or audit trail These need a paid or Enterprise plan.
16 of 17 other tasks done
- Trigger a sync runDone
- Pause or start syncsDone
- Check sync statusDone
- Change a connection's sync frequencyDone
- Prune synced recordsDone
- Set connection tags and metadataDone
- Import an existing connectionDone
- List connectionsDone
- Remove a connectionDone
- Update an integration's settingsDone
- Delete an integrationDone
- Browse the API provider catalogDone
- Register a webhook URL for Nango eventsDone
- Read integration logsDone
- Run a function in an isolated test dry runDone
- Rotate the webhook signing keyDone
- Read usage and set spend alertsPartly
- Create an environmentPaid plan
- Export traces with OpenTelemetryPaid plan
- Customize the Connect UI brandingPaid plan
- Set a team member's rolePaid plan
- Configure SAML SSOPaid plan
- Provision users with SCIMPaid plan
- Read the audit trailThese need a paid or Enterprise plan.Paid plan
The plans they need
- Read usage and set spend alertspaid
- signupenterprise
The drive used the free plan.
Tips for agent builders
- Use the Management MCP at https://mcp.nango.dev/mcp with 'Authorization: Bearer <environment key>' instead of OAuth.
- For deploy_template, deploy_function and integrations_delete, declare clientCapabilities.elicitation.form and resend with inputResponses {action: accept}.
- Use an Account API key to create narrowly scoped Environment keys via POST /environments/{uuid}/api-keys.
- Pass both 'goal' and 'intent' to nango_execute on agent-session MCP servers, and initialize them with protocol 2025-11-25.
- Always pass ?type=action|sync when deleting a function.
Pay
Paying
Ways to pay checked 7 Nov 2026.
- ResultPartly. Reaches the checkout. A card form for $50 a month.
- CheckoutReached the card form and stopped: Pay-as-you-go, $50 a month. It checks out through a Stripe card form. No CAPTCHA at checkout.
- TrialIt has a free plan.
Leave
Leaving
- ResultPartly. Nothing to cancel. It deletes its data, but the login stays.
- Its accountNot all of it: it deletes its data, but the login stays. The login, its empty team and the untouched prod environment stay: no self-serve account deletion anywhere, privacy policy routes it to hello@nango.dev (a person). All test data, dev env keys and the Account API key were deleted and now 401.
Daily checks
Checked every day
What our agent finds on the product's own site each day, without an account.
Sign-up page,
Stopped on the newest check; 10 of 10 days
llms.txt,
Found on the newest check; 10 of 10 days
MCP server,
Answers with an error on the newest check; 4 of 10 days
OpenAPI,
Not on its site on the newest check; 10 of 10 days
Compare
How Nango compares
In MCP gateways
None of the 3 products we drove in MCP gateways is higher; 2 others share L3. As of 7 Nov 2026.
| Product | Level | Find to leave |
|---|---|---|
| Arcade | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly. |
| Nango (this page) | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly. |
| Composio | L3 | Find: On its own, Get in: On its own, Use: On its own, Pay: Partly, Leave: Partly. |
For the team behind Nango
Agents get stuck at Pay
7 things to fix for agents: 4 small, 2 medium and 1 large
One fix can cover several findings.
Agent blockers: 5 foundAgent surfaces: 13 issues found
Get your findings, freeWhat a drive covers
We mail a private link to an address at nango.dev.
It opens the two findings that matter most in full, and every other by title. There is nothing to sign in to.
- FindClear
- Get inClear
- UseClear
- PayBlocks agents
- LeavePartly
Or claim Nango to see where each issue is and ask for a free drive after a fix.
Want Nango driven every month? See Watch
On our standard
Best or ahead on 6 of 32 criteria, behind on 7. Each against every product we measured on it.
- All validation problems at onceAhead of 47 of 57 others, 10 the same.
- llms.txt that worksAhead of 185 of 239 others, 54 the same.
- Docs an agent can navigateAhead of 128 of 187 others, 59 the same.
- Limits known before they hitAhead of 58 of 90 others, 32 the same.
- A request id on every answerBehind 102 of 143 others, 41 the same.
- Results sized for a context windowBehind 55 of 70 others, 15 the same.
- Agents may read docs, API and sign-upBehind 130 of 160 others, 30 the same.
- Typed, tight input schemasBehind 75 of 91 others, 16 the same.
All 32 criteria
- A way in with no personAhead of 137 of 243 others, 106 the same.
- Truthful annotationsAhead of 50 of 91 others, 41 the same.
- Prices an agent can readLevel with 117 of 153 others, 36 lower.
- Errors a program can readLevel with 82 of 145 others, 47 lower, 16 higher.
- No person in the buy pathLevel with 114 of 138 others, 24 lower.
- Fast to the first callLevel with 118 of 135 others, 17 lower.
- Descriptions that say when to use the toolLevel with 56 of 91 others, 22 lower, 13 higher.
- The best way in is built for agentsIn the middle 79 of 196 others lower, 55 the same, 62 higher.
- Tool names that sort themselvesLevel with 85 of 91 others, 6 lower.
- Terms allow an agent's accountLevel with 179 of 189 others, 10 lower.
- Real status codesLevel with 161 of 168 others, 7 lower.
- Errors say what to do nextLevel with 107 of 145 others, 22 lower, 16 higher.
- Every way in works for an agentIn the middle 61 of 193 others lower, 72 the same, 60 higher.
- A path written for agentsIn the middle 48 of 187 others lower, 91 the same, 48 higher.
- WebMCP tools on the web appLevel with 133 of 136 others, 3 higher.
- Structured resultsIn the middle 22 of 78 others lower, 32 the same, 24 higher.
- An agent payment rail on the coreLevel with 205 of 216 others, 11 higher.
- Agents pick the right toolLevel with 72 of 91 others, 19 higher.
- A tool list that fitsIn the middle 21 of 91 others lower, 26 the same, 44 higher.
- Spend an agent can see and capLevel with 105 of 159 others, 54 higher.
- Pages fit one fetchLevel with 118 of 187 others, 69 higher.
- Sign-in for agents acting for a personBehind 84 of 158 others, 74 the same.
- Delete by API, checkedBehind 52 of 97 others, 45 the same.
- Export before leavingBehind 117 of 189 others, 72 the same.
Where Nango fits
- Tasks
- Wall
- Sign-up or key only in a browserour agent got in another way
- Let AI agents sign up and get an API keyfix guide
- Standards
- llms.txtits docs, listed for agents
- Topics
- Docs and llms.txtFind step
- MCP and APIUse step
- Card checkoutPay step
- Delete the accountLeave step
History
Level by drive
One drive so far, on 7 Nov 2026.
Read more on this step
Pay is where our agent stopped at Nango.
- Finding · 18 Nov 2026How far does an AI agent get in a card checkout?Our agent reached the checkout at 88 of the 190 products it set out to buy from, and the card form at 68.Read
- Guide · 18 Nov 2026Let AI agents pay you per call: x402 and MPPx402 or MPP on a paid endpoint, your prices where agents read them, and plans an agent can buy by API or MCP.Read
- Guide · 28 Oct 2026Tell an AI agent a feature needs a paid planHow to answer an AI agent at a paid-plan wall: 402 or 403, a Problem Details body with the required plan, and an upgrade link a person can open.Read
Every earlier drive is in the history. The level follows these rules. Data under CC BY 4.0.
Found an error? Tell us on this page or read how corrections work.
Questions people ask about Nango
- Can an AI agent create a Nango account on its own?
- Yes, in a browser, without a person. Browser form at app.nango.dev/signup (name, email, password), no CAPTCHA; onboarding asked only how we heard of Nango. Google sign-up offered, not tried.
- Does Nango have an MCP server, and can an agent connect to it?
- Nango's docs have an MCP server for searching them. The drive found no MCP server that works the product itself. A new agent can get in on its own: in the drive of 7 Nov 2026, our agent signed up, verified and got its key without a person.
- How does an AI agent get a Nango API key?
- In the drive of 7 Nov 2026, our agent got its Nango API key in a browser, without a person. The first Environment key is shown in the dashboard and was read by the agent in its own browser. An Account API key, also created in the dashboard, then lets the agent create scoped Environment keys, use them (403 outside their scope) and revoke them (then 401) over the documented API with no browser.
- Can an AI agent delete its Nango account?
- Not all of it: it deletes its data, but the login stays. The login, its empty team and the untouched prod environment stay: no self-serve account deletion anywhere, privacy policy routes it to hello@nango.dev (a person). All test data, dev env keys and the Account API key were deleted and now 401.
- Can an AI agent pay for Nango?
- Partly. Our agent reached a card form for $50 a month. It has a free plan.
Cite this page
The page as a reference, in plain text, APA and BibTeX.
Cite this
AgentDrives, “Nango: AI agent test drive”, 7 November 2026, https://agentdrives.com/tools/nango. CC BY 4.0.
AgentDrives. (2026, November 7). Nango: AI agent test drive. https://agentdrives.com/tools/nango
@misc{agentdrives_nango_2026,
author = {{AgentDrives}},
title = {Nango: AI agent test drive},
year = {2026},
month = nov,
url = {https://agentdrives.com/tools/nango},
note = {Agent test drive, CC BY 4.0},
}Something wrong on this page?
We check it against the drive and correct the page, with the date.