looot Ops API

The Ops API from looot — 3 operation(s) for ops.

Operations 3

GET /v1/ops/summary Credential-health and operational inventory summary #
POST /v1/ops/probe-results Record one daily-probe run's verdict (#721) #
GET /v1/ops/signals Six operational signals: provider health, route quality, latency, errors, cost… #

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/looot:looot-ops-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

looot-ops-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: looot Ops API
  version: 0.1.0
  description: Discover, inspect, run, and pay for real (or fixture) provider operations through one bearer token.
servers:
- url: https://api.looot.ai
  description: Public API (default)
- url: https://coset-gateway.onrender.com
  description: Legacy host -- still live, for tokens issued before the public domain existed
- url: http://127.0.0.1:8787
  description: Local development
security:
- bearerAuth: []
tags:
- name: Ops
paths:
  /v1/ops/summary:
    get:
      summary: Credential-health and operational inventory summary
      description: Connection states and alerts are scoped to the caller's own organization; provider health/readiness and operational alerts reflect the whole platform, matching how the provider registry itself is not tenant-scoped.
      responses:
        '200':
          description: Summary
        '403':
          description: ops:read scope required
        '503':
          description: Ops summary unavailable
      tags:
      - Ops
      operationId: getV1OpsSummary
      x-operation-id-source: derived
  /v1/ops/probe-results:
    post:
      summary: Record one daily-probe run's verdict (#721)
      description: 'Reads the run from the probe workspace, judges it against the fixture''s expectation and stores one row in the probe results table. A second call for the same run returns the first row. Not tenant-scoped: platform operators with probe:write only.'
      responses:
        '200':
          description: Already recorded; the stored verdict
        '201':
          description: Recorded
        '400':
          description: Invalid body
        '403':
          description: probe:write scope and platform operator authority required
        '404':
          description: No such run in the probe workspace
        '422':
          description: Not a probe run, endpoint mismatch, or the run has not settled
        '503':
          description: Probe workspace not configured, or the table could not be written
      tags:
      - Ops
      operationId: postV1OpsProbeResults
      x-operation-id-source: derived
  /v1/ops/signals:
    get:
      summary: 'Six operational signals: provider health, route quality, latency, errors, cost…'
      description: Sourced from the analytics store when configured, otherwise computed from runtime state. Not tenant-scoped -- platform-wide operational data.
      responses:
        '200':
          description: Signals
        '403':
          description: ops:read scope and platform operator authority required
        '503':
          description: Ops signals unavailable
      tags:
      - Ops
      operationId: getV1OpsSignals
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer