TrustMRR Scraper

Acquisition marketplaces publish asking prices, and almost none publish revenue you can check. TrustMRR verifies revenue against the seller's payment processor, which makes its listings the rare case where a multiple means something. This Actor returns one structured record per listing: asking price, verified revenue, MRR, profit margin, the implied revenue multiple, 30 day growth and how many offers it has drawn.

What it does

• Returns the whole marketplace on the listings route, or a fuller detail record per listing on the startup route, which carries MRR, total revenue, active subscriptions and more.
• Carries verified revenue, not a seller's claim, because TrustMRR checks it against the payment processor.
• Computes the revenue multiple the asking price implies, so listings are comparable without a spreadsheet.
• Reports 30 day revenue growth, which is what separates a business that is compounding from one that is being sold on its peak.
• Carries the offer count, so demand for a listing is visible next to its price.
• Reports the profit margin, so revenue quality is visible rather than just revenue size.

Use cases

You need to	How this Actor does it
Screen the market for value	Sort on revenueMultiple and filter on profitMarginPercent
Find businesses that are growing	Filter on revenueGrowth30dPercent above your threshold
Gauge demand for a listing	Read offerCount next to value
Track a category	Filter on category and schedule the run daily
Watch a specific listing	Use the startup route with its slug for the fuller figures
Feed a deal-sourcing agent	Call the Actor over MCP and let the model screen the market

Quick start

1. Click Try for free.
2. Leave Route on listings to read every business currently for sale.
3. For the fuller figures on specific listings, switch Route to startup and add slugs or listing URLs, one per line.
4. Click Start. Rows appear within seconds.
5. Export as JSON, CSV, Excel or XML, or read the dataset over the API.

Input

Field	Type	Default	What it controls
route	string	listings	listings returns the whole marketplace, startup returns a detail record per slug
slugs	array	empty	Slugs or listing URLs. Only used on the startup route
maxItems	integer	0	Caps how many records are written. 0 writes them all

{
    "route": "listings",
    "maxItems": 0
}

Output

One dataset item per listing. Fields TrustMRR does not publish for a listing are dropped rather than returned as null, so a listing with no verified revenue carries no revenue fields.

Field group	Fields
Listing	status, name, category, url
Price	value, currency, revenueMultiple
Revenue	revenueLast30Days, monthlyRecurringRevenue, revenueGrowth30dPercent
Quality	profitMarginPercent, activeSubscriptions
Demand	offerCount
Timing	validFrom, scrapedAt

{
    "status": "ok",
    "name": "Invoice automation for freelancers",
    "category": "SaaS",
    "value": 84000,
    "currency": "USD",
    "revenueMultiple": 3.1,
    "revenueLast30Days": 2260,
    "monthlyRecurringRevenue": 2180,
    "revenueGrowth30dPercent": 8.4,
    "profitMarginPercent": 71.2,
    "offerCount": 4,
    "validFrom": "2026-09-06T05:30:00.000Z",
    "url": "https://trustmrr.com/startup/invoice-automation-for-freelancers"
}

Integrations

Run it over the API and get the rows back in one call:

curl -X POST "https://api.apify.com/v2/acts/publicmoney~trustmrr-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"route": "listings", "maxItems": 0}'

From Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("publicmoney/trustmrr-scraper").call(run_input={"route": "listings", "maxItems": 0})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["name"], item["value"], item["validFrom"])

Give an AI agent the Actor over MCP:

{
    "mcpServers": {
        "apify": {
            "url": "https://mcp.apify.com/?actors=publicmoney/trustmrr-scraper"
        }
    }
}

Schedules run it on any cron, webhooks fire when a run finishes, and platform integrations push the dataset to Google Sheets, Slack, Airtable, Zapier or your own endpoint.

Cost

Pay per event, so you pay for records rather than compute time.

Event	Free tier	Top volume tier
Record with data	$0.002	$0.0007
Actor start	$0.00005 per GB	Same

A record that returned no data is published as a failure row and is never charged. Six volume tiers apply, so the per-record price falls with monthly volume.

Troubleshooting

Issue	Solution
The startup route returns failed	The slug is wrong. Copy it from the end of the listing URL, or paste the whole URL, which the Actor accepts.
A listing has no revenue fields	TrustMRR has not verified revenue for it. Treat the asking price as unbacked, which is the useful signal.
revenueMultiple is missing	It cannot be computed without verified revenue. An unverified listing carries the price only.
Fewer listings than the site shows	Sold and withdrawn listings drop off the marketplace between runs. Schedule the Actor and accumulate to keep a history.
slugs seems to be ignored	It only applies on the startup route. On listings the Actor reads the whole marketplace.

FAQ

What makes TrustMRR different from other acquisition marketplaces?

It verifies revenue against the seller's payment processor rather than taking a claim. That makes a revenue multiple meaningful, which is not true of listings where the revenue is self-reported.

Does TrustMRR have an API?

No public API. This Actor reads the public marketplace pages, which need no login.

What is the difference between the two routes?

listings returns every business currently for sale, which is the screen. startup returns the fuller figures a detail page carries for the slugs you name, including MRR, total revenue and active subscriptions.

Does it include sold listings?

No. It reads what is currently for sale. Schedule the Actor and accumulate the dataset if you want to see what left the market and at what price it was listed.

Can I use this to value my own business?

You can see what comparable businesses are asking and what multiples the market is showing, which is useful context. It is not a valuation, and asking prices are not sale prices.

Do I need a TrustMRR API key?

No. You need an Apify token to call the Actor over the API. No TrustMRR credential is involved anywhere.

Can I get this data in Python?

Yes, with the apify-client package as shown above. It returns parsed JSON, so there is no HTML or response handling on your side.

Can I get the data into Excel or Google Sheets?

Yes. Export the dataset as XLSX or CSV, or connect the Google Sheets integration so each run appends to a sheet.

Can an AI agent call this Actor?

Yes. Add it to an MCP client with the config above and the model can request what it needs on its own. Every record is flat JSON with named fields, so no post-processing is needed.

Is it legal to scrape TrustMRR?

This Actor reads TrustMRR's public marketplace pages, which need no login. Listings describe businesses rather than named individuals, but a seller name or handle is personal data where it appears, so handle it under your own obligations. Take your own legal advice for your use case.

Changelog

• 0.0.2 Added the startup detail route, the revenue multiple and 30 day growth.
• 0.0.1 First release. The marketplace listings.

Feedback

Found a field TrustMRR publishes that this Actor misses, or an input it rejects? Open an issue on the Issues tab with the input and what you expected. A daily test runs every Actor in the fleet against live sources, so parser fixes ship fast.