treg vs Nango: the short answer
Both reach an agent over MCP. treg is like OpenRouter for tools: one API key and one balance for many paid APIs. treg gives your agent paid data from many providers on treg's accounts, billed per call at 0% markup, and your own keys and connected accounts are never metered. Nango connects the product and agents you build to 1,000+ APIs in each user's own accounts, with managed OAuth, TypeScript functions, syncs and webhooks. A product can use both: Nango for its users' apps, treg for the data its agent needs.
Which one fits
Different tools fit different jobs. Here is when each one is the better choice.
Choose Nango if
- You build a product whose users connect their own apps, and your agent acts in them.
- You want integrations as code you can generate, review, test and deploy.
- You need syncs, webhooks and triggers, not only on-demand calls.
- You want a raw proxy to any endpoint of a connected API.
- You need SOC 2 Type II, HIPAA with a BAA, or Nango in your own cloud.
Choose treg if
- Your agent needs data you have no account for: SEO and SERP, people and company enrichment, social, ad libraries, or image, video and voice generation.
- You want each call billed in dollars at the provider's own rate, with 0% markup.
- You want a team daily spend cap, a per-call cost ceiling and per-member call caps.
- You want your own provider keys to win, and your Google Analytics, Search Console, Google Ads and Meta Ads calls never metered.
- You want to self-host for your own team, with the code on GitHub.
treg vs Nango, side by side
Each Nango cell restates Nango's own public pages on 5 November 2026. "Not published" means those pages say nothing about it, not that the feature does not exist.
| Feature | treg | Nango |
|---|---|---|
| Billing | ||
| How you pay | A prepaid team balance. Each catalog call is billed at the provider's own rate. No subscription and no seats. | Plans: Free $0, Pay-as-you-go $50 a month with $50 of credit, Enterprise custom. Usage is $0.29 per connection a month, $0.72 per compute hour and $0.50 per GB. |
| Free start | $1.00 of credit, once per new verified account. No card. | Free plan with hard caps each month: 10 connections, 10 compute hours and 10 GB. |
| Fees | 0% markup, a commitment in the terms. No top-up fee. Calls on your own keys, tools and connected accounts are never metered, except X through treg's own X app, which X bills per use. | Billed by connection, compute time (each run rounded up to 1 second) and data sent. No per-call fee. |
| What your agent can use | ||
| Size, in their words | 4,100+ tools across 126 providers, plus the tools your team registers. | 1,000+ APIs, with 10,000+ pre-built tools, triggers and syncs. |
| Paid data with no account at the vendor | Yes: SEO and SERP data, backlinks, people and company enrichment, social profiles and posts, ad libraries, web search and scraping, image, video and voice generation. | Not published. Calls run on the accounts your users connect. |
| Your own accounts | Google Analytics, Search Console, Google Ads, Business Profile, Tag Manager, Meta Ads, TikTok Ads, Microsoft Advertising, Pinterest Ads, Snapchat Ads, YouTube, LinkedIn, Slack, X, TikTok, Instagram and Facebook Pages. | Yes, the core of the product: each end user's own accounts, through Nango-managed OAuth apps or your own. |
| Actions (writes) | Writes in your connected accounts (ad changes, Slack messages, social posts) and any API or CLI your team registers. No triggers or scheduled workflows: the agent runs the steps. | Yes: action functions, plus syncs, webhooks and triggers. |
| What a call returns | The provider's own answer, unchanged. Routed tools add a small wrapper and say so. | Your action function's output (2 MB at most), or the provider's response through the proxy. |
| How your agent connects | ||
| MCP | A remote MCP server with OAuth or a token header, for Claude, ChatGPT, Claude Code, Codex, Cursor and others. | An MCP server per agent session, scoped to chosen connections and actions, plus a management MCP. |
| API, CLI and SDKs | An HTTP API (method, path, query and body reach the provider unchanged), a CLI and an agent skill. No SDKs. | A REST API with a proxy, backend SDKs for Node, Python, Java, Ruby, Go, Rust and PHP, and a CLI to build and deploy functions. |
| Bring your own keys | Yes, on every account. Your team's key always wins and is never metered. | Your users connect their own keys or OAuth accounts. You can use your own OAuth app instead of Nango's. |
| Open source and self-host | Code on GitHub under Apache 2.0 with added terms. You can self-host for your own team; offering it as a hosted service to others needs permission. | Code on GitHub under the Elastic License 2.0. Free self-host is limited to auth and proxy; full self-host and BYOC are on Enterprise. |
| Control | ||
| Price before the call | Yes. Each tool's rate, with its source and the date it was checked. | Rates are published. A call's cost depends on how long it runs. |
| Spend limits | A team daily spend cap, a per-call cost ceiling, per-member daily call caps and daily budgets per tagged customer (advisory). No per-key hourly or lifetime caps. | The Free plan is hard-capped. Spend alerts on paid plans. Dollar caps are not published. |
| Call records | An audit log of calls with their cost, and every charge in the balance ledger. | Built-in logs, metrics and alerts, kept 15 days, with OpenTelemetry export. |
| Team | Teams with owner, admin, member and viewer roles, and tool access per member. | RBAC, SAML SSO, SCIM and an audit trail; SOC 2 Type II; HIPAA with a BAA. |
treg's catalog size is read live from the catalog. Prices change; check each product's own pricing page before you decide.
0% additional fee.
provider rate + $0.000 markup = your priceThe trade-off
What each one does better
Where Nango does best
- 01
Breadth of app integrations. 1,000+ APIs and 10,000+ pre-built tools, triggers and syncs, in each user's own account.
- 02
Syncs and webhooks. Keep external data fresh with polling or real-time syncs, and react to provider webhooks.
- 03
Integrations as code. TypeScript functions you can generate with a coding agent, test locally and deploy through CI/CD.
- 04
A raw proxy. Authenticated requests to any endpoint of a connected API.
- 05
Compliance. SOC 2 Type II, HIPAA with a BAA, SSO and SCIM, and BYOC in your own AWS, GCP or Azure account.
Where treg is the better choice
- 01
Paid data, no vendor accounts. 4,100+ tools across 126 providers: SEO and SERP data, backlinks, people and company enrichment, social, ad libraries and generation models, all on treg's accounts.
- 02
Billed per call, 0% markup. Each call at the provider's own rate, with no connection fee, no compute time and no plan. 0% markup is a commitment in the terms.
- 03
Your keys and accounts, never metered. Your team's own key always wins over treg's. Calls on your connected Google Analytics, Search Console, Google Ads, Meta Ads, LinkedIn, Slack and YouTube accounts are never metered.
- 04
Dollar limits, prices first. A team daily spend cap, a per-call cost ceiling and per-member call caps, and each tool's rate with its source and checked date before the call.
- 05
Self-host for your team. treg's code is on GitHub under Apache 2.0 with added terms, and you can run it for your own team.
Not either-or
Using Nango and treg together
A product can use Nango for auth, syncs and actions in its users' apps, and treg for the data its agent needs from vendors nobody has an account with. Both reach an agent over MCP.
Give your agent
every tool in the catalog.
Frequently Asked Questions
Is there a Nango alternative for AI agents?
It depends on the job: treg is a Nango alternative when your agent needs paid data, and Nango fits when your product acts in each user's own apps. treg gives an agent SEO and SERP data, people and company enrichment, social, ad libraries and image, video and voice generation, with no vendor accounts.
How much does Nango cost?
Nango pricing has a hard-capped Free plan and a Pay-as-you-go plan at $50 a month with $50 of credit, while treg has no plan and bills each catalog call at the provider's own rate with 0% markup. Nango charges $0.29 per connection a month, $0.72 per compute hour and $0.50 per GB sent.
Is Nango open source, and can I self-host Nango for free?
Partly: free self-hosted Nango is for hobby projects and is limited to auth and proxy, while treg's code is on GitHub and you can self-host treg for your own team. Nango's code is under the Elastic License 2.0, and full self-hosting and BYOC are on the Nango Enterprise plan.
Nango vs treg: what is the difference?
Nango connects the product and agents you build to 1,000+ APIs in each user's own accounts, while treg gives your agent paid tools from many providers on treg's accounts. Nango adds managed OAuth, TypeScript functions, syncs and webhooks. treg adds a team daily spend cap, a per-call cost ceiling, per-member call caps and each tool's rate before the call.
Can I use Nango and treg together?
Yes. A product can use Nango for auth, syncs and actions in its users' apps, and treg for the data its agent needs from vendors nobody has an account with. Nango and treg both reach an agent over MCP.
Can I use my own API keys with treg?
Yes. treg accepts your own keys on every account, your team's key always wins over treg's, and calls on your connected Google Analytics, Search Console, Google Ads and Meta Ads accounts are never metered. On Nango, your users connect their own keys or OAuth accounts.
Does treg have an MCP server?
Yes. treg is a remote MCP server with OAuth or a token header, for Claude, ChatGPT, Claude Code, Codex, Cursor and others. Nango gives each agent session its own MCP URL and token, scoped to the connections and actions your backend names.
Sources and method
- Nango home pagehttps://www.nango.dev
- Nango pricinghttps://www.nango.dev/pricing
- Introductionhttps://nango.dev/docs/getting-started/intro-to-nango
- Auth guidehttps://nango.dev/docs/guides/auth/auth-guide
- Agent sessionshttps://nango.dev/docs/guides/agent-sessions
- Self-host Nangohttps://nango.dev/docs/guides/platform/self-hosting/self-hosting
- Limitshttps://nango.dev/docs/guides/platform/limits
- Nango on GitHubhttps://github.com/NangoHQ/nango
We read these pages on 5 November 2026. treg's own facts come from its pricing, terms and code. We left out what we could not check, and we do not guess why a product works the way it does.
Something wrong or out of date? Write to jason@treg.to and we will fix it.
Other comparisons
Paid data with no vendor accounts, at each provider's rate. Composio connects agents to apps in each user's accounts.
Read the comparison →tregvsZapier MCP
Dollars per call, not tasks, for data with no vendor accounts. Zapier MCP lets an agent act in the apps you connect.
Read the comparison →tregvsPipedream Connect
Billed in dollars per call, for data you hold no account for. Pipedream Connect lets agents act in your users' apps.
Read the comparison →tregvsAIsa
Each provider's own answer, with every field it returns. AIsa reshapes answers into one schema, sourced per value.
Read the comparison →tregvsLocus
Your team's own keys, accounts and tools, beside the catalog. Locus is built to resell paid tools to your customers.
Read the comparison →tregvsMonid
0% markup in the terms, and your own keys first. Like Monid, treg sells paid tools from a prepaid balance.
Read the comparison →