> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmcpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Billing

> The plan, what it allows, what has been used against it, and the whole catalogue.

The catalogue comes back with the answer for the same reason the alert metrics do: a limit is domain knowledge, and a client holding its own copy of the prices is a client that can disagree with the invoice.



## OpenAPI

````yaml https://api.getmcpulse.com/docs/openapi.json get /v1/account/billing
openapi: 3.1.0
info:
  title: MCPulse API
  version: 1.0.0
  description: >-
    Analytics for MCP servers.


    The API is the product — the dashboard is one client and an MCP server will
    be another. Every number here is computed server-side so that both get the
    same answer.


    **Two kinds of auth.** Ingest uses an MCP API key (`mp_live_…`). Everything
    else uses a Supabase access token from the browser session.
servers:
  - url: https://mcpulse-production.up.railway.app
    description: MCPulse API
security: []
tags:
  - name: ingest
    description: What the customer's server sends
  - name: mcps
    description: MCPs and ownership
  - name: metrics
    description: Everything the dashboard reads
  - name: keys
    description: Ingest API keys
  - name: account
    description: Account, team and usage
paths:
  /v1/account/billing:
    get:
      tags:
        - account
      summary: Get Billing
      description: >-
        The plan, what it allows, what has been used against it, and the whole
        catalogue.


        The catalogue comes back with the answer for the same reason the alert
        metrics do: a limit is domain knowledge, and a client holding its own
        copy of the prices is a client that can disagree with the invoice.
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                nullable: true
        '401':
          description: Invalid or missing token
        '403':
          description: Your role does not permit this

````