ABSCHNITT 06 // MASCHINENLESBARE DATEN · 227 PART RECORDS · 19 SYSTEMS
Datenzugriff
Everything on this site — every part number, fitment claim, approval tier and dated source — is available as static JSON and as llms.txt. llms.txt and the human-readable site are free forever, no key, with attribution to paprparts.com. The JSON API has a free tier — 100 requests/day with a free account key (launching shortly) — and paid tiers for commercial use: see /pricing/.
Endpunkte
| Endpoint | Gibt zurück |
|---|---|
/api/index.json | API manifest: endpoints, record counts, taxonomy definitions. |
/api/parts.json | All 227 part records: specs, supersession chain, fitment claims with approval tier and dated evidence. Free tier: 100 req/day (keys launching shortly). |
/api/systems.json | All 19 system records: approvals, headtops, summaries, sources. Free tier: 100 req/day (keys launching shortly). |
/llms.txt | llms.txt-spec index of key pages and machine-readable endpoints. |
/llms-full.txt | The entire database as readable markdown in one fetch — built for LLM ingestion. Never requires a key. |
Everything is pre-rendered at build time and served with Access-Control-Allow-Origin: * on /api/*, so you can fetch it from a browser, a script, or an agent without a proxy.
Keys. API keys are launching shortly. The free tier is 100 requests/day with a free account key (sign-up at /account/), attribution required, non-commercial. Until keys go live the endpoints answer without one; you can still append ?key=<your-project-name> so we recognise your integration in the logs. /llms.txt and /llms-full.txt never need a key.
Beispiel
Pull every part record and filter for batteries:
curl -s https://paprparts.com/api/parts.json \
| jq '[.[] | select(.category == "battery")
| {partNumber, brand, name, status, supersededBy}]'Or hand an LLM the whole database in one fetch:
curl -s https://paprparts.com/llms-full.txtWas die Felder bedeuten
Every fitment claim in parts.json carries exactly one approval tier from our four-tier compatibility taxonomy — officially-approved (on the approval documentation for the complete system), manufacturer-listed (on the manufacturer’s parts list, but not itself the approval document), physically-compatible (fits, but on no approval documentation — using it voids the system approval), or workplace-regulatory (a claim about workplace-programme suitability, the layer above the hardware).
Every record also carries a dataStatus: verified, audit-supported, or needs-verification. Every evidence object carries a sourceUrl, a sourceType and a verifiedOn date, because a compatibility claim without a dated source is just a rumour.
Datenlizenz
LICENCE v1 · 2026-07-05
Free for any use, including commercial — research, agentic, product — provided you keep visible attribution. Use the line Data: PAPR Parts Intelligence — paprparts.com and link it to paprparts.com wherever your medium allows a link.
Bulk redistribution or republishing of substantially the whole dataset — mirroring the API, reselling the JSON, or shipping the full database inside another product — requires written permission. Ask us first; for genuine integrations the answer is usually yes.
If you build on the data, keep the approval tiers and the needs-verification flags intact: stripping them turns honest records into unsafe advice.
No warranty. This is identification data, not safety advice and not an endorsement. PAPR systems are approved as complete tested systems; always verify a part against the manufacturer’s approval label before purchase or use. Found an error in the data? It matters — tell us.
Bauen Sie auf dieser API auf?
Leave an email for API news and higher-limit tiers. No account, no spam — just a heads-up if limits, licensing or new endpoints change. Everything here stays free and open. See /pricing/ for the Pro and commercial data licence tiers.