View as Markdown (for AI/KB) Whole knowledge base (llms.txt)
This page is for the administrator. Draft — some points need confirming, see the bottom.
MCP and REST are the same API. Sometimes a script is better than tool calls — for example, iterating a table or sweeping the fleet. Then you need a credential.
Personal key
Each person can have a personal key that identifies them to the API. Writes are attributed to that person.
Short-lived tickets
For a script you mint a ticket — a short-lived credential, read-only by default, limited in time and number of calls (at most 4 hours and 20,000 calls). It grants exactly what you already hold, nothing more, and can be revoked immediately if it ends up in the wrong place. A separate upload ticket applies only to the upload routes.
Service accounts
Systems that need to reach the API can be given a service account with the Viewer role. A health check lets you test that a credential works.
Everything is attributed and audited
Every call is tied to its credential and logged (see change log and audit). A revoked role or a disabled account stops a ticket at the next call, not only at expiry.
To confirm before publishing
Two points conflict in the sources and must be confirmed with Daniel R:
- Does reading require a seat? The licence view implies reading is never blocked, while the API description says even reading requires an identified credential and a seat (review or reader) since 2026-09-17.
- Service key. An older part still mentions a shared
X-Service-Key, while the API description says there is no shared service key. Decide whether this is fixed in Probe or in the text.
Related: people and access.
Probe is E-Sharp’s design-review engine. Every call carries its author.