🔔 EPA Pesticide Registration Check

One pesticide_registration_check verdict per queried registration number / product SKU — resolve against a local index built from the official EPA PPIS bulk files, keyless and logged-out.

Difference: A verification CHECK, not a dump. Submit EPA registration numbers (e.g. 1-7173) and get one definitive verdict each — FOUND (a registered pesticide product) with product name, status, signal word, approval/cancellation dates, restricted-use flag, and the registrant organization; or NOT_FOUND / SERVICE_FAULT. Rides the same bulk files as the epa-ppis-pesticide-products roster.

Output is one pesticide_registration_check row per result; billing is pay-per-event, the value event being one pesticide registration check (a $0.02 start fee per run, then $0.05 per pesticide registration check). Source: www3.epa.gov.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run 2M0HjbInAUPXjyGv9 on build 0.1.5 (2026-09-18), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

input	query	verdict	product_name	product_status	registrant_name
1-7173	1-7173	FOUND	SOUTHERN'S SOLUBLE OIL	Cancelled/Transferred	PRATT LABORATORIES
10163-1	10163-1	FOUND	PROKIL PARATHION 4 LB	Cancelled/Transferred	GOWAN COMPANY, LLC
999999-99999	999999-99999	NOT_FOUND

The run finished with the status message: PARTIAL: 2 resolved (1 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 3 | answers billable=2 | pesticide_registration_check charged=2

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• record_type (string) — e.g. pesticide_registration_check
• input (string/null) — e.g. 1-7173
• query (string/null) — e.g. 1-7173
• source (string/null) — e.g. https://www3.epa.gov/pesticides/PPISdata/product.zip
• verdict (string/null) — e.g. FOUND
• reg_number (string/null) — e.g. 1-7173
• reg_number_raw (string/null) — e.g. 00000107173
• product_name (string/null) — e.g. SOUTHERN'S SOLUBLE OIL
• product_status (string/null) — e.g. Cancelled/Transferred
• signal_word (string/null) — e.g. None
• approval_date (string/null) — e.g. 19760101
• cancellation_date (string/null) — e.g. 19760622
• restricted_use (string/null) — e.g. false
• registrant_name (string/null) — e.g. PRATT LABORATORIES
• registrant_state (string/null) — e.g. TX
• unbilled_reason (string/null) — e.g. not_found: no EPA pesticide registration matches this number/SKU

✅ What you get

What you get

One verdict per query. Only a completed official answer — a FOUND resolution — is billed; NOT_FOUND and service-fault are emitted and never billed; a run that resolves nothing fails loud.

Privacy: registrant/agent contact names and phones are never read or returned; agent files are never fetched. The interactive ordspub.epa.gov service (robots Disallow: /) is never called — the bulk file is the lawful door.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "queries": [
    "1-7173",
    "10163-1",
    "999999-99999"
  ]
}

The sample run charged exactly: 2 × $0.02 apify-actor-start + 2 × $0.05 pesticide_registration_check = $0.14 on the Free tier — every delivered row was billed.

This actor takes no size cap or filter beyond the input above, so the Store example is the one input to run; put it on a schedule to keep the data current.

🧾 JSON sample record

One real record from run 2M0HjbInAUPXjyGv9, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "record_type": "pesticide_registration_check",
  "input": "1-7173",
  "query": "1-7173",
  "source": "https://www3.epa.gov/pesticides/PPISdata/product.zip",
  "verdict": "FOUND",
  "reg_number": "1-7173",
  "reg_number_raw": "00000107173",
  "product_name": "SOUTHERN'S SOLUBLE OIL",
  "product_status": "Cancelled/Transferred",
  "signal_word": "None",
  "approval_date": "19760101",
  "cancellation_date": "19760622",
  "restricted_use": "false",
  "registrant_name": "PRATT LABORATORIES",
  "registrant_state": "TX",
  "unbilled_reason": null
}

🔧 How it works

Source. The actor reads www3.epa.gov — endpoints: https://www3.epa.gov/pesticides/PPISdata/company.zip, https://www3.epa.gov/pesticides/PPISdata/product.zip. Public pages and feeds only; nothing behind a login.

Transport. Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

Charging. Each pesticide registration check is charged at the moment it is pushed (pesticide_registration_check); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

🔧 How it works

How it behaves

product.zip + company.zip are downloaded once behind a CRC gate and indexed by both the raw 11-digit and the masked co-prod registration form; each query resolves against the index.

Source

https://www3.epa.gov/pesticides/PPISdata/product.zip + company.zip

Attribution

Source: U.S. Environmental Protection Agency — Pesticide Product Information System (PPIS) public files (public domain).

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Pesticide registration check (pesticide_registration_check)	$0.05	$0.045	$0.04	$0.0335

Worked at the live Free-tier price:

• 3 pesticide registration checks: $0.02 start + 3 × $0.05 = $0.17
• 25 pesticide registration checks: $0.02 start + 25 × $0.05 = $1.27
• 100 pesticide registration checks: $0.02 start + 100 × $0.05 = $5.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: PARTIAL: 2 resolved (1 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 3 | answers billable=2 | pesticide_registration_check charged=2.

⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www3.epa.gov. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. The source (www3.epa.gov) is read logged-out; the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other NexGen Watch actors actors?
A: Same output shape and billing model; this one covers www3.epa.gov. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Fewer rows than expected → the source had fewer items in scope → widen the input.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• EPA GHGRP Facility-Year Master — One facility_year_record per row of EPA's GHGRP PUB_DIM_FACILITY table — one Greenhouse Gas Reporting Program facility per reporting year, with the f…
• EPA GHGRP Sector-Gas Emission Ledger — One sector_emission_record per row of EPA GHGRP's PUB_FACTS_SECTOR_GHG_EMISSION table — one facility × reporting sector / subsector × gas × year, wit…
• EPA GHGRP Subpart-Gas Emission Ledger — One subpart_emission_record per row of EPA GHGRP's PUB_FACTS_SUBP_GHG_EMISSION table — one facility × reporting subpart × gas × year, with the self-r…
• EPA Pesticide Products (PPIS) — One structured pesticide_product_record per EPA pesticide registration — from the official EPA Pesticide Product Information System bulk files, publi…
• ESMA BMR Benchmarks Register — One structured benchmark_record per benchmark registered under the EU Benchmarks Regulation (BMR) — from the official ESMA registers machine endpoint…
• ESMA EU Fund Register — One fund_record per entry in the official ESMA EU fund register via the ESMA registers machine endpoint — keyless, logged-out
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.