Changelog
API changelog
Everything that changed in the API, newest first. Breaking changes are called out explicitly; anything that alters an existing record's contents says so.
-
api
Trace responses on person and company requests
Pass
trace=trueto see which sources were queried, which matched, and which were skipped for a given request. Trace output is metadata only and does not affect credit cost.GET /v1/people/profile?profile_id=rokafor&trace=true
Provenance → -
api
Per-key credit ceilings
Set a monthly credit ceiling on any API key. Requests past the ceiling return
402with a documented error body instead of silently spending.HTTP 402 credit_ceiling_reached
Authentication → -
sdk
Go and PHP SDKs are generally available
Both wrap the same two endpoints with typed request and response structs, retries with jitter, and idempotency key support. Neither adds a surface the HTTP API does not have.
go get github.com/triguna/triguna-go
Quickstart → -
api
Deriving seniority from person records
Person records guide →Titles are free text and inconsistent across companies, so seniority is not a field we return. It is a judgement you should own. The person records guide now documents a rule-based approach that keeps
unknownvisible instead of silently defaulting to a middle level. -
fix
Merge precedence documented and stabilized
Provenance →Conflicting values across sources are now reconciled by a published precedence order rather than resolution order. Records assembled before this date may differ on conflicting fields, so compare
fetched_atbefore treating an old stored record as equivalent to a new one. -
api
MCP server, public beta
Retrieval is exposed as tools in any MCP-compatible runtime, using the same keys, credits, and parameters as the HTTP API. The key is read from the environment and never passed as a tool argument, so it cannot leak into a transcript.
npx triguna mcp --stdio
Agents and MCP →
Keep up with changes
The blog covers the reasoning behind the larger ones.