Skip to content

OSINT Data Sources, Scraped via One API

Open-source intelligence work usually means pulling the same handful of public page types over and over: press releases, government contract listings, corporate filings, public records and social media signals.

OUTPUT FORMATSHTMLJSONMarkdown

Those pages are rarely static HTML. They lean on JavaScript, they sit behind bot detection, and they often vary by country. An OSINT scraper API exists to absorb that friction so your code stays a thin HTTP call and your team spends its time on the data rather than on proxy pools and headless browsers.

What the API absorbs for you

The core value is that the messy parts of collection are handled server-side. A stealth proxy layer and a headless-browser layer deal with JavaScript-heavy pages and active bot detection, so your client only sends a URL and parameters. On top of that baseline, the platform exposes optional controls you enable per request: JavaScript rendering, premium proxies, geotargeting, screenshots, and CSS/XPath or AI-driven extraction rules. The practical effect is that one integration covers several OSINT source types instead of one bespoke scraper per site.

Three real OSINT collection patterns

Most OSINT scraping falls into three jobs, and each maps to a different emphasis in the request.

Press releases. Structured press release data feeds competitor tracking and industry-trend analysis. These pages are usually well-structured, so CSS or XPath extraction rules give you clean fields without AI extraction.

Government contracts. Contract records support competitive insight and lead identification. Listings often paginate and vary by jurisdiction, so plan for geotargeting and steady concurrency rather than bursty traffic.

Social media signals. Metrics and post data help spot emerging trends and tune content strategy. These pages are the most JavaScript-dependent and the most likely to trigger bot detection, so render_js and stealth_proxy are the levers to reach for first.

How a request flows

The sequence is short by design. First, create an account and obtain an API key; any free-trial allowance, credit grant or card requirement is set by the provider and should be checked on the current sign-up page before you plan a test run. Second, install an SDK for your stack (Python, Node, Go, PHP or Ruby) or call the endpoint directly. Third, send any public OSINT URL to the endpoint with your API key; the platform renders the page and handles bot bypass, returning parsed HTML or structured JSON. Fourth, add advanced parameters only when a target needs them: render_js for JavaScript, stealth_proxy for aggressive bot defenses, country_code for geo-specific content, and ai_extract_rules for natural-language extraction. A dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL — useful when you want to prototype without writing code first.

Field and control map

Use this as a quick reference when a request underperforms:

  • render_js=true — runs the page in a real headless browser and returns post-render HTML. Use when content is missing from the raw response.
  • stealth_proxy — routes through residential proxies with browser-like behavior. Use when a target blocks normal traffic.
  • country_code — routes through a residential IP in that country. Use when content differs by geography.
  • extract_rules — CSS or XPath selectors that pull structured fields out of the page.
  • ai_extract_rules — natural-language extraction instructions for AI-driven parsing.

A useful distinction when something fails: a block response usually means the target rejected the request shape (reach for stealth_proxy), an empty or partial body usually means JavaScript did not execute (reach for render_js), and intermittent failures under load usually mean the target is throttling aggressive patterns (space out requests or use multiple sessions).

Choosing a plan

Plans differ mainly in monthly API credits and concurrent requests, with support and team features appearing at higher tiers. Because request cost depends on which features you enable, estimate your credit burn per request type before picking a tier. The pricing table below is a dated reference captured from the original publisher; confirm current prices and terms with the provider before committing. All listed prices are exclusive of VAT. Treat the table as a starting point for comparison rather than a live quote: check the provider's current pricing page for the figures that apply to a new subscription, and note which features are bundled at each tier.

Compliance and scale notes

Proxy rotation and headless rendering are used to reduce IP-based blocking and mimic normal browsing. Throughput scales with concurrent requests. Before relying on either capability for a production workload, confirm the provider's current data-handling and acceptable-use terms, and test throughput against your own targets rather than assuming a fixed success rate or response time.

Plan reference (captured from original publisher; verify current terms)
PlanPrice / moAPI CreditsConcurrent requestsJS renderingRotating & Premium ProxiesGeotargetingScreenshots & Extraction RulesPriority Email SupportDedicated Account ManagerTeam Management
Hobby$1975,00025IncludedIncludedIncludedIncludedNot includedNot includedNot included
Freelance$49250,00050IncludedIncludedIncludedIncludedNot includedNot includedNot included
Startup (Recommended)$991,000,000100IncludedIncludedIncludedIncludedNot includedNot includedNot included
Business$2493,000,000200IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Business +$5998,000,000400IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 14$99914,000,000500IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 24$1,59924,000,000600IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 41 (Recommended)$2,39941,000,000700IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 69$3,59969,000,000800IncludedIncludedIncludedIncludedIncludedIncludedIncluded
Enterprise 120$5,799120,000,000900IncludedIncludedIncludedIncludedIncludedIncludedIncluded

All prices are exclusive of VAT. Plan names, credit allowances and feature availability reflect the original publisher's page at capture time and may have changed. Confirm current prices, credit allowances and feature availability with the provider before subscribing.

Frequently asked questions

How do I start scraping OSINT data?

Create an account, copy your API key, and send a GET request with the target URL. The platform renders the page, rotates proxies, and returns the data. Any free-trial allowance or credit grant is set by the provider, so check the current sign-up page for the terms that apply.

Will I get blocked when scraping OSINT data?

Requests are routed through rotating residential proxies and a real headless browser so they resemble normal traffic. If a target is unusually aggressive, enable stealth_proxy on the request.

Can I scrape OSINT data without writing code?

Yes. The dashboard request builder lets you paste a URL, set parameters, and copy a generated snippet in Python, Node, Go, PHP, Ruby or cURL.

How do I handle JavaScript when scraping OSINT data?

Pass render_js=true. The page runs in a real headless browser, the JavaScript executes server-side, and you receive the post-render HTML.

Can I scrape OSINT data from a specific country?

Yes. Pass country_code to route the request through a residential IP in that country, which matters when content varies by geography.

What's the rate limit for scraping OSINT data?

Limits are expressed as concurrency per plan rather than per-target rate limits. If a target throttles aggressive patterns, space out requests or use multiple sessions.