Skip to content
triguna
  • Product
  • Guides
  • Docs
  • Pricing
↑↓ navigate ↵ open esc close
Log in Get API key

Best practices

View all →
Guide Person records Guide Company records Reference Identifiers and slugs

Patterns

View all →
  • Enrich on signup 7 min read
  • Nightly backfill 8 min read
  • Agent workflows 7 min read

Reference

View all →
/v1/people/profile Person profile Identity, work history, education, skills, optional contact details. /v1/companies/details Company details Identity, headquarters, size, industries, specialities, funding. errors Errors and limits ApiKey header, status codes, Retry-After, and the rate-limit headers.
Get API key
  • Product What the person and company APIs return
  • Guides Task-shaped walkthroughs and integration patterns
  • Docs The API reference, on docs.triguna.ai
  • Pricing Usage-based pricing, per record retrieved
  • Log in Sign in to the console at app.triguna.ai
  1. Home /
  2. Legal /
  3. Terms of service

Legal

Terms of service

Last updated 31 July 2026

Draft, pending legal review. This page describes our intended practice in plain language so you can evaluate the service. It is not the executed agreement. For a signable DPA or the current terms, write to support@triguna.ai.

The service

Triguna provides two authenticated HTTP endpoints that resolve an identifier you supply into a structured person or company record, retrieved live at request time.

Your account and keys

  • You are responsible for activity under your API keys. Keep them server-side.
  • A key carries no scopes and can do anything your account can, so treat it as a full credential. You may revoke one at any time.
  • We may suspend a key that is causing harm to the service, and will tell you why when we do.

Acceptable use

You agree not to use the API to:

  • build a general-purpose people-search product or resell records as a database;
  • enable unlawful discrimination, harassment, or surveillance of individuals;
  • present retrieved values to third parties as verified facts about a person; or
  • circumvent rate limits or the absence of a bulk endpoint.

Billing

  • Usage is billed per successfully retrieved record.
  • A lookup that resolves no record is billed, because the retrieval runs either way. Malformed identifiers, auth failures and rate limits are not billed.
  • Your balance is the cap. At zero, enrichment requests return 402 rather than spending further.

What we warrant, and what we do not

We warrant that a record reports the sources that contributed to it and the time it was assembled. We do not warrant that any value in a record is correct, current, or complete. Every field is nullable and a record may be thin or absent.

If a decision in your product depends on a record being true, that judgement, and the consequences of it, remain yours. See provenance for what the record actually claims.

Availability

Availability commitments and any contractual SLA are agreed per plan. Without a signed SLA the service is provided on a reasonable-efforts basis.

Ending the agreement

You may close your account at any time; usage already incurred remains payable. We may end the agreement for material breach of the acceptable-use terms, or on notice with a pro-rata refund of prepaid credits.

Changes

We will give notice of material changes to these terms, and of changes to the API that alter the contents of a record.

Contact

Questions about these terms: contact page.

Privacy Terms Data processing
triguna

Structured person and company records, assembled at request time.

Product

  • Person API
  • Company API
  • Pricing

Developers

  • API reference
  • Person endpoint
  • Errors and retries
  • OpenAPI spec

Writing

  • Blog
  • RSS feed
  • About

Company

  • Contact
  • Privacy
  • Terms
  • Data processing
© 2026 Triguna support@triguna.ai