AI Web Scraper — Any URL to JSON by Prompt ✅ No Code

AI Web Scraper — Any URL to JSON by Prompt ✅ No Code

Extract structured data from any URL with a natural-language prompt — describe what you want, get it back as clean data. No code, no CSS selectors, no LLM API key. Add an optional JSON Schema when you need an exact output shape. Powered by the Neuralverge API. You only pay for successful extractions — a miss costs only the $0.005 lookup fee. Export to JSON, CSV or Excel.

Ideal for one-off and repeatable extraction, monitoring, enrichment, research, and feeding clean data to AI agents (MCP-ready).

✨ Why this Actor

• 💸 Pay per successful extractions — if a page returns no content (or times out), the row is skipped and never billed. A miss costs only the $0.005 lookup fee.
• 🗣️ Just describe what you want — a natural-language prompt instead of code or selectors. Nothing to maintain when a site changes its markup.
• 🔑 No LLM API key, no login — the model and fetching run on the Neuralverge backend. You don't bring an OpenAI/Gemini key.
• 🎯 Optional JSON Schema — pass one to force an exact structured shape; omit it to get a clean markdown result. Geo-routing (countryCode) built in. MCP-ready for AI agents.

🔧 How it works

1. Provide a URL and an instruction (e.g. "Extract company name, website, industry, founded year, specialties"). Optionally add a JSON Schema for an exact shape.
2. Run the Actor. Fetching + AI extraction run on the Neuralverge backend.
3. Get one dataset row — { url, settings, machine, human }. With a JSON Schema the structured object lands in machine; without one, machine is null and the result comes back as a markdown summary in human.

If a URL returns no content (or an upstream error like a 504), it's logged and skipped without charge — you're not billed for that run.

Input

One URL per run.

Field	Type	Notes
url	string	The page URL to extract from.
instructions	string	Natural-language description of what to extract.
extractSchema	object	Optional JSON Schema for an exact output shape.
countryCode	string	Two-letter geo-routing code (advanced, default us).
finalizerModel	string	Extraction model (advanced).

{
  "url": "https://www.linkedin.com/company/ibm",
  "instructions": "Extract company name, website, industry, founded year, specialties"
}

What you'll receive

Each dataset row is { url, settings, machine, human } — the source url, the extraction settings (the JSON schema lives at settings.extract_schema_json when you pass one), the Neuralverge system machine output 1:1, and a human-readable markdown summary in human.

• With a JSON Schema — machine holds the structured object matching your schema; human carries a readable summary of the same facts.
• Without a schema — machine is null and the extracted facts come back as markdown in human.

Service fields (session_id, total_points, duration_ms, kind) and the raw API response are not included.

Example output (real run)

A real dataset row from https://www.linkedin.com/company/ibm with the prompt above and no schema — shown in full. With no schema the backend returns machine: null, so the extracted facts come back as text in human. Pass a JSON Schema and machine holds the structured object instead.

{
  "url": "https://www.linkedin.com/company/ibm",
  "settings": {
    "has_schema": false,
    "country_code": "us"
  },
  "machine": null,
  "human": "Company Name: IBM\nWebsite: http://www.ibm.com\nIndustry: IT Services and IT Consulting\nFounded Year: N/A\nSpecialties:\n- Analytics\n- Commerce\n- Research\n- Financing\n- Consulting\n- IT infrastructure\n- Experience Design\n- Cloud\n- Security\n- Internet of Things\n- Mobile\n- Cognitive\n- Technology support\n- Watson\n- Industry solutions\n- Resiliency services\n- Systems services"
}

Genuine result from a live run (no schema). Note Founded Year: N/A and the full 17-item specialties list come straight from the page. Pass a JSON Schema to get company_name, website, industry, founded_year, specialties as a structured object inside machine instead — human keeps the readable summary. No wrapper fields (kind/used_url/total_points) and no raw response are included.

Pricing

Pay per event — $0.005 per run, plus $0.005 per successful extraction ($5 per 1,000). A miss costs only the $0.005 lookup fee — you are never charged the per-result price.

Event	Price
Lookup (per run)	$0.005
Successful extraction (per dataset row)	$0.005

URLs that return no content are not charged the per-result price — only the $0.005 lookup fee applies. Pricing is on top of your Apify platform usage.

Free plan limits

Users on any paid Apify plan are not affected by anything in this section.

On the Apify Free plan all Neuralverge Actors share one budget, per user and per calendar month: 15 runs in total, at most 5 of them on this Actor, and 35 returned rows. A run that finds nothing still counts, because the lookup is performed either way. LinkedIn People Search is metered differently — one run there uses 25 of the 35 rows, because a full page of 25 profiles is bought upstream whether or not all of them are returned. When a limit is reached the Actor stops gracefully with a status message naming it; everything resets on the 1st of every month, and any paid Apify plan removes all of it.

Integrations & API

Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client to give an AI agent a general-purpose web-extraction tool.

FAQ

Do I need an OpenAI/Gemini or Crunchbase-style API key? No. The model and fetching run on the Neuralverge backend — you bring nothing but a URL and a prompt.

Do I have to write selectors or code? No. Describe what you want in plain language.

When should I use a JSON Schema? When you need a guaranteed structure (fixed field names/types) for a database or pipeline. Otherwise the markdown result in human is enough.

Am I charged if extraction fails? No. You're billed only for rows returned to the dataset; empty results and upstream errors are logged and skipped.

---

Disclaimer: This Actor is an independent tool. You are responsible for ensuring you have the right to extract from the URLs you submit and for complying with each site's terms and applicable law. All trademarks are property of their respective owners.