usage-lab

endpoint

https://usage-lab.pages.dev/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is usage-lab live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is usage-lab free to use?

Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.

What tools does usage-lab have?

6 tools: get_meter_rollups, create_meter, list_meters, get_account, get_docs, record_usage_events.

Is usage-lab safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_meter_rollups auth-required 1h ago

  Monthly totals per customer for one meter, recomputed from raw events (GET /api/v1/meters/{meter}/rollups). Returns total_quantity and per-subscription quantity and event_count. Needs your API key.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "required": [
      "meter"
    ],
    "properties": {
      "meter": {
        "type": "string",
        "description": "Meter key or id."
      },
      "month": {
        "type": "string",
        "pattern": "^\\d{4}-(0[1-9]|1[0-2])$",
        "description": "YYYY-MM (UTC). Defaults to the current month."
      },
      "subscription": {
        "type": "string",
        "description": "Optional: only this customer/subscription."
      }
    }
  }

  arguments 21 lines copy
• create_meter auth-required never probed

  Create a meter once (POST /api/v1/meters). aggregation: sum (add up value, e.g. tokens), count (number of events, e.g. tool calls) or unique_count (distinct unique_value, e.g. active users). Re-creating an existing key returns meter_exists (harmless). Free plan: 3 meters. Needs your API key.

  mcp-tool

  123456789101112131415161718192021222324252627282930

  {
    "type": "object",
    "required": [
      "key",
      "aggregation"
    ],
    "properties": {
      "key": {
        "type": "string",
        "pattern": "^[a-zA-Z0-9][a-zA-Z0-9_.-]{0,63}$",
        "description": "1-64 chars of letters, digits, _ . - (e.g. agent_tool_calls)."
      },
      "name": {
        "type": "string",
        "description": "Optional display name (defaults to key)."
      },
      "aggregation": {
        "enum": [
          "sum",
          "count",
          "unique_count"
        ],
        "type": "string"
      },
      "stripe_event_name": {
        "type": "string",
        "description": "Optional Stripe Billing Meter event_name for Stripe push (Pro/Ultra)."
      }
    }
  }

  arguments 30 lines copy
• list_meters auth-required 1h ago

  List the meters on your Usage Lab account (key, name, aggregation sum | count | unique_count). Needs your API key (Authorization: Bearer).

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• get_account auth-required 1h ago

  Your account: plan, event and meter limits, event_count and first_event_at (GET /api/v1/account). Needs your API key.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• get_docs auth-required never probed

  Quickstart for the Usage Lab metering API and this MCP server: how to get a free API key, connect, create a meter, record idempotent usage events and read rollups. No API key needed.

  mcp-tool

  1234

  {
    "type": "object",
    "properties": {}
  }

  arguments 4 lines copy
• record_usage_events auth-required never probed

  Record 1-100 usage events in one all-or-nothing batch (POST /api/v1/usage). Every event MUST carry its own idempotency_key; retrying with the same keys is safe (results say created / duplicate / conflict). Needs your API key.

  mcp-tool

  1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859

  {
    "type": "object",
    "required": [
      "events"
    ],
    "properties": {
      "events": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "idempotency_key",
            "subscription"
          ],
          "properties": {
            "meter": {
              "type": "string",
              "description": "Meter key or id. Optional only if the account has exactly one meter."
            },
            "value": {
              "type": "number",
              "description": "Required for sum meters (e.g. tokens). Defaults to 1 for count meters."
            },
            "timestamp": {
              "type": [
                "string",
                "number"
              ],
              "description": "ISO-8601 or unix seconds/ms. Defaults to now. Max 30 days old, max 5 minutes in the future."
            },
            "properties": {
              "type": "object",
              "description": "Optional JSON stored with the event, e.g. {\"traffic_class\":\"ai_agent\",\"tool\":\"search\"}."
            },
            "subscription": {
              "type": "string",
              "maxLength": 200,
              "description": "Required. Your customer or subscription id (who to bill)."
            },
            "unique_value": {
              "type": [
                "string",
                "number"
              ],
              "description": "Required for unique_count meters (e.g. a user id)."
            },
            "idempotency_key": {
              "type": "string",
              "maxLength": 255,
              "minLength": 1,
              "description": "Required. A stable id for this event (e.g. sha256 of run_id:step:tool_call_id, or your provider response id). Reuse it on retries: same key + same payload returns duplicate and counts once; same key + different payload is a conflict and the original is kept."
            }
          }
        },
        "maxItems": 100,
        "minItems": 1
      }
    }
  }

  arguments 59 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.