> ## Documentation Index
> Fetch the complete documentation index at: https://docs.thewo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Operational Evidence API Reference

> Machine-readable reference for the Operational Evidence public API.

The Wo API Reference is generated from the OpenAPI contract stored with the
application source.

## Current API version

```text theme={null}
v1
```

## Current endpoints

```http theme={null}
POST /v1/evidence/reports
GET /v1/usage/current
```

`POST /v1/evidence/reports` transforms operational evidence into a structured
Evidence Report.

`GET /v1/usage/current` returns the authenticated customer's current monthly
usage, configured quota, and remaining units.

## Authentication

Protected endpoints use:

```http theme={null}
x-api-key: <your-api-key>
```

See [Authentication](/platform/authentication) before integrating a protected endpoint.

## OpenAPI contract

The current Operational Evidence contract is defined in:

```text theme={null}
developer-docs/openapi/operational-evidence-v1.yaml
```

The specification describes:

* authentication;
* supported request fields;
* supported operational contexts;
* public report response fields;
* categories;
* priorities;
* customer usage visibility;
* monthly usage and quota semantics;
* HTTP response semantics.

## Base URL status

A public production API base URL has not been activated yet.

During the private beta, approved integrations receive the appropriate
environment base URL directly from The Wo.

The OpenAPI specification intentionally does not advertise a public server
until a real beta or production API environment exists.

When public infrastructure is activated, the corresponding server URL will be
introduced through a reviewed contract change.

Do not invent or hardcode an unannounced The Wo API hostname.

## Contract stability

The OpenAPI specification represents the documented public contract.

The deployed application implementation remains the runtime source of truth.

Changes to public HTTP behavior must update the OpenAPI contract and developer
documentation in the same delivery flow.

A dedicated contract-review step is used before documentation work is
considered complete.