Skip to main content

Product access — Operational Evidence

Activate Operational Evidence

Use Developer Console to see whether Operational Evidence currently has a public plan and activation path: View plans and activation in Developer Console. Sign in or create an account, create or select a Workspace, and open Operational Evidence. When a public plan is available, complete activation in the Console. Then create an API key and follow the Quickstart. Availability and public plans come from The Wo’s current product catalog.
  • Live and Beta products may offer self-service activation when public plans exist.
  • Private Preview does not offer self-service activation.
  • Coming Soon products do not have public plans.
The Console shows the current state; this guide does not assign a fixed status to Operational Evidence. The Website and Console handle product discovery, activation, API-key management, and billing. This guide explains how the resulting product access is enforced by the API.

API access checks

POST /v1/evidence/reports is a protected product operation. A valid API key identifies the customer, but authentication alone does not guarantee that the customer may execute Operational Evidence. The current access path is conceptually:

Product entitlement

The customer must be entitled to execute the Operational Evidence evidence_report operation. Entitlement is evaluated before billable execution and before an idempotent POST replay is returned. If product access is not enabled, the API returns:
Example:
Internal entitlement reasons and identifiers are not exposed.

Entitlement check unavailable

If The Wo cannot safely evaluate product entitlement, the operation fails closed with:
Example:
Clients may retry a temporary 503 according to their normal retry policy.

Relationship to quota

Entitlement and quota are different decisions:
A customer can therefore be entitled to the product and still receive:
when the current quota is exhausted.

Idempotent retries

Entitlement is checked on every protected create request, including a request that could otherwise replay a completed idempotent result. If access has been disabled since the original request, the retry is denied instead of using the old idempotency result as an access bypass. When access remains enabled, existing idempotency behavior is unchanged:

Public metadata

Entitlement implementation data remains internal. The public Evidence Report success response does not include: