Part specs for AI agents One call, plain words, cited answers. No key, no signup, nothing to configure.
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.
Fetch https://api.openspecindex.com
That is the OpenSpec parts database: a public API, no key needed, with real
manufacturer part records, specs, pricing, and a source link on every record.
The response tells you how to query it.
Find me a #10-32 nylon-insert locking nut in stainless steel.
1. Table of 5 or 6 distributors: distributor, part number, price, what that
price actually buys (a single nut, a 100-pack, a bulk box), and a clickable
source URL so I can check the page myself.
2. Spec sheet download links. They are PDF and Word files, so hand me the
links, do not open them yourself.
3. Bottom line, in a few punchy sentences: you just used it. What does it
mean for me, and for AI agents like you, that every distributor, spec,
and price lives in one queryable place? What happens to my BOM and
purchasing workflows if I wire this API in: speed, accuracy, and
savings for my purchasers and engineers?
Use only distributors and prices OpenSpec actually returned, nothing from your
own knowledge. 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.
Building against it directly? The API page has a live query console and the full per-category gate reference.