Agent Auth

Agent self-signup

Create an organization and restricted API key by submitting an email and the current terms-of-service version.

Three server-side dedup branches — all return HTTP 200 (or 409 only for stale ToS) to block email enumeration:

  • New email → returns org_id + api_key. OTP sent to email.
  • Duplicate unverified-agent signup with current ToS → opaque response (no org_id/api_key). OTP rotated and re-sent.
  • Duplicate verified / console-origin org → opaque response. No email sent.
  • Stale tos_version (agent-origin) → 409 with current_version hint.

The returned key is bound to an unverified org. It is fully usable for reads and writes within the standard per-resource quotas, but the org cannot graduate from the introductory free-agent-unverified plan tier until you call POST /v1/agent/verify with the emailed OTP. Verification rotates the org to its normal plan (e.g. free-agent or — during the soft-launch window — pro via the auto-grant capacity gate).

Rate limit: 5 requests per 60 seconds per client IP.

post/v1/agent/sign-up

Request

  • Base URL: https://api.chronary.ai
  • URL: https://api.chronary.ai/v1/agent/sign-up
  • Auth: none required

Request body

emailstring email required
agent_namestring required
tos_versionstring required

Example request

{
  "email": "agent@example.com",
  "agent_name": "Support Agent",
  "tos_version": "2026-05-11"
}

Response

Sign-up accepted. New-org payload includes keys; duplicate returns the opaque shape.

OR

Example response

{
  "org_id": "org_a1b2c3d4-e5f6-7890-1234-567890abcdef",
  "agent_id": "agt_abcd1234xyz0",
  "api_key": "chr_sk_...",
  "message": "Verification code sent to email"
}

Changes

No recorded changes to this operation across all 1 revision of this API.