Mezmo Heartbeats API

The Heartbeats API from Mezmo — 1 operation(s) for heartbeats.

Operations 1

POST /edge/clients/{clientId}/heartbeat Send Heartbeat #

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/mezmo-heartbeats-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

mezmo-heartbeats-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Mezmo Edge Heartbeats API
  description: 'Edge / local deployment surface for Mezmo Pipelines. Self-hosted pipeline

    instances poll the control plane for configuration, send heartbeats, accept

    tasks, and report results.

    '
  version: v3
servers:
- url: https://api.mezmo.com/v3
security:
- PipelineServiceKey: []
tags:
- name: Heartbeats
paths:
  /edge/clients/{clientId}/heartbeat:
    parameters:
    - name: clientId
      in: path
      required: true
      schema:
        type: string
    post:
      tags:
      - Heartbeats
      summary: Send Heartbeat
      operationId: sendHeartbeat
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/Heartbeat'
      responses:
        '200':
          description: Heartbeat acknowledged; returns any pending tasks.
components:
  schemas:
    Heartbeat:
      type: object
      properties:
        timestamp:
          type: integer
          format: int64
        status:
          type: string
        version:
          type: string
  securitySchemes:
    PipelineServiceKey:
      type: http
      scheme: bearer