Tessen Docs

Usage

Your own request volume, errors and latency. Scoped to the caller — there is no user parameter, deliberately.

GET/api/devstats

Requests, errors, latency percentiles and per-key activity.

Session cookie, or an API key carrying the read scope.

Query parameters

NameTypeRequiredDescription
daysintegernoWindow in days. Defaults to 30.

Request

curl "https://cloud.tessen.ai/api/devstats?days=30" \
  -H "Authorization: Bearer tsn_cloud_EXAMPLE"

Errors

StatusWhen
401No session and no valid key.
It names what it cannot measure rather than reporting zero — a confident 0 reads as "we measured it" rather than "we have no such record".

GET/api/usage

Your token consumption.

Session cookie only. An API key is refused regardless of scope — Not opened to keys today. This is a measured boundary, not a recommendation — an integration cannot read its own token usage programmatically yet.

Errors

StatusWhen
401Not signed in, or a key was presented instead of a session.