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.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/chronary-ai:chronary-ai-terms-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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Chronary Terms 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: Terms
paths:
  /v1/auth/terms/current:
    get:
      operationId: getCurrentTerms
      summary: Get current Terms of Service version
      description: Returns the latest ToS manifest entry. No authentication required — intended for CLIs, SDKs, and agent-signup flows that need to read the current version at runtime rather than rely on a build-time constant.
      tags:
      - Terms
      security: []
      responses:
        '200':
          description: Current ToS manifest entry
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TermsVersion'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /v1/auth/terms:
    patch:
      operationId: acceptTerms
      summary: Accept the current Terms of Service
      description: Appends an immutable row to `tos_acceptances` (source=`reaccept`) capturing the accepting org, client IP, user-agent, and the ToS document SHA-256, then updates the denormalized `accepted_terms_version` / `accepted_terms_at` columns on the organization. Authenticated via JWT (console session cookie or Bearer token), not an API key.
      tags:
      - Terms
      security:
      - SessionAuth: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ReacceptRequest'
      responses:
        '200':
          description: Re-acceptance recorded
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReacceptResponse'
        '400':
          description: Validation error — invalid request body or query parameters
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Missing or invalid console session — these endpoints require a console JWT, not an API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '409':
          description: ToS version stale — the submitted `tos_version` does not match `CURRENT_TERMS_VERSION`. Response body includes a `current_version` field on the `error` object.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /v1/terms/accept:
    post:
      operationId: acceptTermsWithApiKey
      summary: Accept the current Terms of Service (API key)
      description: Bearer-API-key equivalent of `PATCH /v1/auth/terms`, for SDK / MCP clients that have no console session. Use it to clear a material ToS bump signalled by the `Chronary-Terms-Upgrade-Required` response header. Reaches the same re-acceptance path (appends an immutable `tos_acceptances` row and updates the org). Requires an org-level API key (`chr_sk_*`) — agent-scoped keys are rejected with 403.
      tags:
      - Terms
      security:
      - BearerAuth: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ReacceptRequest'
      responses:
        '200':
          description: Re-acceptance recorded
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TermsAcceptResponse'
        '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'
        '403':
          description: Forbidden — quota exceeded or operation not permitted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '409':
          description: ToS version stale — the submitted `tos_version` does not match `CURRENT_TERMS_VERSION`. Response body includes a `current_version` field on the `error` object.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    TermsVersion:
      type: object
      properties:
        version:
          type: string
          example: '2026-10-28'
        effective_at:
          type: string
          example: '2026-04-26'
        url:
          type: string
          example: https://chronary.ai/terms/v/2026-10-28
        material:
          type: boolean
          description: When `true`, clients should block on re-acceptance.
      required:
      - version
      - effective_at
      - url
      - material
    ReacceptRequest:
      type: object
      properties:
        tos_version:
          type: string
          minLength: 1
          example: '2026-10-28'
          description: Must equal `CURRENT_TERMS_VERSION`.
      required:
      - tos_version
    TermsAcceptResponse:
      type: object
      properties:
        accepted_terms_version:
          type: string
          example: '2026-10-28'
        accepted_terms_at:
          type: string
          format: date-time
          example: '2026-05-11T00:00:00.000Z'
      required:
      - accepted_terms_version
      - accepted_terms_at
    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
    ReacceptResponse:
      type: object
      properties:
        data:
          type: object
          properties:
            accepted_terms_version:
              type: string
              example: '2026-10-28'
            accepted_terms_at:
              type: string
              format: date-time
              example: '2026-04-24T02:30:00.000Z'
          required:
          - accepted_terms_version
          - accepted_terms_at
      required:
      - data
  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