API
MaterialsHub is built on two APIs you can call directly — the MIVAA API (the Python backend that does the heavy lifting: PDF processing, search/RAG, price & mention & job tracking) and the Supabase API (the platform database, auth, storage and edge functions). On top of those, a handful of endpoints are fully public and need no key at all — most notably the Jobs board API. This section explains what each API is for, how you authenticate, and where the live, always-current reference lives.
The live specs are the source of truth. Both APIs publish machine-readable, always-current documentation (Swagger/OpenAPI). The pages here orient you — the linked specs give you every endpoint, parameter and schema.
The three surfaces
| API | What it's for | Auth |
|---|---|---|
| MIVAA API | The application backend — PDF/catalogue processing, multi-vector search & RAG, and the partner tracking APIs (prices, mentions, jobs). | Session JWT, a platform key, or a kai_* partner key. |
| Supabase API | The data layer — REST over your tables (row-level-security enforced), auth, file storage, and the platform's edge functions. | Session JWT + the public anon key; RLS decides what you can see. |
| Public Jobs API | A public, key-less job board feed for your careers postings — for aggregators, no-code tools and your own site. | None — public GET. |
Which one do I want?
- You want to track prices, brand mentions or jobs from another product → the MIVAA partner APIs with a
kai_*key you generate in Profile → Subscription. - You want to read/write your own workspace data (contacts, products, documents) → the Supabase REST API as a signed-in user; RLS keeps you to your own workspace.
- You want to publish your open roles on your website or a job aggregator → the Public Jobs API. No key, no auth, just a GET.
References
MIVAA API
The backend API — base URL, auth models, the main surfaces, and the live Swagger / OpenAPI spec.
Supabase API
REST over your data, auth, storage and edge functions — with RLS, keys and the per-function docs.
Public Jobs API
The key-less job-board feed (Greenhouse/Lever/Ashby-style) — endpoints, fields and examples.
Rate limits & cost: partner API calls are metered — some operations debit credits from the key owner's balance (documented per endpoint), and public endpoints are cached and safe to poll politely. Check each reference for specifics before building against it.