We're building the infrastructure layer for construction waste intelligence.
Every dumpster rental platform, waste hauler, and construction PM tool deserves accurate, data-driven waste estimates. We're making that a single API call.
The problem we solve
Construction waste estimation is manual, inaccurate, and inconsistent. Contractors overbuy dumpsters, undershoot tipping fee budgets, and fail LEED diversion targets because there's no standardized data layer.
Project managers are Googling county landfill fees in spreadsheets. Dumpster rental platforms are guessing container sizes based on project descriptions. Waste haulers are pricing jobs on gut feel. None of this needs to be true.
The old way
- Manual research into local landfill websites
- Spreadsheet guesses at waste tonnage by project type
- Contractors overpaying by 40% on dumpster rentals
- LEED diversion targets missed because waste wasn't tracked
- No consistent data across different project types or regions
WasteCalc API
- 50-state tipping fee database, county-level fallback
- EPA C&D waste rates by project type and material
- Dumpster size recommendation from square footage alone
- LEED diversion % and credit eligibility in the response
- Single API call returns waste, fees, dumpster, and LEED data
Where our data comes from
We don't guess. Every data point in the API response is traceable to a primary source.
EPA C&D Studies
Waste generation rates by project type and material category, derived from EPA construction and demolition debris characterization studies.
50-State Tipping Fees
County-level C&D tipping fee schedules compiled from state environmental agencies and landfill operators, with fallback to state then national averages when county data is unavailable.
Recycling Facility Data
EPA RCRAInfo-registered facilities and state-level C&D recycling programs, used for diversion rate calculations and hazmat screening flags.
Built by developers who got tired of watching construction PMs guess
"We were building software for a dumpster rental company and kept running into the same wall: there was no API for this. Every estimate was a phone call to a landfill, a spreadsheet lookup, and a coin flip on container size. Contractors were overpaying by 40% on dumpster rentals just because nobody had standardized the data. We built WasteCalc API to fix that - for ourselves first, then for everyone building in this space."
How we operate
Accuracy over Speed
We would rather return a well-sourced estimate than a fast guess. Our 4-level ZIP fallback (ZIP → county → state → national) ensures we never return null - but we always tell you which level of precision you're getting.
Developer-First
Clean REST API with predictable response schemas. No SDK required. No surprise rate limit errors without a Retry-After header. Documentation that shows real payloads, not just parameter tables.
Data Transparency
Every API response includes a data_source field. You know whether a tipping fee came from the county landfill directly or fell back to a state average - and you can tell your users.