API overview
The Zenode API exposes the same data and AI that power zenode.ai over HTTPS and JSON, so you can build part selection, BOM tooling, and design automation on top of it.
The Zenode API is a public, contract-stable HTTP API for building on Zenode's electronic-component intelligence. It exposes the same data and AI that power zenode.ai — part identification, catalog search, pricing and availability, and AI-driven part discovery and deep-dive research — as plain JSON over HTTPS.
Base URL
1https://api.zenode.ai/v1The major version is in the path. New optional fields and new endpoints are additive and ship within
v1; anything breaking would ship under a new major version.
What you can do
Match parts & BOMs
Turn partial or messy part numbers into canonical, orderable MPNs — one at a time or a whole BOM in one request.
Search the catalog
Free summary search by query and parametric filters; fetch the full record per part when you need specs, pricing, and availability.
Look up parts & manufacturers
Fetch a full part record — specs, pricing, datasheets, regulatory — or a manufacturer, by slug.
AI part discovery
Describe what you need in plain language; get back the best parts to choose from, each with a rationale.
AI deep dive
Ask the AI specific questions about a part and get formatted, cited answers.
How requests work
- Requests and responses are
application/json; charset=utf-8. - Authentication is a Bearer API key (see Authentication).
- Field names are
snake_case; all timestamps are ISO-8601 UTC. - Every response carries a
request_id(also in theX-Request-Idheader) for support and tracing.
Resources are referenced by stable, readable slugs, never by internal database IDs — so the identifiers you store keep working as the catalog evolves. See Identifiers.
Usage billing
REST bills in two paid classes — part records (the full part record) and AI tokens — while matching, catalog search, and catalog metadata are free. See Usage billing for the full endpoint table.
Next
- Usage billing — which endpoints cost what
- Authentication — create a key and authorize requests
- Make your first call — match a part end to end
- API reference — endpoints, objects, and limits
- Coming soon — alternative-part discovery and job webhooks on the roadmap