TrustMRR Startups Scraper - Revenue & Sale Data avatar

TrustMRR Startups Scraper - Revenue & Sale Data

Pricing

from $4.00 / 1,000 results

Go to Apify Store
TrustMRR Startups Scraper - Revenue & Sale Data

TrustMRR Startups Scraper - Revenue & Sale Data

Scrape public TrustMRR startup cards with name, category, revenue, sale price, valuation multiple, status and profile URL.

Pricing

from $4.00 / 1,000 results

Rating

0.0

(0)

Developer

Ben

Ben

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Share

Turn public source pages into structured, analysis-ready data with TrustMRR Startups Scraper - Revenue & Sale Data. The Actor is designed for SaaS research, founder benchmarking, startup acquisition monitoring, valuation comparisons, and market maps. It runs in Apify, writes one record per result to the default dataset, and supports JSON, CSV, Excel, XML, RSS, API access, schedules, webhooks, Make, Zapier, and n8n.

The current engine reads TrustMRR's server-rendered public startup cards. It does not require a user login or a private API key. Defaults are intentionally small so a first run is fast, inexpensive, and suitable for Apify's automated health checks.

What this Actor does

  • Collects current public records from the selected source
  • Accepts focused keywords or source search URLs
  • Returns normalized fields while retaining source wording
  • Removes duplicate records within a run
  • Caps results with maxResults for predictable cost
  • Raises an explicit error when the source unexpectedly returns no data
  • Supports recurring monitoring through Apify schedules

Data extracted

  • name - source-provided name value.
  • category - source-provided category value.
  • for_sale - source-provided for sale value.
  • revenue - source-provided revenue value.
  • revenue_text - source-provided revenue text value.
  • price - source-provided price value.
  • price_text - source-provided price text value.
  • multiple - source-provided multiple value.
  • multiple_text - source-provided multiple text value.
  • url - source-provided url value.

Every record also contains source context and a scrape timestamp where relevant. Missing values remain null rather than being guessed. This distinction matters for research: an undisclosed salary, price, fee, or location is not the same as zero.

Input

The input editor provides a tested default and prefill. Keep the first run at ten results, inspect the dataset, then increase the limit only for searches that produce useful records.

{"searchUrls":["https://trustmrr.com/"],"maxResults":10}

maxResults applies per keyword or input URL. The Actor enforces a hard upper bound to prevent accidental unbounded runs.

Example output

{"name":"Ritual75","category":"Health & Fitness","revenue":534,"price":7000,"multiple":1.1,"source":"TrustMRR Startups"}

The example shows the output shape from a live source probe. Public listings change continuously, so names, dates, amounts, and availability in future runs will differ.

Common workflows

Scheduled monitoring

Save the input as an Apify task and run it daily or weekly. Store the source ID or canonical URL as the durable key, compare the newest dataset with the previous one, and send only newly observed records to Slack, email, Telegram, a spreadsheet, or a data warehouse.

Market and competitor research

Normalize categories, companies, locations, and numeric fields outside the Actor while retaining the source text. This produces an auditable dataset for trend analysis without pretending that every source uses the same definitions.

Lead and account research

Use a public listing as a research signal, not as automatic permission for outreach. Enrich only records that fit a documented business purpose, keep the source URL beside the enrichment, and apply a human review before contact.

Dataset and API delivery

Download the default dataset in JSON, CSV, or Excel, or call the dataset API from your application. Apify integrations can forward completed-run data to Make, Zapier, n8n, Google Sheets, cloud storage, or a webhook.

Pricing

The Actor uses transparent pay-per-event pricing: a small $0.00005 start event and $0.004 per startup saved to the default dataset. This price is positioned against current public competitors while preserving room for maintenance. The input result limit gives direct control over spend.

Reliability and data quality

The engine retries temporary request failures, uses a browser-like user agent where needed, deduplicates source identifiers, and fails visibly when no records are found. A successful process with an empty dataset is not treated as healthy.

Source websites can change markup or embedded data. If a field suddenly becomes empty, open an Actor issue with the run ID and a public input. Do not include passwords, private cookies, account sessions, or confidential data. Small reproducible inputs make support faster.

For production use, monitor the run status, result count, and presence of key fields. Alert on a sharp row-count drop as well as a failed run. Keep historical snapshots when changes over time matter; do not overwrite previous values and then treat the latest state as historical fact.

Responsible use

Use the Actor only for lawful collection and processing of public data. Respect source terms, robots and rate expectations, copyright, database rights, and applicable privacy, employment, marketing, and consumer-protection rules. Do not use it to evade authentication, collect private records, harass people, or send indiscriminate messages.

Collect only fields needed for the stated workflow, define a retention period, protect exported datasets, and honor deletion or opt-out obligations that apply to your use case.

FAQ

Do I need an account on the source website?
No. The Actor uses the public data path documented above.

Can I run it on a schedule?
Yes. Save an input as a task and attach an Apify schedule.

How do I avoid duplicates?
Use the source ID when present and the canonical URL as a fallback key. The Actor also deduplicates within each run.

Why is a field null?
The source did not expose that field in the collected record. The Actor does not fabricate missing values.

Can I export to a spreadsheet?
Yes. Download CSV or Excel directly, or connect the dataset to Make, Zapier, n8n, or Google Sheets.

How should I report a problem?
Open the Actor's Issues tab with a run ID, public input, expected field, and observed result. Never attach private credentials.

Support and feedback

If this Actor saves time in your workflow, please leave a short Apify Store review. Reviews help other users evaluate the tool and help prioritize maintenance. For a source change, submit a reproducible issue instead of silently retrying a large run.

You might also like


Keywords: trustmrr scraper - startup revenue, price & mrr multiples, public data API, dataset export, monitoring automation, structured data, CSV export, JSON API, Apify Actor, scheduled scraper, market research.