BearingBrain Developers

Build bearing search, quote, and checkout workflows into your agents and systems. Discovery endpoints are open. Transactional endpoints require scoped keys.

Quickstart (read-only)

Start with search/stats/feed health. No key required for read discovery surfaces.

curl -sS https://bearingbrain.com/api/v1/search?q=6203-2RS&limit=3

Discovery endpoints for AI systems

/.well-known/openapi.json — canonical API schema
/llms.txt and /llms-full.txt — model-readable summaries
/facts — canonical JSON product facts
/api/v1/capabilities — capability and auth surface summary

Scope tiers

Free read tier: search.read, stats.read, feeds.read, mcp.read

Approved write tier: quote.write, checkout.write (plus matching read scopes)

Write scopes are reviewed to protect reliability and prevent abuse.

Transactional example (scoped key required)

curl -sS https://bearingbrain.com/api/v1/quotes \
  -H "x-api-key: YOUR_KEY" \
  -H "Idempotency-Key: demo-quote-001" \
  -H "content-type: application/json" \
  -d '{
    "items": [{"partNumber":"6203-2RS","quantity":2}],
    "currency":"USD"
  }'

Get API access

Submit onboarding details via POST /api/developers/signup to start key issuance. Phase-1 key management stubs are now available under /api/developers/keys using x-developer-lead-ref: devlead_....

Need write scopes or higher throughput? Include expected volume and use-case in signup notes.

# 1) signup (returns developerLeadRef)
curl -sS https://bearingbrain.com/api/developers/signup \
  -H "content-type: application/json" \
  -d '{
    "email":"[email protected]",
    "name":"Jane Developer",
    "organization":"Acme MRO",
    "useCase":"Internal bearing lookup assistant"
  }'

# 2) create free-tier key (replace LEAD_REF from step 1)
curl -sS https://bearingbrain.com/api/developers/keys \
  -H "content-type: application/json" \
  -H "x-developer-lead-ref: LEAD_REF" \
  -d '{
    "label":"acme-dev-key",
    "scopes":["search.read","stats.read","feeds.read","mcp.read"]
  }'