SaaS Pricing Page Extractor - Plans and Trials API avatar

SaaS Pricing Page Extractor - Plans and Trials API

Pricing

from $5.00 / 1,000 pricing page reports

Go to Apify Store
SaaS Pricing Page Extractor - Plans and Trials API

SaaS Pricing Page Extractor - Plans and Trials API

Extract public SaaS pricing-page signals, price points, plan names, trial language, per-seat billing, usage pricing, and enterprise CTAs.

Pricing

from $5.00 / 1,000 pricing page reports

Rating

0.0

(0)

Developer

Sean J

Sean J

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

18 hours ago

Last modified

Share

What does SaaS Pricing Page Extractor do?

Collect public price strings before preparing a SaaS comparison sheet. This Actor finds amounts alongside trial or enterprise-plan language, with configured signals about billing by seat and usage. Open the Actor to inspect its input and pricing.

Start with one website

  1. Paste one public URL into the Input tab, preferably the relevant policy or resource page.
  2. Keep evidence enabled and set a run spending limit that covers both event fees below.
  3. Run the check, then inspect its sources and errors before expanding the list.

Example input with one public source URL checked on 27 October 2026. Current responses and coverage may differ:

{
"startUrls": [
{
"url": "https://apify.com/pricing"
}
],
"maxPagesPerSite": 3,
"concurrency": 1,
"requestTimeoutSecs": 10,
"includeEvidence": true
}

Read the evidence

Keep each source URL with the extracted amount and check its currency and billing context. The returned strings do not reliably associate every price with a named plan, seat count or monthly/annual billing period.

FieldHow to use it
status, confidenceSignal-detection status and a heuristic score, not a probability of correctness.
extracted.pricesPrice-like text strings, not validated plan-to-price records.
findingsShort source snippets when includeEvidence is enabled.
coverage, errorsRequest/download limits and problems affecting what was checked.

Export JSON or CSV with retrievedAt and your source notes so a later comparison retains its original context.

Scope and limits

JavaScript pricing widgets, negotiated quotes and location-specific offers may be missed. This version does not compare stored runs, send price-change alerts or calculate a complete purchase cost.

Checks use static public responses, without browser execution or login. Each site is bounded by 20 seconds, 1 MiB downloaded and 4 MiB decoded text; redirects and failed requests consume maxPagesPerSite attempts. Submit at most 100 combined URL/domain entries, including duplicates. An undetected signal is not proof of absence.

Pricing and spending control

Event fees are $0.002 per attempt (website-processed) plus $0.005 per useful report (pricing-report): $0.007 when both apply. Check the Pricing tab for the current rates. The report fee requires FOUND or PARTIAL with useful detected signals or extracted evidence. Failed or empty resource probes do not qualify; ordinary NO_SIGNAL/FETCH_FAILED output incurs only the attempt fee.

Budget for both fees before starting a website, and check the Pricing tab for platform terms and plan charges. Review RUN_SUMMARY before repeating billing/output uncertainty, because a retry is a new chargeable check.

Responsible use and support

Use permitted public targets and review their terms. Send a sanitized input through the Issues tab for support or a scope discussion.