API Reference
Every documented endpoint, at the contract its handler enforces.
Four resources are documented in full. Each entry names a route that exists in this application, and a test fails if a documented path has no route file or a documented method is not exported by it.
Executions
An execution is a plan: a goal, the stages Tessen chose for it, and the state of each. Creating one returns immediately with the plan — the work runs after the response.
POST/api/executionStart an execution, or resume one that stopped at an approval gate.
GET/api/executionRead one of your plans, or your ten most recent.
Capabilities
What Tessen can be asked to do, and the honest status of each — including the ones that are registered and deliberately not offered.
GET/api/capabilitiesThe capability registry, with coverage totals.
API Keys
Keys are created and revoked by a person in a browser, never by a program. This resource is documented so the boundary is visible, not so it can be automated.
GET/api/keysList your keys. Prefixes only — the secret is never returned again.
POST/api/keysCreate a key. The plaintext secret is returned exactly once.
DELETE/api/keysRevoke a key.
Usage
Your own request volume, errors and latency. Scoped to the caller — there is no user parameter, deliberately.
GET/api/devstatsRequests, errors, latency percentiles and per-key activity.
GET/api/usageYour token consumption.