Chronary Agent Auth API
The Agent Auth API from Chronary — 2 operation(s) for agent auth.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/chronary-ai:chronary-ai-agent-auth-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Chronary Agent Auth API
version: 1.0.0
description: 'Calendar-as-a-service API for AI agents.
Manage calendars, events, and availability for AI and human agents.
All endpoints require an API key passed as a Bearer token.
**Authentication:** `Authorization: Bearer chr_sk_...` or `Authorization: Bearer chr_ak_...`
**Rate limit:** 10 requests/second per API key. Exceeds return HTTP 429.
**Quotas:** Monthly operation limits by plan — see Billing & plans and Rate limits.
**Agent bootstrap:** Custom extensions prefixed `x-agent-*` describe the self-signup flow for AI agents. These are not part of any registered OpenAPI extension — they are a Chronary convention.'
contact:
name: Chronary Support
email: support@chronary.ai
url: https://docs.chronary.ai
servers:
- url: https://api.chronary.ai
description: Production
security:
- BearerAuth: []
tags:
- name: Agent Auth
paths:
/v1/agent/sign-up:
post:
operationId: signUpAgent
summary: Agent self-signup
description: '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 limits: 5 requests per 60 seconds per client IP, plus a per-network sign-up budget (default 20 per UTC hour and 50 per UTC day per IPv4 address or IPv6 /64). Over either limit returns 429 with a `Retry-After` header.'
tags:
- Agent Auth
security: []
x-agent-bootstrap: true
x-agent-hint: Call this first. Returns a restricted API key that works immediately for reads + writes. Follow up with POST /v1/agent/verify once the human reads the OTP.
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AgentSignUpBody'
responses:
'200':
description: Sign-up accepted. New-org payload includes keys; duplicate returns the opaque shape.
content:
application/json:
schema:
anyOf:
- $ref: '#/components/schemas/AgentSignUpNewOrgResponse'
- $ref: '#/components/schemas/AgentSignUpOpaqueResponse'
'400':
description: Validation error — invalid request body or query parameters
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'409':
description: Submitted tos_version is out of date. Includes current_version hint.
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited — 10 requests per second per key exceeded
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal server error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
/v1/agent/verify:
post:
operationId: verifyAgentOtp
summary: Verify agent email OTP
description: 'Promote a restricted agent key to full access by submitting the 6-digit OTP received via email.
On success the org transitions `status: unverified → verified`, the plan upgrades from `free-agent-unverified` to `free-agent`, and the key immediately gains full write access.
On any failure (wrong OTP / expired / already burned after 10 attempts / unknown org) the response is a generic 400 validation_error — no information is leaked about which precondition failed.'
tags:
- Agent Auth
x-agent-bootstrap: true
x-agent-hint: Submit the 6-digit OTP the human received via email. Upgrades the restricted key to the full plan tier. Returns generic 400 on any failure to prevent enumeration.
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/AgentVerifyBody'
responses:
'200':
description: OTP verified; full access unlocked.
content:
application/json:
schema:
$ref: '#/components/schemas/AgentVerifyResponse'
'400':
description: Validation error — invalid request body or query parameters
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'401':
description: Unauthorized — missing or invalid API key
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'429':
description: Rate limited — 10 requests per second per key exceeded
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
'500':
description: Internal server error
content:
application/json:
schema:
$ref: '#/components/schemas/Error'
components:
schemas:
AgentVerifyResponse:
type: object
properties:
verified:
type: boolean
enum:
- true
example: true
message:
type: string
example: Full access unlocked
required:
- verified
- message
AgentSignUpOpaqueResponse:
type: object
properties:
message:
type: string
example: Verification code sent to email
required:
- message
AgentSignUpNewOrgResponse:
type: object
properties:
org_id:
type: string
example: org_a1b2c3d4-e5f6-7890-1234-567890abcdef
agent_id:
type: string
example: agt_abcd1234xyz0
api_key:
type: string
example: chr_sk_...
message:
type: string
example: Verification code sent to email
required:
- org_id
- agent_id
- api_key
- message
Error:
type: object
properties:
error:
type: object
properties:
type:
type: string
example: invalid_request
message:
type: string
example: The field "name" is required.
request_id:
type: string
example: req_01H9X4M2P5R8T6V0
required_plan:
type: string
example: pro
description: 'plan_required: the plan that unlocks the feature'
feature:
type: string
description: 'plan_required: the gated feature'
metric:
type: string
description: 'quota_exceeded and count caps: the metric at its limit (a PLAN_LIMITS key, accepted by POST /v1/billing/upgrade-requests)'
limit:
type: integer
description: 'quota_exceeded and count caps: the plan''s limit for `metric`'
upgrade_url:
type: string
description: Where a human upgrades the plan
docs_url:
type: string
contact_url:
type: string
description: 'Contract-managed plans: where to contact sales'
retry_after:
type: integer
description: Seconds until the request may be retried
required:
- type
- message
- request_id
required:
- error
AgentVerifyBody:
type: object
properties:
otp:
type: string
minLength: 6
maxLength: 6
pattern: ^\d+$
example: '123456'
required:
- otp
AgentSignUpBody:
type: object
properties:
email:
type: string
format: email
example: agent@example.com
agent_name:
type: string
minLength: 1
maxLength: 100
example: Support Agent
tos_version:
type: string
minLength: 1
example: '2026-10-28'
required:
- email
- agent_name
- tos_version
securitySchemes:
BearerAuth:
type: http
scheme: bearer
description: 'API key with `chr_sk_*` for org-level access or `chr_ak_*` for agent-scoped access. Pass in the Authorization header: `Authorization: Bearer chr_sk_...`'
SessionAuth:
type: apiKey
in: cookie
name: chronary_session
description: Console session JWT (HS256), issued by sign-in and sent as the `chronary_session` cookie (a Bearer JWT is also accepted). This is NOT a chr_sk_*/chr_ak_* API key — API keys are rejected with 401 on these endpoints.
x-agent-self-signup:
url: https://api.chronary.ai/v1/agent/sign-up
verify_url: https://api.chronary.ai/v1/agent/verify
restricted_key_returned: true
human_in_the_loop: otp_email
rate_limit: 5 requests per 60s per client IP
x-agent-bootstrap-script:
npx: npx @chronary/agent-init@latest
shell: https://chronary.ai/agent-init.sh
description: One-liner that performs sign-up, prompts for OTP, verifies, and creates a smoke calendar. Accepts CHRONARY_EMAIL and CHRONARY_OTP env vars for non-interactive flows.
x-llms-txt: https://docs.chronary.ai/llms.txt
x-llms-full-txt: https://docs.chronary.ai/llms-full.txt
x-mcp-server-card: https://chronary.ai/.well-known/mcp/server-card.json
x-api-catalog: https://chronary.ai/.well-known/api-catalog