Skip to main content

​
Request beta access

Operational Evidence is currently available through a manually reviewed beta.

Request Operational Evidence beta access

Tell us about your company or project and how you plan to use Operational Evidence.
Submitting a request does not create an API key automatically and does not start a paid subscription. Do not include passwords, API keys, credentials, or sensitive operational secrets in your access request.

​
Approval

The Wo reviews the intended integration before enabling beta access. When access is approved, the beta setup can include:
  • an API customer identity;
  • an assigned Plan;
  • monthly quota;
  • an API credential;
  • the appropriate API base URL.
These values are provisioned manually during the MVP beta.

​
Receiving your API key

The API key is a secret credential. The Wo will provide the credential through an approved private delivery channel associated with the beta onboarding process. After receiving it:
  1. store it in a server-side secret manager or protected environment variable;
  2. do not commit it to Git;
  3. do not place it in frontend or mobile application code;
  4. do not include it in screenshots, tickets, or public logs;
  5. use it only for the approved integration.

​
Calling the API

Protected requests include:
See Authentication for the complete authentication behavior.

​
Quota during beta

Beta customers operate within an assigned monthly quota. For Operational Evidence:
Each successfully created report consumes one unit. See Usage and quotas.

​
No self-service promise

The current beta documentation intentionally does not promise:
  • automated account registration;
  • automated API key creation;
  • self-service Plan changes;
  • automated payment collection;
  • automatic overage billing;
  • a customer billing portal.
Those capabilities may be introduced later as explicit product features.

​
Beta feedback

During beta, preserve the requestId returned by failed API requests. When reporting an integration problem, provide:
  • the request ID;
  • the HTTP status;
  • the public error code;
  • a description of the expected behavior.
Never send your raw API key as part of a support report.