Treg gives an agent one key for 3,800+ API endpoints and routes every lookup to the cheapest provider first. pipe0 gives it fewer blocks, built for GTM, with waterfalls ordered by measured accuracy. On the same 150 LinkedIn profiles, pipe0 found 94% of mobile numbers. The four Treg phone providers we benchmarked found 72%.
| pipe0 | Treg | |
|---|---|---|
| AI agents over MCP | Yes. | Yes.plus a CLI and plain HTTP |
| Public API | Yes.pipes, searches, and actions | Yes. |
| Spreadsheet tables | Yes.Sheets, up to 2M rows | No. |
| Schedules and signals | Yes.cron runs, signals, emailed reports | No.every call is one-off |
| Inbound webhooks | Yes.webhook and email inbox streams | No. |
| Open source | No. | Yes. |
| pipe0 | Treg | |
|---|---|---|
| Catalog | GTM only: 50+ providers, 100+ enrichments and searches | 3,800+ endpoints: SEO, ads, social, enrichment |
| Waterfall order | Benchmarked for accuracy, reorderable | Cheapest first, falls through on a miss |
| Mobile coverage, our benchmark | 94% (141 of 150) | 72% across 4 of its 16 phone providers |
| Amplemarket data | Yes.only meta provider allowed to offer it | No. |
| pipe0 | Treg | |
|---|---|---|
| Pricing model | Credits from $49/mo, bills on success only | Pay per call at provider list price, no markup |
| Cost per mobile found, our benchmark | About 12¢ | About 14¢ (simulated routing) |
| Free tier | Yes.20 credits, no card | Yes.$1.00 of credit, no card |
Verified October 2026 against treg.to and its public pricing. Coverage figures come from pipe0's provider benchmark (150 profiles, August 2026); see the FAQ for the method.
A waterfall stops at the first answer, so a cheap provider that guesses wrong hides the right answer further down. In our work email benchmark, one of the cheapest sources we tested disagreed with Amplemarket and Crustdata on 33 of 46 shared answers; Prospeo disagreed on 5 of 50. pipe0 puts providers like Prospeo first because they are cheap and agree with premium data, not because they are cheapest.
Cheap phone providers mostly find the same people. In our benchmark, Amplemarket or Crustdata also found 61 of the 62 numbers that LeadMagic, Prospeo, and Aviato found, plus 80 numbers those three missed. Neither premium source is in Treg's phone catalog. pipe0 is the only meta provider allowed to offer Amplemarket data, which is most of the gap between 94% and 72%.
With Treg, the story ends when the data reaches your agent. In pipe0 the agent can say "write this to a pipe0 sheet" and the same records become a table that holds up to 2M rows, runs on a schedule, and listens to webhooks. Nothing gets rebuilt.
Treg is built for breadth, and it is honest about prices in a market that usually isn't.
Pick Treg if
Your agent needs Semrush, ad libraries, and social scrapers next to contact data, and every job is a one-off call you pay for by the request.
Pick pipe0 if
GTM data is the job, coverage and accuracy matter more than the cheapest call, and some lists need to keep running after the conversation ends.
Yes, for GTM data. Both give AI agents people and company enrichment over MCP and an API. Treg covers far more categories, such as SEO and ads. pipe0 covers GTM only, with curated waterfalls, premium sources such as Amplemarket, and sheets, schedules, and webhooks when the data needs a home.
We ran 150 LinkedIn profiles through each provider in August 2026. Four of Treg's 16 phone providers are in that benchmark: Aviato, LeadMagic, Wiza, and Prospeo. We simulated Treg's cheapest-first routing over them at Treg's list prices, which found 72%. pipe0's waterfall found 94%. The other 12 Treg phone providers were not tested, and the profile list was pre-filtered for resolvable people, so absolute rates run high.
Per call, often yes. Per number found, they come out close: about 14 cents with Treg's cheapest-first routing over the benchmarked providers, about 12 cents with pipe0's waterfall. The bigger difference is how many numbers you get back.
No. Treg is stateless: each call returns data to your agent and the work ends there. It can replay a paid response, but it has no tables, schedules, or inbound webhooks.
Keep reading: Stateless or stateful: GTM data for agentspipe0 vs Deeplinepipe0 vs Landbase