Admiral Health API

The Health API from Admiral — 1 operation(s) for health.

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/meetadmiral-com:meetadmiral-com-health-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

meetadmiral-com-health-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Admiral Health API
  version: 0.1.0
tags:
- name: Health
paths:
  /health:
    get:
      summary: Health
      description: 'Liveness, and it has to mean something.


        This is the ALB''s health check (infra/ecs.tf), so what it returns

        decides whether a task keeps receiving traffic. It used to return

        `ok` unconditionally — so a task whose database connection had died

        stayed in the target group and kept answering requests it could not

        serve, and the load balancer had no way to route around it.


        The query is deliberately the cheapest one there is. A health check

        runs every 30 seconds per task forever; anything that touches real

        tables would be a permanent load, and anything slow would turn a

        busy database into a failed deploy.


        It is also cached for a few seconds, because this endpoint is

        unauthenticated and has to be — the ALB cannot present a credential.

        Probing per request meant anyone who could reach the load balancer

        could open a database connection per request, for free, without

        signing in: a health check that can be used to exhaust the pool it

        exists to report on. The cache makes a flood cost one `SELECT 1`

        every `_HEALTH_TTL` no matter how fast it arrives, and the ALB''s

        30-second interval is far longer than that, so the check it gets is

        always freshly measured.'
      operationId: health_health_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Health