treg vs Pipedream Connect, now part of Workday

treg vs Pipedream Connect: the short answer

Both reach an agent through remote MCP servers and keep credentials out of the model. treg is like OpenRouter for tools: one API key and one balance for many paid APIs. treg gives your agent paid data from 4,100+ tools across 126 providers with no vendor accounts, billed per call at 0% markup, and your own keys always win. Pipedream Connect, now part of Workday, gives the agents you build 10,000+ tools across 3,000+ APIs, acting in each end user's own accounts with managed OAuth. A product can use both: Pipedream for its users' apps, treg for the data.

Recent change. Pipedream Workflows and String shut down on 31 March 2027. Pipedream's docs say that Connect, its API, its MCP servers and its API proxy are not affected.

Which one fits

Different tools fit different jobs. Here is when each one is the better choice.

Choose Pipedream Connect if

You build a product whose users connect their own apps to your agent.
You want a raw API proxy with managed credentials for any endpoint of a connected app.
You need triggers that react to events in your users' apps.
You need HIPAA, SSO, SCIM or static egress IPs.

Choose treg if

Your agent needs keyword volume, backlinks, work emails, social profiles or ad libraries, with no account at each vendor.
You want each call billed in dollars at the provider's own rate, with no per-user fee and no plan.
You want Google Analytics, Search Console, Google Ads, Meta Ads, LinkedIn and Slack on the same token, never metered.
You want your team's own keys and tools behind one token.
You want code on GitHub you can self-host for your team.

treg vs Pipedream Connect, side by side

Each Pipedream Connect cell restates Pipedream's own public pages on 3 November 2026. "Not published" means those pages say nothing about it, not that the feature does not exist.

Feature	treg	Pipedream Connect
Billing
How you pay	A prepaid team balance. Each catalog call is billed at the provider's own rate. No subscription and no seats.	Free for development. Startup $99 a month (annual) with 100 external users and 10,000 credits, then $2 per user and $0.012 per credit. One credit is 30 seconds of compute.
Free start	$1.00 of credit, once per new verified account. No card.	Free for development and personal MCP use, no card. Production needs a paid plan.
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.	MCP tool calls use credits; there is no separate MCP fee.
What your agent can use
Size, in their words	4,100+ tools across 126 providers, plus the tools your team registers.	10,000+ tools and triggers across 3,000+ APIs.
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. Tools act in 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 managed OAuth or your own OAuth client.
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, plus deployed triggers.
What a call returns	The provider's own answer, unchanged. Routed tools add a small wrapper and say so.	Prebuilt tool results, or the raw API through the Connect 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.	Remote MCP servers at mcp.pipedream.com, one per app or one endpoint for all.
API, CLI and SDKs	An HTTP API (method, path, query and body reach the provider unchanged), a CLI and an agent skill. No SDKs.	The Connect API and API proxy, plus TypeScript and browser SDKs.
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.
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.	Component code is source-available, with no commercial use. Conduit (early access) can be self-hosted.
Control
Price before the call	Yes. Each tool's rate, with its source and the date it was checked.	Not published
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.	Not published
Call records	An audit log of calls with their cost, and every charge in the balance ledger.	An audit log of tool calls in Conduit.
Team	Teams with owner, admin, member and viewer roles, and tool access per member.	Unlimited team members; SOC 2 Type 2; SSO and SCIM on Business.

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 price

we earn on volume pricing with vendors - not on you

The trade-off

What each one does better

Where Pipedream Connect does best

01
Breadth of actions. 10,000+ prebuilt tools and triggers across 3,000+ APIs.
02
Built for your users. Per-user accounts, Connect Link, your own OAuth clients and 1M+ connected accounts.
03
A raw API proxy. Any endpoint of a connected app, with credentials managed for you.
04
Enterprise path. HIPAA on Business, SSO, SCIM, static IPs, and Conduit for governed access across a company.

Where treg is the better choice

01
Paid data with no accounts. 4,100+ tools across 126 providers: SEO and SERP data, enrichment, social, ad libraries and generation, on treg's own accounts.
02
Billed per call in dollars. 0% markup, a commitment in the terms. No per-user fee, no compute credits and no top-up fee.
03
Your own keys win. Register a key and treg uses it instead of its own, never metered.
04
Spend controls. A team daily spend cap, a per-call cost ceiling and per-member daily call caps, with each tool's price shown before the call.
05
Open code. treg's code is on GitHub under Apache 2.0 with added terms, and you can run it for your team.

Not either-or

Using Pipedream Connect and treg together

A product can use Pipedream Connect for actions in its users' apps and treg for the data its agent needs from vendors nobody has an account with.

Give your agent
every tool in the catalog.

$ set up treg — https://treg.to/llms.txt

Get started

Frequently Asked Questions

Is there a Pipedream alternative for AI agents?

Yes, for paid data. treg is a Pipedream alternative when an agent needs SEO and SERP data, enrichment, social profiles or ad libraries from vendors you have no account with. Pipedream Connect gives the agents you build 10,000+ tools that act in each end user's own accounts.

How much does Pipedream Connect cost?

Pipedream Connect pricing is free for development; Startup costs $99 a month (annual) with 100 external users and 10,000 credits, then $2 per user and $0.012 per credit. One credit is 30 seconds of compute. treg bills each catalog call at the provider's own rate, with 0% markup and no per-user fee.

Did the Workday acquisition change Pipedream Connect?

No, according to Pipedream's docs. Pipedream says Pipedream Connect, its API, MCP servers and API proxy are not affected, while Pipedream Workflows and String shut down on 31 March 2027. treg's code is on GitHub under Apache 2.0 with added terms, and you can self-host treg for your own team.

Pipedream vs treg: what is the difference?

Pipedream Connect runs tools in the accounts your product's users connect, while treg runs catalog calls on treg's own accounts for your agent. Pipedream adds triggers, a raw API proxy and per-user managed OAuth. treg adds a team daily spend cap, a per-call cost ceiling and each tool's price before the call.

Can I use Pipedream and treg together?

Yes. A product can use Pipedream Connect for actions in its users' apps and treg for the data its agent needs from vendors nobody has an account with. Both Pipedream and treg reach an agent over remote MCP.

Can I use my own API keys with treg?

Yes. treg accepts your own keys on every account, and your team's key always wins over treg's and is never metered. On Pipedream Connect, 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, beside an HTTP API, a CLI and an agent skill. Pipedream runs remote MCP servers at mcp.pipedream.com, one per app or one endpoint for all tools.

Sources and method

Pipedream home pagehttps://pipedream.com
Pipedream pricinghttps://pipedream.com/pricing
Pipedream Connecthttps://pipedream.com/docs/connect
Pipedream MCPhttps://pipedream.com/docs/connect/mcp
Workflows shutdown noticehttps://pipedream.com/docs/workflows
Workday announcementhttps://newsroom.workday.com/2025-11-19-Workday-Signs-Definitive-Agreement-to-Acquire-Pipedream

We read these pages on 3 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.

This page as markdown, for your agent or notesOpen markdown ↗