Chronary Usage API
The Usage API from Chronary — 1 operation(s) for usage.
The Usage API from Chronary — 1 operation(s) for usage.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/chronary-ai:chronary-ai-usage-api"
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.
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: 3.2.0
info:
title: Chronary Usage 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: Usage
paths:
/v1/usage:
get:
operationId: getUsage
summary: Get usage and quota stats
description: Returns current-month usage counters and plan limits for the authenticated organization.
tags:
- Usage
responses:
'200':
description: Usage data
content:
application/json:
schema:
$ref: '#/components/schemas/Usage'
'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:
Usage:
type: object
properties:
plan:
type: string
example: free
period_start:
type: string
format: date-time
example: '2026-04-01T00:00:00.000Z'
period_end:
type: string
format: date-time
example: '2026-04-30T23:59:59.000Z'
agents:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
calendars:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
events:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
api_calls:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
webhooks:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
webhook_endpoints:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
availability_queries:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
ical_subscriptions:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
proposals:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
recurring_events:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
description: Active recurring event series (DB-counted masters). Deleting a series frees its slot.
booking_pages:
type: object
properties:
used:
type: integer
example: 120
limit:
type:
- integer
- 'null'
example: 2500
description: '`null` means unlimited.'
required:
- used
- limit
description: Active public booking pages (DB-counted). Deleting a page frees its slot.
scoped_keys:
type: object
properties:
count:
type: integer
example: 3
limit:
type:
- integer
- 'null'
example: 50
description: Plan cap on active agent-scoped keys. `null` means unlimited (Scale).
required:
- count
- limit
description: Active agent-scoped (`chr_ak_*`) keys. `count` is a direct count; `limit` is the plan cap (`null` = unlimited).
holds:
type: object
properties:
created:
type: integer
example: 24
confirmed:
type: integer
example: 18
expired:
type: integer
example: 4
required:
- created
- confirmed
- expired
description: 'Temporal-hold lifecycle counters for the current period. Informational — not gated by any plan limit. Funnel identity: `created = confirmed + expired + active`, where `active` is derived (not stored). Counts cover all three end-of-hold paths (TTL expiry, manual release, priority bump).'
cross_calendar_queries:
type: object
properties:
used:
type: integer
example: 11
required:
- used
description: Availability requests that touched more than one calendar in the current period. Informational — gated separately by the `cross_calendar_availability` capability, not by this counter.
required:
- plan
- period_start
- period_end
- agents
- calendars
- events
- api_calls
- webhooks
- webhook_endpoints
- availability_queries
- ical_subscriptions
- proposals
- recurring_events
- booking_pages
- scoped_keys
- holds
- cross_calendar_queries
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
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