Subscription figures are provider list prices recorded in treg.to’s own catalog grid; per-call prices are what treg.to charges today, with $0.000 added.
set up treg — https://treg.to/llms.txt
Using treg, find every posting for a data engineer in Berlin published in the last week, show me the price per 100 postings from each provider first, cap the run at 500 rows, then give me a table of company, title, date posted and link, deduped on the posting URL, and say how many rows came back.
The LinkedIn rows take a keyword and a location; the company rows take a company or a filter. Say which you have.
The Apify row bills per posting it returns and a broad search returns thousands. A maxItems cap is the difference between a cent and a dollar.
The date posted is the field nobody trusts and the link is the one that lets you check. Both belong on the table.
The same job is reposted, cross-posted and recycled. No row here dedupes for you; the agent has to.
treg.to holds the provider keys. Neither you nor the agent sees them.
The provider's own rate, $0.000 markup, from a prepaid balance.
Charged per call. $1.00 free per new team, no card to start.
Already pay Hunter? Register it and those calls are never metered.
Another provider is a different word in the prompt, not a new integration.
No SDK, no OAuth dance per vendor, no seats.
treg.to does not choose for you. It hands ChatGPT this comparison, with the price shown before any call, and ChatGPT picks. Or you tell it how: "cheapest", "most reliable", "the one that takes what I have", or a provider by name.
Apify at $0.001 · LinkedIn
PredictLeads at $0.04 · Company data
TikHub at $0.001 · LinkedIn
Those units are not interchangeable: one call can return many results, so compare on the unit you will actually be billed in.
| Provider | Success | Median | Sample |
|---|---|---|---|
| Crustdata | 100% | 798ms | 24 calls |
| 100% | 24.1s | 110 calls | |
| 87% | 2.0s | 768 calls |
Measured on treg.to traffic: real calls, real inputs, and sample sizes differ by provider. Live reliability, not a controlled benchmark.
| Provider | Price | Accepts | Success rate | Verified |
|---|---|---|---|---|
| Crustdata | $0.009 per result | filters, fields, sorts, limit, cursor, aggregations | 100% (24 calls) | 2026-08-25 |
| $0.025 per result | titles.include, companies.include, location.countries, seniority, hasRemote, postedWithin | 87% (768 calls) | 2026-07-28 | |
| $0.04 per call | active_only, not_closed, location, first_seen_at_from, first_seen_at_until, last_seen_at_from | not yet measured | 2026-08-20 |
| Provider | Price | Accepts | Success rate | Verified |
|---|---|---|---|---|
| $0.001 per result | maxItems, maxTotalChargeUsd, timeout, jobTitles, company, locations | 100% (110 calls) | 2026-08-20 | |
| $0.001 per found | location, keyword, country, job_type, experience_level, time_range | (38 calls) | unverified |
treg call apify.linkedin.search.jobs --query maxItems=1 --query maxTotalChargeUsd=0.05 --query timeout=180 --data '{"jobTitles":["attorney"],"locations":["Miami, Florida"],"maxItems":1}'Swap the id for any provider above. All 6 endpoints behind this job, with their parameters and captured responses, are on the Company data, LinkedIn shelf.
Of the ~210 Reddit and X posts read in August 2026 roughly half were on the job, the densest corpus behind any of these pages, and five vendor clusters were excluded, including one launch story reposted to three subreddits with the AI tool's name swapped each time. These five are people fighting the boards.
“Since when did Indeed start injecting invisible fake job cards as a scraper honeypot?” X, 189 likes
What this page can do about it: Which is why there is no Indeed row here and this page says so in its first paragraph. The LinkedIn rows exist because a provider absorbs that fight on its side; on Indeed nobody in the catalog does.
“I hate LinkedIn and Indeed. Filters don't work well, search experience is terrible, and the sites are contaminated with so many offshore agencies.” r/findapath, 745 points
What this page can do about it: Rows fix the filter half: once the postings are data, your agent filters them by whatever rule you like. The contamination half arrives with the data, and the agent is the filter for that too.
“Not being able to trust the date posted of any job. Being shown too many irrelevant jobs.” r/leetcode, 401 points
What this page can do about it: No row here fixes the date; it returns what the platform shows. What a daily pull gives you is your own first seen date, which is the only one you can trust, and that costs a tenth of a cent a posting.
“Half are gone by day 28, and almost all of that drop happens in a single week.” r/jobsearchhacks, 376 points
What this page can do about it: That poster tracked over a million postings a day to learn it, and the method is the point: a repeated pull is what turns postings into a signal. The rows here make the pull cheap; the tracking is the agent's job.
“Everyone in this community is bragging about AI-powered automations or seemingly simple workflows that call overpriced APIs to parse a page.” r/n8n, 307 points
What this page can do about it: Fair, and a tenth of a cent per posting is the answer to overpriced rather than to free. The self written scraper wins until LinkedIn changes something; the row wins the day after.
On LinkedIn, Apify's job search actor bills a tenth of a cent per posting returned with no platform charge on top, and TikHub's LinkedIn row bills a tenth of a cent per successful call, which on a big search is the cheaper of the two. On the companies shelf Crustdata bills under a cent per result, LeadMagic two and a half cents, and PredictLeads four cents a call for a company's openings and a credit per record for a filtered search. All of it is the provider's own rate with $0.000 added. The row labelled treg is the routed endpoint: the explicit opt in where you ask treg.to to choose among the company rows, your own keys first, and it names the provider that served and bills that provider's rate.
The Apify row is charged per dataset item it produces, so a search that matches four thousand postings costs four dollars unless maxItems says otherwise; set it on every call and read the run's usage afterwards. Per call rows have the opposite shape: one page costs the same whatever it holds, so page size is free and pagination is the cost.
The date posted is the platform's date, which the research says is the field people trust least. TikHub's LinkedIn job search has not been called live through treg.to yet and is marked unverified in the table; run one search before an agent runs a hundred.
It is a call that searches job postings and returns them as structured rows: title, company, location, date, description, link. The boards themselves mostly do not offer one to the public any more, which is why the searches for an Indeed API keep landing on scrapers. The rows here come in two shapes. The LinkedIn shelf searches LinkedIn's postings by keyword and location and returns the postings, priced per posting or per call. The companies shelf comes from the firmographic databases, which index job openings per company as a hiring signal, so the natural question there is which companies are hiring for what, rather than which jobs match a title.
No. Indeed closed its publisher API and the catalog carries no Indeed row, scraped or official. The LinkedIn rows are the closest thing on this page, and the company rows answer a different question: who is hiring, not which jobs match a title.
Yes, as many as the platform shows. No row here dedupes across reposts or checks that a posting is real, and this page will not claim otherwise. Dedupe on the posting URL in the agent, and treat the date posted as the platform's claim.
On the per posting row, the number of postings times a tenth of a cent, which is why the prompt caps the run. On the per call rows, the number of pages. Ask the agent to print the price for your cap on every row before it runs.
That is what the companies shelf is for. PredictLeads, Crustdata and LeadMagic index openings per company, so an agent can ask which of your two hundred target accounts opened an engineering role this month, without searching a board at all.