Introduction
Integrate Zenode's component intelligence via REST and GraphQL — part search, catalog data, AI discovery, aggregations, and BOM matching.
Zenode exposes its electronic-component intelligence through a REST API for JSON-over-HTTPS integration, a GraphQL API for precise field selection, aggregations, and BOM matching, and an MCP server that gives AI agents native tools for the same data.
REST API
The Zenode REST API is a public, contract-stable HTTP API for part identification, catalog search, pricing and availability, and AI-driven part discovery and deep-dive research.
Base URL
1https://api.zenode.ai/v1The major version is in the path. New optional fields and new endpoints are additive within v1.
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 REST 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. See Identifiers.
GraphQL API
The Zenode GraphQL API gives you precise control over the data you fetch — request only the fields you need. It exposes the same part search capabilities as the REST API, and adds aggregations and BOM matching in a single request.
Endpoint
1POST https://graphql.zenode.aiAll requests are POST with a JSON body containing query and optionally variables.
An interactive GraphiQL explorer is available at graphql.zenode.ai — browse the schema, autocomplete fields, and run queries directly in the browser.
GraphQL adds aggregations (manufacturer, category, spec buckets) and BOM matching (supMultiMatch) that are not available on the REST API. Use REST for simple scripting with curl; use GraphQL when you need field selection or multi-part queries in one round trip.
MCP server
The Zenode MCP server exposes the same component intelligence to AI agents over the Model Context Protocol — but shaped for an agent, not as a REST mirror. Catalog search and resolution are free and return compact summaries; you pay only to open the full part record or run an AI tool. AI operations run blocking with live progress, tools return "did you mean…" guidance on mistakes, and everything is text-only.
Endpoint
1https://api.zenode.ai/mcp/Connect any MCP client with your zn_ API key as a bearer token. See the
MCP overview and the setup guides for
Claude, Cursor, and
VS Code.
Use the REST/GraphQL APIs when your own code is the caller and you want full records in one response. Use the MCP server when an LLM agent is driving and benefits from cheap exploration, inline guidance, and blocking AI calls.
Get started
MCP server
Give an AI agent native tools — free search, charged details, and blocking AI research with live progress.
REST quickstart
Make your first REST API call — match a part end to end.
GraphQL overview
Query parts, aggregations, and BOM matches with GraphQL.
Authentication
Create an API key and authorize REST and GraphQL requests.
Rate limits & usage
Per-minute throttling and how REST and GraphQL meter usage for billing.
REST usage billing
Which REST endpoints are free vs part-record or AI-token billed.
GraphQL quickstart
Make your first GraphQL query — curl and GraphiQL.
GraphQL reference
Types, inputs, and enums for the GraphQL schema.