Search documentation

Search across all documentation pages

Get API Key
Concepts

Usage billing

Two paid classes — the full part record and AI tokens. Overview data (matching, catalog search, metadata) is free.

REST endpoints draw from the same credits ledger as GraphQL and the zenode.ai web tool. Usage is counted per unit of work, not per HTTP request. The model is simple: you pay for detailed part data and AI work — overview data is free.

Overview data is free. Matching a part number, searching the catalog, browsing manufacturers and categories, and reading facets return summary data — enough to identify a part and decide what to open — and don't consume your allowance (they're still abuse-tracked). You pay only when you fetch the full part record (specs, pricing, availability) or run an AI job.

Endpoint billing

EndpointBillingOne unit is…
POST /v1/parts/matchFree—
POST /v1/parts/match/batchFree—
POST /v1/parts/searchFree—
POST /v1/parts/search/facetsFree—
GET /v1/parts/{manufacturer}/{mpn}Part records1 full part record fetched
POST /v1/parts/discoverAI tokensLLM tokens on the job (usage.total_tokens)
POST /v1/parts/{manufacturer}/{mpn}/deep-diveAI tokensLLM tokens on the job (usage.total_tokens)
POST /v1/parts/{manufacturer}/{mpn}/alternatesAI tokensThe AI work of the search, billed as it runs
POST /v1/manufacturers/matchFree—
GET /v1/manufacturers/{manufacturer}Free—
POST /v1/categories/matchFree—
GET /v1/categoriesFree—
GET /v1/categories/{slug}Free—
GET /v1/jobs, GET /v1/jobs/{job_id}, GET /v1/jobs/{job_id}/streamFree—
POST /v1/jobs/{job_id}/cancelFree—
GET /v1/usageFree—

Paid endpoints require an active subscription with remaining allowance in the relevant class. When your balance for a class is exhausted, new requests in that class return 402 usage_limit_exceeded, with a reason saying which limit — see Errors → Usage limits.

Requests made with an organization's API key are billed to the organization, within its limits: each member's seat allowance, then the organization's shared pool (or, on an invoiced plan, its monthly spend limit), and any monthly cap on part lookups its plan sets for all members together.

The two paid classes

Part records

The full part record — specs, the distributor pricing ladder, availability and stock, datasheets, lifecycle, and regulatory data. This is the detailed data you pay for, billed once per part record fetched:

Catalog search and matching return lightweight PartSummary objects — MPN, manufacturer, description, image, status — enough to identify a part. They're free. You spend a part-record unit only when you open the full record for its specs, pricing, and availability.

AI tokens

Discovery, deep dive, and alternates run as async jobs. Billing happens when you create the job; following it via poll, stream, or cancel is free. Each completed discovery and deep-dive job reports exact token counts on usage:

JSON
1{
2 "input_tokens": 4200,
3 "output_tokens": 1800,
4 "total_tokens": 6000
5}

An alternates search fans out into many smaller AI steps — screening each candidate, then comparing each finalist — billed from the same allowance as they run. Its job's usage is null; a search won't start when your balance can't cover it.

REST vs GraphQL

RESTGraphQL
Paid part lookupPart records — one unit per full record fetchedpart_match — one unit per part returned
FreeMatching, catalog search, facets, manufacturers, categories, jobs, usagesupManufacturers, supCategories
AIToken-metered (REST only)—

The GraphQL API is a frozen compatibility surface and keeps its original per-part billing on supSearchMpn, supSearch, supMultiMatch, and supParts. On REST, matching and catalog search return summaries and are free — you pay only to fetch the full record.

Check your usage

GET /v1/usage returns running totals for the paid classes in the current billing period (part_records, ai_tokens). See Rate limits & usage for per-minute throttling and quota error codes.

Next