Is Zenode a drop-in upgrade for the Nexar API?

Yes. Zenode's GraphQL API is a drop-in upgrade for existing Nexar integrations. Point your queries to https://graphql.zenode.ai/graphql and authenticate with a Zenode API key; the queries your application already sends can stay in place.

Do I have to rewrite my Nexar integration for REST?

No. Use Zenode's drop-in GraphQL endpoint for the Nexar integration you already have. REST is available for new integrations, matching, catalog search, full records, AI Discovery, and Deep Dive.

What intelligence does Zenode add to component data?

AI Discovery ranks components against natural-language engineering requirements and explains why they fit. Deep Dive answers questions from component documentation and cites the source material it used.

Does Nexar provide similar-parts data?

Yes. Nexar's public GraphQL example returns related part records through its Similar Parts field. Zenode's live Alts web workflow additionally accepts application context and candidate parts; its dedicated alternatives API endpoint remains on the roadmap.

How does API usage differ?

Zenode makes REST part matching, BOM matching, and summary search free. Full records and AI jobs use credits. Nexar counts supply parts returned by queries against the application's matched-part limit.

How broad is Zenode's catalog?

Zenode publicly describes a catalog of 40M parts spanning thousands of distributors. The same catalog supports search, matching, part records, and AI workflows.

Nexar API upgrade

A drop-in upgrade for the Nexar API

Keep the Nexar GraphQL queries your integration already uses by pointing them at Zenode's compatible endpoint. Then go beyond Octopart supply data with ranked recommendations, datasheet-grounded answers with citations, and application-aware alternative-part research through REST and MCP.

Get an API key See a datasheet answer

What the data helps your team do

Compare the path from a query to a decision

Nexar is strong at retrieving Octopart supply data. Zenode keeps the familiar GraphQL workflow and adds recommendation and document intelligence for the engineering work that follows.

Comparison of the engineering outcomes supported by Zenode and the Nexar Octopart API
Engineering task	Zenode	Nexar
Upgrade an existing Nexar integration	The drop-in GraphQL endpoint lets you keep existing Nexar query shapes and upgrade by changing the endpoint and API credentials.	The original Nexar GraphQL API provides Octopart data to existing integrations.
Find a part from requirements	AI Discovery accepts natural-language engineering requirements and returns ranked components with a fit rationale.	The public Octopart API documents MPN, keyword, and filtered search; it does not document requirements-based recommendations with fit rationales.
Answer a datasheet question	Deep Dive returns a formatted answer, explanation, and citations to the manufacturer documents it used.	The public API documents technical specifications and datasheet links, but not a cited question-and-answer workflow over those documents.
Evaluate alternative parts	The live Alts web workflow accepts a prime part, candidate parts, and application context. A dedicated alternatives API endpoint is on the roadmap.	The Similar Parts GraphQL field returns related part records. Its public example does not include application context, comparison rationale, or cited evidence.
Understand why a part fits	Discovery explains why each ranked part matches the stated design need, so engineers can review the reasoning.	Search and Similar Parts return the requested component fields; the public API does not document a fit-rationale response.
Match and enrich a BOM	Match up to 250 lines in one free REST request, then retrieve full records only for the parts that need deeper data.	Supply requests accept up to 100 MPNs or part IDs, and returned matches count against the application's matched-part allowance.
Connect an AI engineering tool	A first-party MCP server exposes component search, part records, Discovery, and Deep Dive to compatible AI clients.	No first-party MCP server is documented publicly; teams can build their own tool layer around the GraphQL API.
Retrieve pricing and availability	Full part records include distributor offers, pricing, and availability alongside technical data; freshness varies by source.	Established Octopart supply coverage includes distributor pricing, inventory, offers, and factory lead-time fields.

Upgrade an existing Nexar integration

Zenode: The drop-in GraphQL endpoint lets you keep existing Nexar query shapes and upgrade by changing the endpoint and API credentials.
Nexar: The original Nexar GraphQL API provides Octopart data to existing integrations.

Find a part from requirements

Zenode: AI Discovery accepts natural-language engineering requirements and returns ranked components with a fit rationale.
Nexar: The public Octopart API documents MPN, keyword, and filtered search; it does not document requirements-based recommendations with fit rationales.

Answer a datasheet question

Zenode: Deep Dive returns a formatted answer, explanation, and citations to the manufacturer documents it used.
Nexar: The public API documents technical specifications and datasheet links, but not a cited question-and-answer workflow over those documents.

Evaluate alternative parts

Zenode: The live Alts web workflow accepts a prime part, candidate parts, and application context. A dedicated alternatives API endpoint is on the roadmap.
Nexar: The Similar Parts GraphQL field returns related part records. Its public example does not include application context, comparison rationale, or cited evidence.

Understand why a part fits

Zenode: Discovery explains why each ranked part matches the stated design need, so engineers can review the reasoning.
Nexar: Search and Similar Parts return the requested component fields; the public API does not document a fit-rationale response.

Match and enrich a BOM

Zenode: Match up to 250 lines in one free REST request, then retrieve full records only for the parts that need deeper data.
Nexar: Supply requests accept up to 100 MPNs or part IDs, and returned matches count against the application's matched-part allowance.

Connect an AI engineering tool

Zenode: A first-party MCP server exposes component search, part records, Discovery, and Deep Dive to compatible AI clients.
Nexar: No first-party MCP server is documented publicly; teams can build their own tool layer around the GraphQL API.

Retrieve pricing and availability

Zenode: Full part records include distributor offers, pricing, and availability alongside technical data; freshness varies by source.
Nexar: Established Octopart supply coverage includes distributor pricing, inventory, offers, and factory lead-time fields.

Richer component intelligence

Help engineers choose, validate, and explain a part

Recommend parts from the design requirement

Describe the electrical, mechanical, and application constraints and receive ranked parts with an explanation of each fit.

Answer questions the catalog cannot

Ask a question buried in a datasheet and return an answer, explanation, and citation to the source document.

Evaluate alternatives in context

Use the live Alts web workflow to compare a prime part and candidates against how the component will be used.

Put the same intelligence inside AI tools

Connect compatible clients through MCP for component search, full records, Discovery, and cited datasheet research.

Try Zenode Alts Read the Deep Dive docs

Developer experience

Richer intelligence, with a familiar REST API

Keep existing Nexar GraphQL queries through Zenode's drop-in endpoint, use REST for new work, or connect an AI client directly through MCP.

Task-specific REST endpoints

Start new integrations with documented JSON requests and responses for matching, search, full records, and AI workflows.

Drop-in Nexar GraphQL upgrade

Keep the GraphQL queries used by an existing Nexar integration while adding new Zenode capabilities through REST.

First-party MCP

Give compatible AI clients Zenode tools without maintaining a separate adapter around the component API.

Frequently asked questions