Track hazardous e-scrap/ITAD shipments (CRT glass, batteries, circuit boards) end-to-end using the EPA e-Manifest RESTful API
domain: EPA e-Manifest / RCRAInfo REST API (github.com/USEPA/e-manifest, rcrainfo.epa.gov) · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register as a RCRAInfo user and complete CROMERR-compliant identity proofing and e-signature setup — a prerequisite before any e-Manifest API call can create or sign a manifest
Review the API reference, sample client code, and JSON schema (emanifest.json) published in the USEPA/e-manifest GitHub repo, and obtain API credentials for the RCRAInfo test/preprod environment first
Use the manifest endpoints to create a draft manifest, add waste line items (EPA waste codes, DOT hazard class) for regulated e-scrap such as CRT glass or leaded/NiCd batteries, and route it to the designated receiving facility
Invoke the e-signature endpoints at each custody transfer point (generator, transporter, receiving facility) to certify the manifest electronically
Query the manifest status/retrieval endpoints to confirm final certification and pull the signed manifest data into your chain-of-custody records
Known gotchas
e-Manifest only covers RCRA hazardous waste — most ITAD/e-scrap material is non-hazardous and never gets a manifest at all, so confirm applicability before assuming a shipment needs one
Production API access requires passing EPA's system-to-system connection testing in the preprod environment first; this is a multi-step onboarding process, not a simple API-key signup
CROMERR identity-proofing and e-signature registration are human steps completed outside the API and can't be automated away
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?