Skip to main content

Authentication

Every API and MCP call is authenticated. There are two mechanisms.

Request access and tenant approval​

Choose Request access on the sign-in page. Enter your email and, optionally, a short description. You do not need a password at this stage.

Your request waits for a Super Admin's approval. Submitting a request, including through Google sign-in, creates neither a tenant nor a login account. After approval, AgentData creates your tenant and account together. For email sign-in, use the password setup link to complete registration; approved Google users can sign in with Google.

Super Admins review requests in Settings → Users → Access requests and can approve or reject them. Tenant administrators manage users in their own tenant; they cannot view the platform request queue or Super Admin accounts. Invitations let users join an existing tenant without creating another tenant.

Older empty tenants created before approval are retained as inactive placeholders and hidden from the tenant list while their requests remain unapproved. Approval restores the corresponding tenant instead of creating a duplicate.

API keys (for CLI, IDE and server clients)​

Pass your key as a bearer token:

Authorization: Bearer agentdata_sk_ab12cdef…

You can also pass it as a query parameter where headers aren't convenient: ?api_key=agentdata_sk_…

Key facts:

  • Format: agentdata_sk_ followed by a hex secret.
  • Each key is scoped to your tenant and user, and tracks last_used_at.
  • Only a SHA-256 hash is stored — the plaintext key is shown once, at creation. Save it then.

Create a key​

In the app: Conversation → Query → Connect → Create key. Or via the API:

curl -X POST https://agentdata.mdm.biskilled.com/api/keys \
  -H "Authorization: Bearer <existing_session_or_key>" \
  -H "Content-Type: application/json" \
  -d '{"name": "claude-desktop"}'

Response returns the plaintext key (once), plus its prefix and name. List keys with GET /api/keys and revoke with DELETE /api/keys/{key_id}.

Treat keys like passwords

A key can read everything your tenant's confirmed model exposes. Store it in a secret manager, never commit it, and revoke keys you no longer use.

OAuth 2.1 (for web connectors)​

Web connectors such as claude.ai and ChatGPT authenticate over OAuth 2.1 instead of a static key. AgentData advertises its authorization server via .well-known/oauth-protected-resource, so a compliant client discovers and completes the flow automatically. Tokens are per-application and scoped to your tenant.

Enforcement​

In production, the API and MCP endpoints fail closed — a request with no valid credential gets 401, and the response carries a WWW-Authenticate header so web connectors can discover the OAuth server. In local development this can be relaxed for convenience.

Enterprise SSO and downstream identities​

Entra OIDC SSO, OAuth OBO and customer-side AD/Kerberos delegation are planned, not enabled in the current app. The MCP OAuth flow above authorizes clients to AgentData; it is not Microsoft OBO. Existing source credentials determine the downstream database identity unless a separately implemented mode is available. See Enterprise identity & Active Directory for the proposed modes and preparation steps.