Generate clients without losing Tri-Proof decision semantics.

The versioned OpenAPI contract covers Campaign API v2 resources, Bearer authentication, pagination constraints, response schemas, and machine-readable safety boundaries for cluster intelligence and evidence.

Open raw OpenAPI JSON Campaign API v2 Tri-Proof SDK

Versioned contract

OpenAPI 3.1 with a stable v2 contract version and production server definition.

Client generation

Unique operation IDs cover campaign, analysis, cluster, policy, decision and webhook operations.

Typed pagination

Catalog, evidence and member limits plus opaque cursor semantics are part of the machine-readable contract.

Safety extensions

`x-triproof-*` fields freeze non-recomputation and non-promotion boundaries for generated integrations.

Fetch the contract

The OpenAPI document itself is public. Business API requests still require a Bearer API key.

curl https://triproofprotocol.com/api/v2/openapi.json \
  -H "Accept: application/json"

Generate TypeScript types

Use the public contract in your preferred OpenAPI tooling.

npx openapi-typescript \
  https://triproofprotocol.com/api/v2/openapi.json \
  -o triproof-api-v2.d.ts

Generate a client

Generated clients inherit path, method, enum and pagination constraints from the contract.

openapi-generator-cli generate \
  -i https://triproofprotocol.com/api/v2/openapi.json \
  -g typescript-fetch \
  -o ./generated/triproof-v2

Machine-readable decision boundary

The contract explicitly states that Cluster Support Confidence is not a Sybil probability, inferred archetypes are not automatic decisions, shared infrastructure is not standalone Sybil evidence, unknown shared funding alone is not conclusive, evidence pagination never re-scores stored evidence, policy changes do not recompute prior runs, and Decision Package export remains read-only.