For developers & agents · Read-only beta
Your agents can now ask iimaginer directly.
The partner API and MCP server expose the same typed tools that power our dashboards and Mojo chat — org-scoped pipeline, candidate, and market intelligence with the receipts intact. Read-only, key-gated, and governed by each student's own visibility choices. Server-side. Always.
Private beta — keys are minted with you during partner onboarding. Nothing here is self-serve yet, and we'd rather tell you that than pretend otherwise.
Quickstart
Three calls to your first candidate list.
1 · Authenticate with your partner key
Every request carries your key as a bearer token. Keys are org-bound and scoped —/meshows exactly what yours can do.
curl https://iimaginer.com/api/v1/partner/me \
-H "Authorization: Bearer iim_live_..."2 · Search candidates — visibility enforced for you
Results honor each student's visibility level server-side. You cannot opt out of this, and neither can we — it's the contract the platform is built on.
curl "https://iimaginer.com/api/v1/partner/candidates?skills=Python,ML&country_code=SE" \
-H "Authorization: Bearer iim_live_..."3 · Or skip REST — point your agent at the MCP server
The same tools, agent-native (Streamable HTTP). Your key's scopes decide which tools your agent even sees.
claude mcp add --transport http iimaginer-partner \
https://iimaginer.com/api/v1/partner/mcp \
--header "Authorization: Bearer iim_live_..."Endpoints (beta)
All read-only. Responses are typed blocks — tables, metrics, lists — documented in the OpenAPI spec.
| Endpoint | Scope | Returns |
|---|---|---|
| GET/api/v1/partner/me | — | Introspect your key: org, tier, scopes |
| GET/api/v1/partner/candidates | candidates:read | Search candidates within your visibility horizon |
| GET/api/v1/partner/candidates/{id} | candidates:read | One candidate’s intelligence (tier-dependent depth) |
| GET/api/v1/partner/pipeline | pipeline:read | Your follow pipeline: stages, funnel, recency |
| GET/api/v1/partner/pipeline/graduation-timeline | pipeline:read | Upcoming graduations among followed candidates |
| GET/api/v1/partner/market/skill-trends | market:read | Trending skills in the visible talent pool |
| GET/api/v1/partner/market/skill-demand | market:read | Demand signal for one skill |
Visibility is law
public · verified_only · consent_required · private — enforced inside the same tool handlers the app uses. A private student is indistinguishable from a nonexistent one on this surface.
Limits & metering
60 requests/min per key with honest 429s and Retry-After. Every call is metered per key — you'll see your own usage before we ever bill on it.
Scoped keys, additive OAuth
Keys carry explicit resource:read scopes — nothing more. Bearer keys are the beta mechanism; OAuth 2.1 lands before general availability without breaking a single integration.
What this is not (yet)
We'd rather under-promise here.
- No writes. Introduction requests, follows, and anything that changes state stay in the app until our approval-gate machinery ships — by design, not by omission.
- No ATS sync. It's on the roadmap, co-designed with our first Partner-tier customer. It is not sold as shipped.
- Beta payload contract. The block format may evolve at GA;
/v1is the compatibility boundary we hold.
Want a key, or want to shape the write surface with us? Talk to partnerships.