Cleaning power (PSI × GPM)
API · /pressurewasher-api
Pressure Washer API
Pressure-washer maths as an API, computed locally and deterministically — the cleaning-power, nozzle and water numbers a buyer or pro sizes and runs a machine by. The cleaning-units endpoint gives the cleaning power, PSI × GPM, with a duty class — both matter because pressure breaks the dirt loose and flow flushes it away, so a 3,000 PSI / 2.5 GPM machine (7,500 cleaning units) cleans far faster than the same pressure at 1.5 GPM. The nozzle endpoint gives the flow at a different pressure (a fixed nozzle flows with the square root of pressure) and the nozzle reaction force you feel, ≈ 0.0526 × GPM × √PSI in pounds — a few pounds on a consumer unit, enough on a big machine to need two hands. The water-usage endpoint gives the water used over a run, flow × time, in gallons and litres with an optional cost — a pressure washer actually uses far less water than a garden hose for the same cleaning. Everything is computed locally and deterministically, so it is instant and private. Ideal for pressure-washer shops and rental apps, cleaning-contractor and buying-guide tools, equipment calculators, and DIY sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — surface and detergent matter as much as the numbers.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 81 ms
- Server probes · 24h
- Subscribers
- 4,427
- active
- Total calls
- 76
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 700 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 700 calls/month
- 2 req/sec
- Cleaning units + nozzle + water
- No credit card
Starter
€4.25 /month
- 17,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 17,000 calls/month
- 8 req/sec
- Nozzle reaction & flow
- Email support
Pro
€15.10 /month
- 99,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 99,000 calls/month
- 20 req/sec
- Shop & rental pipelines
- Priority support
Mega
€46.40 /month
- 335,000 calls / month
- 48 requests / second
- Hard cap (429 above quota, no overage)
- 335,000 calls/month
- 48 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Wood Pellet API
Wood-pellet heating maths as an API, computed locally and deterministically — the consumption, heat-output and storage numbers a homeowner, installer or heating planner sizes a pellet system by. The consumption endpoint gives the pellets to meet a heat demand = the demand ÷ the usable heat per kilo, where usable = the calorific value × the boiler efficiency: ENplus wood pellets hold about 4.8 kWh/kg and a modern pellet boiler runs ~90 %, so each kilo delivers roughly 4.3 kWh — a 10,000 kWh annual demand then needs about 2.3 tonnes of pellets, around 154 fifteen-kilo bags or a bulk delivery. The heat-output endpoint inverts it: the usable heat from a mass = mass × calorific value × efficiency, so a tonne of ENplus pellets is about 4,800 kWh gross of which a 90 % boiler delivers ~4,320 kWh — the equivalent of roughly 480 litres of heating oil or 432 m³ of natural gas. The storage-volume endpoint sizes the hopper or silo: storage = the pellet mass ÷ the bulk (poured) density, about 650 kg/m³ for ENplus, so 2.3 tonnes fill roughly 3.6 m³ — size the store for the full delivery plus headroom for the fill pipe. Everything is computed locally and deterministically, so it is instant and private. Ideal for pellet-heating and installer tools, home-energy and quoting apps, and renewable-heat calculators. Pure local computation — no key, no third-party service, instant. Uses standard ENplus figures — set your own for a specific pellet grade. 3 compute endpoints. For cordwood use a firewood API; for propane/LPG a propane API.
api.oanor.com/pellet-api
Programming Languages API
The language definitions GitHub uses to recognise code (the open-source Linguist data) as an API — a clean reference for syntax highlighting, file-type detection, repository dashboards and developer tooling. For each of 800+ languages the API returns its type (programming, markup, data or prose), its brand colour (the hex GitHub paints it), the file extensions associated with it, common aliases, the GitHub language id and the editor (ace) mode. Look a language up by name or alias (golang resolves to Go), reverse-look-up which language(s) own a file extension (.py → Python; .h → C, C++, Objective-C), list the languages of a type, search, or list them all. Distinct from languages-api (ISO 639 human languages) — this is the programming-language reference. Served from memory — always fast.
api.oanor.com/proglang-api
MIME Types API
The canonical MIME / media-type database (the jshttp mime-db used by Express and most of the Node ecosystem: IANA + Apache + nginx), served from memory — no key. Resolve a media type to its file extensions, charset and compressibility; reverse-lookup the media type(s) for a file extension (e.g. png → image/png); and search or list types by source. 2,600+ media types, 1,000+ with file extensions. Lean, predictable JSON. Ideal for upload validation, Content-Type resolution, file-type detection, download handlers and developer tooling.
api.oanor.com/mimetypes-api
MusicBrainz API
The open music-metadata database as an API — artists, release-groups (albums), releases, recordings and labels, identified by stable MusicBrainz IDs (MBIDs), returned as clean JSON. Search any entity by name or Lucene query; look up an artist with their external links and tags, an album, a release with its full track list, a recording with its ISRCs, or a label; and browse an artist's complete discography. Live data with MBIDs, disambiguations, types, countries, life spans, ISRCs, barcodes, catalogue numbers and relations — the canonical identifiers that link and de-duplicate music data across services. Ideal for metadata enrichment and matching, music catalogues, tagging and library tools, and research. 11 data endpoints. Authenticated with an x-oanor-key; fair-use rate limits per plan.
api.oanor.com/musicbrainz-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Pressure Washer API?
What's the rate limit for Pressure Washer API?
How much does Pressure Washer API cost?
Can I cancel my subscription anytime?
Is Pressure Washer API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/pressurewasher-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/pressurewasher-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/pressurewasher-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/pressurewasher-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.