Guides
Guides and integration patterns
Guides cover a single record type end to end. Patterns cover a shape of integration: where to put the call, how to pace it, and what to do when it fails.
Guides
Working with one record type, from request to stored row.
How to map a Triguna person record to your own schema
Resolve a profile URL into a person record and map it onto your own person model: current title, tenure, seniority, and the fields worth storing versus re-requesting.
8 min read GuideHow to store and refresh Triguna company records
Resolve a company URL into firmographics, normalize headcount and country codes, decide which fields to store versus re-request, and avoid the platform_url mix-up.
7 min read GuideHow to design for partial enrichment records
Every field in a Triguna record is nullable. How to model absence, keep null out of your UI and scoring, and tell "no data" apart from "we never asked".
6 min readPatterns
Where the call belongs in your system, and what guards it.
How to enrich a user on signup without slowing it down
Call Triguna once at account creation, keep it off the signup request path, backfill asynchronously, and handle the failures that would block a new user.
7 min read PatternHow to run a nightly backfill without overspending
Pace calls against a rate limit you cannot predict, set credit ceilings, make retries idempotent, and pick refresh candidates so a backfill costs what you budgeted.
8 min read PatternHow to let an agent call the enrichment API safely
Expose Triguna over MCP, write the four rules an agent needs to call it correctly, cap spend with a credit ceiling, and make it report provenance.
7 min readStart with one request
Free credits on signup, no card required. Usage-based pricing after that.