kryptos-io core API

kryptos-io core API as documented publicly: 3 operations. Contract generated from the documentation by API Evangelist (2026-10-30); not the provider's own document.

Operations 3

GET /health Health check #
POST /mcp HTTP transport (OIDC auth) #
GET /v1/sync/{syncid} Retrieve sync details including partially_synced status, recordsFailed, and limitReached information. #

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/kryptos-io:core-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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

kryptos-io-core-openapi-generated.yml Raw ↑
openapi: 3.1.0
info:
  title: kryptos-io core API
  version: '2026-10-30'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-30: 3 operation(s) read from 2 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; kryptos-io has published no machine-readable contract that the
    pipeline could find. Engine: anthropic.'
  x-evidence-tiers:
    code-example: 23
    documentation: 45
    pages-with-code: 20
    pages-read: 28
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-30'
  x-generator: generate-contract-from-docs.py
  x-engine: anthropic
  x-sources:
  - https://docs.kryptos.io/docs/mcp/mcp-overview
  - https://docs.kryptos.io/docs/webhooks/events
  x-docs-section: core
servers:
- url: https://api-v2.kryptos.io
paths:
  /health:
    get:
      operationId: get_health
      tags:
      - Health
      summary: Health check
      x-source: https://docs.kryptos.io/docs/mcp/mcp-overview
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetHealthResponse'
      x-evidence:
        kind: documentation
  /mcp:
    post:
      operationId: post_mcp
      tags:
      - Mcp
      summary: HTTP transport (OIDC auth)
      x-source: https://docs.kryptos.io/docs/mcp/mcp-overview
      responses:
        '201':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostMcpResponse'
      x-evidence:
        kind: documentation
  /v1/sync/{syncid}:
    get:
      operationId: get_v1_sync_syncid
      tags:
      - Sync
      summary: Retrieve sync details including partially_synced status, recordsFailed, and limitReached information.
      x-source: https://docs.kryptos.io/docs/webhooks/events
      parameters:
      - name: syncid
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetV1SyncSyncidResponse'
      x-evidence:
        kind: documentation
security:
- bearer: []
components:
  schemas:
    GetHealthResponse:
      type: object
      properties:
        success:
          type: boolean
    PostMcpResponse:
      type: object
      properties:
        success:
          type: boolean
        data:
          type: object
        error:
          type: string
        message:
          type: string
    GetV1SyncSyncidResponse:
      type: object
      properties:
        status:
          type: string
          description: Underlying sync status including partially_synced state
        recordsFailed:
          type: string
          description: Number of records that failed during sync
        limitReached:
          type: boolean
          description: Indicates if the sync was cut short by workspace transaction limit rather than connector failure
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
tags:
- name: Health
- name: Mcp
- name: Sync