API and Agent Usage Terms

1. What these terms cover

These terms govern programmatic access to Trooth: the public API, authenticated API access from a workspace, and any automated agent, script or crawler that interacts with the Service. They supplement the Terms of Service, which continue to apply. Deprecation and versioning commitments live in the API Versioning and Deprecation Policy.

2. The public API

The public API is described by the machine-readable contract at /openapi.json and documented at /developers. Only the operations that contract lists are offered publicly. Endpoints not in the contract are internal: they exist to serve the application, they change without notice, and building on them is not supported.

3. Credentials

Access to authenticated endpoints requires credentials issued through a Trooth workspace. Credentials are yours to protect: do not embed them in client-side code, public repositories or shared documents. Trooth may rotate or revoke a credential that appears in a public place or shows anomalous use, and will notify the workspace when it does. You are responsible for activity under your credentials until you revoke them or report them compromised to security@trooth.co.

4. Rate limits and fair use

Endpoints enforce rate limits, and a limited response carries HTTP 429. Respect the limit: back off and retry later rather than rotating identifiers, distributing requests to evade a cap, or otherwise circumventing limits. Circumvention is a violation of these terms and of the Acceptable Use Policy.

5. Idempotency

Endpoints that accept an Idempotency-Key header deduplicate retries of the same request. When you retry a request that mutates state, send the same key; the documented behavior at /developers describes the replay semantics.

6. Automated agents and crawlers

Automated access to public Network data is offered through the API rather than by scraping pages. If you operate an agent or crawler anyway, it must identify itself with an accurate user agent, honor robots directives, and respect rate limits. Trooth pages carry noai and noimageai directives, and Trooth does not authorize use of Service content to train AI models. Bulk republication of the directory, or presenting extracted Trooth data in a way that misrepresents what Trooth observed, is not permitted; how Trooth signals may be displayed is covered by the Badge and Mark Usage Terms.

7. What you may do with API data

You may use data obtained through the API to evaluate companies, run your own internal workflows, and build tools for your organization. You may not resell raw Network data as a dataset, misattribute Trooth as having verified something it only witnessed, or remove the source and timestamp context that gives a signal its meaning.

8. Availability and changes

The API is provided as described in the Terms of Service. Trooth publishes changes through the versioning policy above; it does not promise a particular availability level in these terms. Any service-level commitment, where one exists, comes from a written agreement between your organization and Trooth.

9. Suspension

Trooth may suspend programmatic access that degrades the Service for others, violates these terms, or presents a security risk, and will restore it when the issue is resolved.

10. Contact

developers@trooth.co for API questions; security@trooth.co for credential compromise.

Revised September 4, 2026: descriptions of retired features (composite figure, plan tiers, TruePass badge, Verified Inquiries) removed; the document now describes the witness record as published. Section 8 referred to a plan agreement; Trooth sells no plan, so it now refers to a written agreement. No term was narrowed.