01 — Playground
GET /v1/{resource}/{slug} Run a request, get JSON
Pick a resource and a slug. The response is fetched straight from the static dataset, right in your browser.
GET
/v1/smartphones/galaxy-s25-ultra Loading… 02 — Devices
Featured devices
Each card is built from a live detail response. Click one to load it into the playground.
03 — Endpoints
Every resource is a file
No query language, no auth. Each resource is a static file ending in /index.json.
04 — How it works
Curated → replayed → served
[ 01 ]
Curated data
Specs live as reviewed JSON files in the repo, each carrying at least one source URL.
[ 02 ]
Replayed to disk
The real API runs in-process and every response is written out — byte-for-byte identical.
[ 03 ]
Served from a CDN
No server, no cold starts. Just fetch() a file — exactly what this page does.
curl techapi.dev/v1/...
Start fetching in one line
No sign-up, no rate limit, no SDK. Point fetch() or curl at a URL and you have structured specs. Code is MIT, data is CC-BY-SA 4.0.