Quickstart

From API key to a verified agent credential in about ten minutes. This path uses the Operator Verification (human operator) and Agent Identity (agent registration) APIs. Every step here can also be done entirely in the UI — see the Dashboard guides.

Before you start

Create an account — company accounts sign up with a work email (free providers aren't accepted there); Personal accounts accept any non-disposable email. Confirm the verification link we email you. Every account is enabled for the full platform from day one. Running agents on your own machine? See Govern your local agents in 10 minutes.
Generate an API key in Dashboard → API Keys. Keys are shown once — store it securely.
Start a product to use it. Creating verification sessions requires an active subscription; registering an agent requires a live Trust Layer subscription — the 30-day Team plan trial counts, so start it from Billing first. See Errors for the exact responses. On a Personal account, the $20/month Personal plan (14-day trial, 5 agents included, then $2/agent) is the one subscription that covers all of this.

Verify a human operator

The standard path is in-dashboard, no API required: your organization's first two members approve each other on the Operators page, and every later member is approved by one existing verified operator (personal accounts get an operator credential automatically once their email is confirmed). That credential passes every operator gate. The API session below is the optional ID upgrade — a hosted biometric + document check that raises an operator (or verifies your own end users) to strong or enhanced trust.

Human verification

bash

# Optional ID upgrade — the hosted biometric + document check.
# (Standard operator verification is peer approval on the Operators page.)

# 1. Create an API key — Dashboard → API Keys → Create Key

# 2. Create a verification session
curl -X POST https://api.eniyantrust.com/v1/verifications/sessions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "external_user_id": "usr_abc123", "required_level": "strong" }'

# Response — redirect your user to the hosted page
# { "id": "sess_...", "redirect_url": "https://verify.eniyantrust.com/session/..." }

# 3. User completes the biometric + document check on the hosted page.
# 4. You receive a credential.issued webhook when it completes.

Register an agent

Agents are declaration-based — no biometric step. A full five-field declaration earns strong trust; add cloud attestation for enhanced (see Cloud attestation). Requires an active Trust Layer subscription.

Agent registration (KYA)

bash

# Register an AI agent (KYA). All five classification fields are required.
curl -X POST https://api.eniyantrust.com/v1/verifications/sessions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "entity_type": "ai_agent",
    "external_user_id": "agent_support_bot_v3",
    "required_level": "basic",
    "agent": {
      "model_name": "gpt-4o",
      "framework": "LangChain",
      "purpose": "Tier-1 customer support — read tickets, draft replies.",
      "autonomy_level": "human_on_loop",
      "access_mode": "read_write",
      "environment": "production",
      "data_classification": "confidential",
      "operator_credential_id": "cred_human_operator_abc"
    }
  }'

# No redirect for agents (no biometric step) — the credential is auto-issued.
# { "id": "sess_...", "agent_identity_id": "agent_...", "redirect_url": null }

Verify a credential

Verification is always server-authoritative — a revoked or expired credential fails even with a valid signature. For offline checks, validate the ES256 signature against the public JWKS (see Signing & verification).

Verify

bash

# Verify a human or agent credential in real time
curl -X POST https://api.eniyantrust.com/v1/credentials/verify \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "credential_id": "cred_xxxxxxxxxxxx" }'

# { "valid": true, "trust_level": "strong", "risk_result": "low", "expires_at": "..." }

Next steps

Trust levels — what basic / strong / enhanced require.
API reference — sessions, credentials, webhooks, errors & rate limits.
Security model — trust boundaries and what Eniyan does (and does not) do.