Ardent Healthz API

The Healthz API from Ardent — 1 operation(s) for healthz.

Operations 1

GET /healthz Healthz #

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/ardent:ardent-healthz-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

ardent-healthz-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Fast Healthz API
  version: 0.1.0
tags:
- name: Healthz
paths:
  /healthz:
    get:
      summary: Healthz
      description: 'Process liveness — wired to k8s livenessProbe.


        Returns 200 while the Python process is alive. Has no dependency check by

        design: restarting a pod can''t fix a Supabase outage, and the thrashing

        only deepens an incident. See ARD-728 and `app/health.py` for context.


        Declared `async` deliberately (ARD-2136). A sync `def` endpoint is

        dispatched to Starlette''s threadpool, which is the same pool

        `check_supabase_ready` occupies via `asyncio.to_thread` on every 5s

        readiness probe. Liveness then queues behind dependency work it is

        documented not to depend on, times out, and the pod is killed anyway —

        exactly the thrashing ARD-728 set out to prevent. Answering on the event

        loop removes that coupling.'
      operationId: healthz_healthz_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties:
                  type: string
                type: object
                title: Response Healthz Healthz Get
      tags:
      - Healthz
x-provenance:
  method: harvested
  publisher: Ardent
  source: https://api.tryardent.com/openapi.json
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)