Ten small, sharp APIs for public data: sitemaps, structured data, domain records, feeds, SEC filings, PDFs, fuel prices, app charts, grocery deals, and government tenders. No subscription. No servers to run. You pay cents for the results you get, and nothing when you don't.
Every API reads public, logged-out, non-personal data - most of it straight from official endpoints (SEC EDGAR, IANA RDAP, government open data). No fragile scraping, no login walls, no grey areas.
Billing is per event: a domain lookup, an extracted page, a new filing. Events start at $0.0005. Run one job a quarter or a thousand a day. The price scales with what you actually get back.
Each one runs as a one-off job, on a schedule, or as an always-on HTTPS endpoint you can call from code and AI agents. Output as JSON or CSV, with webhooks if you want them.
Open on Apify, run with your input, get structured results. Live pricing is on each API's page.
Full URL inventory of any website from its sitemaps. Every run after that reports exactly what changed: pages added, removed, updated. SEO monitoring and fresh RAG indexes without re-crawling whole sites.
Every JSON-LD block, OpenGraph and Twitter Card tag, canonical URL and microdata item from any list of URLs - one clean record per page. Batch over thousands of URLs or call it synchronously from an agent.
Bulk domain lookups over RDAP, the structured successor to WHOIS: registrar, dates, status, nameservers, DNSSEC, plus expiry monitoring with alerts. Registry data only; contact records are never read.
RSS, Atom, GitHub releases, and status pages, deduplicated against everything previous runs saw. A scheduled run returns only what's new, ready to pipe into Slack, email, a database, or an agent.
Track SEC filings by ticker or CIK with new-filing alerts, or full-text search across all of EDGAR. Official SEC JSON APIs, no key needed. Clean metadata plus the canonical document URL.
Public PDF URLs in, clean per-page text and document metadata out. Built for RAG pipelines and agents; cheaper than the $0.022-0.04/page incumbents.
Station-level fuel prices from official government feeds (Spain, Austria, and Quebec at launch), normalized into one schema with radius and fuel-type filters.
Apple App Store top charts and Apple Music most-played for any country, with rank deltas vs your last run: who climbed, who dropped, who entered, who fell off.
Current weekly flyer deals from every major Canadian grocery chain for any postal code: Loblaws, Metro, Sobeys, IGA, Walmart and more, compared in one schema.
Open tenders from CanadaBuys and the EU's TED in one normalized feed, keyword-filtered and deduplicated over time. Scheduled runs return only new opportunities.
The APIs run on Apify, so there's nothing to deploy and billing is handled by the platform.
Each card above links to the API's page. A free Apify account is all you need to start. No credit card to try things out.
Fill the input form in the console, or POST the same JSON over the REST API. Results land in a dataset you can read as JSON or CSV.
Add a schedule for monitoring use-cases, attach webhooks, or call the always-on endpoint. You're billed per result event. Prices are listed on each API's page.
Every API here also runs in Apify's Standby mode: an always-on HTTPS endpoint that answers synchronously. That makes each one usable as an agent tool: your agent calls a URL with query parameters and gets JSON back in one round trip, no run-and-poll loop.
GET https://gratifying-graph--sitemap-diff.apify.actor/?domain=example.com
Authorization: Bearer <your Apify token>
→ { "added": [...], "removed": [...], "changed": [...] }
Endpoint paths and parameters are documented in each API's README on Apify.
An independent studio in Toronto, Canada. The APIs are built and maintained by us and run on Apify's infrastructure, so uptime, scaling, and billing are platform-grade even though the catalog is small and focused.
Yes, a free one. Apify handles accounts, billing, and the runtime. You pay Apify for the result events each API emits; the prices shown here are the per-event prices set on each API.
These APIs target public, logged-out, non-personal data only. Where a source could expose personal information, the API strips it by design. The domain-intel API, for example, never reads registrant contact records, only registry and registrar data.
Mostly no. Seven of the ten read official data endpoints (SEC EDGAR, IANA RDAP, government open-data feeds, Apple's marketing feeds, published sitemaps and RSS). The rest read public web pages politely over plain HTTP: no login walls, no personal profiles, no protected content.
If it's public data and a good fit for pay-per-result, maybe. Email rafnir@gmail.com with what you need.