GraphQL is for Nexar migration only

Use the GraphQL API only as a drop-in replacement for Nexar's GraphQL when migrating existing integrations. For new projects and full platform capabilities, use the REST API— it's the actively maintained, modern interface.

Concepts

Usage billing

Part-returning queries bill one API unit per part returned; manufacturers and categories are free.

GraphQL paid queries bill against the same credits-api ledger as the REST API (part_match operation). One returned part = one usage unit for subscribed users. REST additionally meters match requests and AI tokens as separate classes — see REST usage billing. See Rate limits & usage for the full metering model across both APIs.

Query billing

Query	Billing
`supSearchMpn`, `supSearch`, `supMultiMatch`, `supParts`	Paid — `part_match` (1 unit per part returned)
`supManufacturers`	Free — abuse-tracked only
`supCategories`	Free — abuse-tracked only

Paid API access requires an active subscription with remaining monthly API units.

Quota checks and capping

Before a paid query runs, the API checks api_usage.can_use and api_usage.can_use_requests from credits-api.

If the requested result count exceeds your remaining quota, the query is capped to the remaining units and a warning is included in the response:

warnings on SupPartResultSet (search queries)
errorString on individual supMultiMatch lines

Errors — billing error codes and extensions shape
Rate limits & usage — shared throttle and quota model
Authentication — API keys and account setup
Search queries — paid search operations

Next Errors