Project fields
Project domain and event classification
Thedomain field tells OTAS what your service’s origin URL is. When an agent logs an API call, OTAS compares the event’s path against this domain to determine whether the call was made to your own backend (in-domain) or to an external service such as an LLM provider (out-of-domain). This distinction lets you filter and analyze your agents’ external API usage separately from internal traffic.
Team access and privileges
Project access is controlled through aUserProjectMapping, which links a user to a project with one of two privilege levels:
The user who creates a project is automatically made an Admin. Only Admins can invite other users, create agents, and manage SDK keys.
Backend SDK keys
Backend SDK keys (BackendAPIKey) let your server-side middleware authenticate with OTAS and log events on behalf of agents without requiring a user JWT. Each key is scoped to a single project.
Key format: otas_<prefix>_<secret>
The full key value is shown only once at creation time. OTAS stores only a hashed version in the database. Copy and store the key immediately.
Key lifecycle
1
Create a key
Send a
POST request to /api/project/v1/sdk/backend/key/create/ with the validity field (1–300 days) in the body. You must be a project Admin.2
Use the key
Pass the key in the
X-OTAS-SDK-KEY header when your backend middleware logs events. OTAS resolves the project from the key automatically.3
Revoke the key
Send a
POST request to /api/project/v1/sdk/backend/key/revoke/ with the sdk_key_id UUID. Revoked keys are immediately rejected and cannot be un-revoked.Creating a project
You can create a project from the OTAS dashboard or directly via the API. API endpoint:POST /api/project/v1/create/
id, which you’ll use as X-OTAS-PROJECT-ID in subsequent requests.
Only project Admins can create agents and SDK keys. When you create a project, you are automatically assigned the Admin role.