TEST IT OUT.
This is the live database. Every category that has cleared spec verification is browsable below: pick a category, narrow to a type, and filter by the specs that actually define the part. Match counts are free and instant; pulling rows is free 20 times per visitor, unlimited with a sign-in. A designer, an API, or an AI can work the same record with equal ease, and spec sheets generate on demand.
SIDE BY SIDE
A blank cell means the manufacturer does not publish that value; nothing is filled in for them.
hit RUN to query the live database (keys: manufacturer, category, family, type, attr.<name>, q, mpn, limit, offset)
This is the real API, live against the full database: match counts are free, rows are capped at 15 with the total alongside (20 free pulls per visitor, unlimited signed in). The same API is served for programmatic use at api.openspecindex.com (instructions at /llms.txt, spec at /openapi.json).
SEARCH IS SET UP PER CATEGORY AND GATE
Every category below has been through spec verification. The
GATES are the identity attributes that define the part (two parts must agree on
every gate to be interchangeable); the rest are scored, filterable specs. Discover
all of this programmatically at
/api/v1/categories
and the values it returns are exactly the values attr.<name>= accepts.
GIVE THIS TO YOUR AI
Paste this into ChatGPT, Claude, Grok, or any assistant with web access. It comes back with real distributors, real prices, and a link to the page every number came from. No key, no signup, nothing to configure.
Fetch https://api.openspecindex.com
That is the OpenSpec parts database. It is a public API, no key needed, with real manufacturer
part records, extensive specifications, and some pricing, each with a link to the source page.
The response tells you how to query it.
I am looking for a #10-32 nylon-insert locking nut in stainless steel.
1. Put 5 or 6 different distributors in a clean table with these columns: distributor, part
number, price, what that price actually buys (a single nut, a 100-pack, a bulk box), and a
clickable link to the source URL so I can check the page it came from.
2. Give me the spec sheet download links. Hand me the links; they are PDF and Word files, so do
not try to open them yourself.
3. Tell me how this would fit into my purchasing or engineering role.
Only use distributors and prices that OpenSpec actually returned. Do not add any from
your own knowledge, and if it returns fewer than I asked for, just tell me.
Under the hood that whole question is
one call, live, no key:
api.openspecindex.com/api/v1/find/10-32-nylock-stainless-nut.
Put your own words after /find/. Agents can read the full instructions at
/llms.txt.
Structured records with provenance are what an agent needs to answer with numbers instead of guesses. Agents start at /llms.txt on the API host: it explains the endpoints, and /api/v1/categories tells an agent which categories are verified and exactly which gates and values each one filters by. No guessing at parameter names.
Live results are real reads of the record against the full database, capped at 15 rows with the total match count alongside. Every value traces to its source page.