Skip to main content
Turn text and image evidence into structured operational reports. Operational Evidence is a focused API product in The Wo. It transforms unstructured real-world evidence into a normalized report that software systems can consume. The current public API accepts text evidence, image URLs, or both, together with the operational context in which the evidence should be interpreted. It returns a structured result containing:
  • title;
  • description;
  • operational category;
  • suggested priority;
  • suggested next step;
  • tags;
  • risk flags;
  • confidence;
  • usage information for the operation.

​
Start here

Quickstart

Configure your environment and make the first POST /v1/evidence/reports request.

Product access

Check current plans and activation in Developer Console, then create an API key.

Report contract

Understand request fields, supported contexts, response fields, categories, and priorities.

API Reference

Review the machine-readable HTTP contract generated from OpenAPI.

​
Product goal

Operational systems frequently receive information that is difficult to use directly:
  • informal maintenance descriptions;
  • inspection notes;
  • photos without structured context;
  • damage reports;
  • delivery evidence;
  • field observations.
Operational Evidence converts that input into structured operational data behind a stable The Wo API contract. The public contract is independent from the AI provider used internally. Clients do not need to manage prompts, model configuration, provider response formats, provider-specific error handling, or provider-side image retrieval. When image evidence is submitted, The Wo retrieves the remote image through its shared secure remote-resource boundary before report generation. The original customer-controlled image URL is not delegated to the report provider for an independent fetch.

​
Current capabilities

Operational Evidence currently supports:
  • shared The Wo API key authentication;
  • text evidence;
  • image evidence referenced by absolute HTTP or HTTPS URLs;
  • secure remote image retrieval before report-provider execution;
  • operational context;
  • optional output language guidance;
  • synchronous report generation;
  • structured operational results;
  • Evidence Report persistence;
  • usage tracking;
  • monthly quota enforcement;
  • current monthly usage visibility.

​
Current public endpoints

POST /v1/evidence/reports creates a structured Operational Evidence report. GET /v1/usage/current lets the authenticated customer inspect current monthly usage, quota, and remaining units.

​
Current evidence types

The current public contract accepts:
  • text;
  • image URLs.
Audio, video, uploaded binary files, and streamed evidence are not part of the current public contract.

​
Current API lifecycle

A successful report request follows this flow:
Each successfully created Evidence Report currently consumes one evidence_report usage unit. See Usage and quotas for the complete usage and monthly quota behavior.

​
Shared platform boundary

Operational Evidence owns its product vocabulary and report-generation contract. Shared API-key behavior is documented once at the platform level in Authentication.

​
API version

The initial public API uses URL versioning:
Backward-incompatible public contract changes must not be introduced silently inside an existing API version.

​
Environment availability

The canonical production API origin is:
Customer integrations must use this HTTPS origin unless The Wo explicitly provides a different environment for a controlled validation activity. The staging environment is reserved for internal release validation and is not a customer integration target. Current product availability and plans are shown in the Developer Console. The OpenAPI contract advertises only the canonical production API origin.

​
Continue exploring