Datasets for AI training and data teams
The data you need,
delivered to your bucket.
Get ready-made datasets in legal, finance, healthcare and code, or have our team build a custom one. Every row keeps its source URL and license.
| doc_type | license | doc_format | source_name |
|---|---|---|---|
| 10-K filing | Unstated | html | |
| Court opinion | Public domain | ||
| Drug label | CC0 1.0 | json | |
| Trial record | Registry terms | json | |
| Final rule | Public domain | xml |
companies of all sizes
Ready-made datasets
US court opinions
Federal and state opinions with court, case type and citation graph.
Chapter 11 court records
Bankruptcy opinions, first-day filings and local rules from D. Del., S.D. Tex. and S.D.N.Y.
Statutes, codes and session laws
U.S. Code, state codes, constitutions, court rules and session laws.
Regulations and agency guidance
CFR, Federal Register, state administrative codes and agency guidance.
Municipal and county codes
Local ordinances, code sections and council legislation.
Describe the sources and fields, and our team builds a custom dataset from web pages, PDFs and licensed providers.
Not in the catalogue? We'll build it.
A list of domains, a URL list or a description of the data
- The fields each record needs
- How many records, roughly
- How often it refreshes
Collection from web pages, PDFs and licensed providers
- Fields and volume scoped with you
- A sample in your schema first
- The full collection after you approve it
Records in your schema, delivered to your bucket
- Parquet, JSONL or CSV, or raw HTML and PDFs
- The source URL on every record
- Weekly or monthly refreshes
- 01Technical documentation in non-English languages as raw HTML and PDFs, refreshed monthly with changed and new URLs
- 02Every page on a list of healthcare provider websites, crawled in full and dropped in S3
- 03Store-level menu prices for named competitors, collected every week
- 04Filings, court records and news tied to the tickers on a coverage list
Tell us the sources and fields, and we'll scope the dataset with you.
Talk to our teamDelivered your way
From request to delivery
- [ 01 ]
Pick a dataset or describe one
Choose from the catalogue, or tell us the sources, fields and volume you need for a custom build.
- [ 02 ]
Choose the slice and delivery
Narrow it by year, document type or jurisdiction, then pick the format, licensing filter and destination.
- [ 03 ]
Review a sample
Ask for about 1,000 rows first, so you can check the fields and coverage before the full delivery.
- [ 04 ]
Get the full set and refreshes
The dataset lands in your bucket or as download links, then refreshes weekly or monthly if you choose.
Or build it on the API
The free plan includes 1,000 credits a month.
Start for freeData you can use
Rights-cleared sources
Catalogue datasets are built from government works, public filings and openly licensed material. Publisher terms are reviewed per source before delivery, and each source is fetched under its own access rules.
Provenance on every row
Each row records its source URL, crawl date, license and rights basis. By default a delivery holds only public-domain and openly licensed rows.
Zero data retention
Enterprise plans can turn on zero data retention for /scrape, /interact and /search, so Firecrawl keeps no page content or extracted data after a request ends.
Ready for procurement
SOC 2 Type II compliant, with the annual renewal audit in progress. SAML SSO, SCIM, a DPA and US data processing, and you can buy through AWS Marketplace or Google Cloud Marketplace.
How Firecrawl compares with other ways to get data
| Feature | Firecrawl | Managed data services | In-house scrapers | Dataset marketplaces |
|---|---|---|---|---|
| Ready-made datasets in legal, finance, healthcare and code | Yes | No | No | Yes |
| Custom datasets built to your schema | Yes | Yes | Yes | No |
| License and rights basis on every row | Yes | Varies | No | Varies |
| Original HTML and PDFs kept next to the Markdown | Yes | Varies | Yes | Varies |
| Delivery to your S3, GCS or R2 bucket | Yes | Yes | Yes | Varies |
| No scraper code or parsers to maintain | Yes | Yes | No | Yes |
| Self-serve API for your own pipelines | Yes | No | Yes | No |
| Callable by AI agents through MCP, CLI and SDKs | Yes | No | No | No |


















