Chronary

Chronary Account claim API

The Account claim API from Chronary — 4 operation(s) for account claim.

GitHub OpenAPI

Operations 4

POST /v1/auth/claim/initiate Start an account claim #
POST /v1/auth/claim/verify Verify an account claim OTP #
POST /v1/auth/claim/{id}/revoke Revoke a verified claim during the hold window #
GET /v1/auth/claims List your account claims #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/chronary-ai/openapi/chronary-ai-account-claim-api-openapi.yml

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.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/chronary-ai:chronary-ai-account-claim-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

chronary-ai-account-claim-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Chronary Account claim 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: Account claim
paths:
  /v1/auth/claim/initiate:
    post:
      operationId: initiateAccountClaim
      summary: Start an account claim
      description: Initiates a claim of an agent-created Chronary account. Requires console JWT auth. Returns the same opaque shape regardless of whether the target email maps to a claimable account — by design, to prevent enumeration. Sends a 6-digit OTP to the target inbox; pair with `POST /v1/auth/claim/verify` within 10 minutes.
      tags:
      - Account claim
      security:
      - SessionAuth: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ClaimInitiateRequest'
      responses:
        '200':
          description: Opaque success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClaimInitiateResponse'
        '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'
        '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/auth/claim/verify:
    post:
      operationId: verifyAccountClaim
      summary: Verify an account claim OTP
      description: Verifies the OTP for a pending claim. Requires console JWT auth with `iat` within the last 5 minutes — older sessions return 401 `reauth_required`. On success the claim enters a 24h revocation hold; the original account holder can revoke from the notification email during that window. After 24h a cron promotes the claim and transfers all org-scoped resources.
      tags:
      - Account claim
      security:
      - SessionAuth: []
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ClaimVerifyRequest'
      responses:
        '200':
          description: Claim entered the 24h hold
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClaimVerifyResponse'
        '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'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /v1/auth/claim/{id}/revoke:
    post:
      operationId: revokeAccountClaim
      summary: Revoke a verified claim during the hold window
      description: Public endpoint — authenticates by the `revocation_token` mailed to the agent-org email at verify time. Allowed only while the claim is in `verified` state and the 24h window is still open. Returns 410 once the window closes.
      tags:
      - Account claim
      security: []
      parameters:
      - schema:
          type: string
          format: uuid
        required: true
        name: id
        in: path
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ClaimRevokeRequest'
      responses:
        '200':
          description: Claim revoked
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClaimRevokeResponse'
        '400':
          description: Validation error — invalid request body or query parameters
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: Resource not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '410':
          description: Revocation window has closed
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClaimRevokeResponse'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
  /v1/auth/claims:
    get:
      operationId: listAccountClaims
      summary: List your account claims
      description: Returns the developer's pending and historical claims, most recent first. Sanitized — never includes OTP hashes, revocation tokens, or full target emails.
      tags:
      - Account claim
      security:
      - SessionAuth: []
      responses:
        '200':
          description: List of claims
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ClaimsListResponse'
        '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'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    ClaimsListResponse:
      type: object
      properties:
        claims:
          type: array
          items:
            $ref: '#/components/schemas/Claim'
      required:
      - claims
    ClaimRevokeResponse:
      type: object
      properties:
        revoked:
          type: boolean
          enum:
          - true
      required:
      - revoked
    ClaimInitiateResponse:
      type: object
      properties:
        claim_id:
          type: string
          format: uuid
        message:
          type: string
      required:
      - claim_id
      - 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
    ClaimVerifyRequest:
      type: object
      properties:
        claim_id:
          type: string
          format: uuid
        otp:
          type: string
          pattern: ^\d{6}$
          example: '123456'
      required:
      - claim_id
      - otp
    ClaimRevokeRequest:
      type: object
      properties:
        revocation_token:
          type: string
      required:
      - revocation_token
    ClaimVerifyResponse:
      type: object
      properties:
        claim_id:
          type: string
          format: uuid
        status:
          type: string
          enum:
          - verified
        revocation_window_ends_at:
          type: string
          format: date-time
        expected_completion_at:
          type: string
          format: date-time
      required:
      - claim_id
      - status
      - revocation_window_ends_at
      - expected_completion_at
    Claim:
      type: object
      properties:
        id:
          type: string
          format: uuid
        target_org_email_masked:
          type: string
        status:
          type: string
          enum:
          - pending
          - verified
          - completed
          - revoked
          - failed
        created_at:
          type: string
          format: date-time
        verified_at:
          type:
          - string
          - 'null'
          format: date-time
        revocation_window_ends_at:
          type:
          - string
          - 'null'
          format: date-time
        expected_completion_at:
          type:
          - string
          - 'null'
          format: date-time
        completed_at:
          type:
          - string
          - 'null'
          format: date-time
        revoked_at:
          type:
          - string
          - 'null'
          format: date-time
        failure_reason:
          type:
          - string
          - 'null'
      required:
      - id
      - target_org_email_masked
      - status
      - created_at
      - verified_at
      - revocation_window_ends_at
      - expected_completion_at
      - completed_at
      - revoked_at
      - failure_reason
    ClaimInitiateRequest:
      type: object
      properties:
        agent_org_email:
          type: string
          format: email
          example: agent@example.com
      required:
      - agent_org_email
  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