Product
Two endpoints. Everything you need about a person or a company.
Triguna turns a profile URL or a company URL into one normalized record, built from multiple independent sources, with the origin and retrieval time attached.
Person API
Send a profile slug and receive a person record: identity, location, network counts, work history, education, skills, badges, verification, and optional contact details.
Fields
member_urnfirst_nameheadlinelocationexperience[]education[]skills[]contact_infosourcefetched_at
Person API → /v1/companies/detailsCompany API
Send a company slug and receive firmographics: identity, headquarters, size, industries, specialities, and the last funding round.
Fields
company_idcompany_namecompany_urllocationsindustries[]specialities[]staff_infofunding_datasourcefetched_at
Company API →How a record gets assembled
Records are built from multiple independent sources and merged by documented precedence rules. No single source is load-bearing.
-
01
Normalize
The URL you send is canonicalized into a stable internal identifier. Slugs in, stable keys out.
-
02
Retrieve
Independent sources are queried in parallel, each contributing what it holds.
-
03
Merge
Conflicting values are reconciled by documented precedence rules, not by resolution order.
-
04
Return
One record, with source and fetched_at describing where it came from and when.
What Triguna does not do
Being specific about the boundaries is cheaper for both of us than finding them in production.
No search
You resolve identifiers you already have. There is no path that discovers people or companies matching a description.
No bulk endpoint
Enriching N entities costs N calls. Size your budget and your pacing around that from the start.
No claim of correctness
A record says these sources held this value at this moment. That is a narrower claim than truth, and it is one we can actually stand behind.
Start with one request
Free credits on signup, no card required. Usage-based pricing after that.