Mezmo

Mezmo Usage API

Query log usage by app, host, or tag via /v1/usage/{type} and detailed byte-based consumption via /v2/usage. Used for chargeback, anomaly detection, and capacity planning against ingestion contract volumes.

Documentation GitHub OpenAPI

Documentation

📖

Documentation

https://docs.mezmo.com/log-analysis-api/reference/usage

Specifications

⚙

OpenAPI

https://raw.githubusercontent.com/api-evangelist/mezmo/refs/heads/main/openapi/mezmo-usage-api-openapi.yml

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-usage-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 email required.

GitHub Google LinkedIn

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

OpenAPI Specification

openapi: 3.0.3
info:
  title: Mezmo Alerts Archiving Usage API
  description: 'Manage Mezmo preset alerts. Preset alerts encapsulate presence or absence

    triggers, frequency, count thresholds, and notification channels (PagerDuty,

    Slack, webhook, email) that views attach to.

    '
  version: '1.0'
servers:
- url: https://api.mezmo.com
security:
- AccessToken: []
tags:
- name: Usage
paths:
  /v1/usage/{type}:
    get:
      tags:
      - Usage
      summary: Get Usage By Type
      operationId: getUsageByType
      parameters:
      - name: type
        in: path
        required: true
        schema:
          type: string
          enum:
          - apps
          - hosts
          - tags
      - name: from
        in: query
        required: true
        schema:
          type: integer
          format: int64
      - name: to
        in: query
        required: true
        schema:
          type: integer
          format: int64
      responses:
        '200':
          description: Usage rollup by resource.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/UsageEntry'
  /v2/usage:
    get:
      tags:
      - Usage
      summary: Get Detailed Usage
      operationId: getUsageDetailed
      parameters:
      - name: from
        in: query
        required: true
        schema:
          type: integer
          format: int64
      - name: to
        in: query
        required: true
        schema:
          type: integer
          format: int64
      - name: groupby
        in: query
        schema:
          type: string
          enum:
          - app
          - host
          - tag
          - level
      responses:
        '200':
          description: Detailed usage rollup with byte and line counts.
components:
  schemas:
    UsageEntry:
      type: object
      properties:
        name:
          type: string
        bytes:
          type: integer
          format: int64
        lines:
          type: integer
          format: int64
        from:
          type: integer
          format: int64
        to:
          type: integer
          format: int64
  securitySchemes:
    AccessToken:
      type: http
      scheme: bearer