Korely Ops API

The ops API from Korely — 1 operation(s) for ops.

GitHub OpenAPI

Operations 1

GET /health Health #

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/korely-ai:korely-ai-ops-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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

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

OpenAPI Specification

korely-ai-ops-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Korely Agent Ops API
  description: Memory for AI agents that knows what was true when.
  version: 1.0.21
tags:
- name: ops
paths:
  /health:
    get:
      tags:
      - ops
      summary: Health
      description: 'Liveness, plus whether this thing can actually do its job.


        `extraction` reports what the provider last DID, in four states.

        `working`: the provider answered, `seconds_ago` says when; before

        this process has called it, the last extraction saved in the store,

        by whichever process made it. `unknown`: a key is set and no

        extraction has ever answered, or the database cannot be read.

        `not configured`: no key. `failing`: the last call was refused, or

        memories have waited more than five minutes with no extraction

        answering. Nothing is probed: a model call on every check would be

        billed every thirty seconds forever. Put `extraction.state` on your

        dashboard, not `status`.'
      operationId: health_health_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
components:
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer