Usage, Billing, Exports, and Users

This page is for the people who need to run the product after it is bought: admins, owners, operations teams, support leads, and finance-adjacent users. It maps the portal labels to the outcomes they control so nobody has to hunt through tabs during rollout or incident review.

​

Where To Look First

​

How Sports MCP Server Usage Is Measured

Sports MCP Server is billed on tool_call. In practice, that means:

• each MCP tool invocation is the primary billable unit
• the portal uses tool-call language for this product
• usage and billing views are built to make tool-call consumption understandable to both technical and commercial teams

​

What The Usage Tab Tells You

The Usage tab is the operational heartbeat of the product. Depending on the data available for the current period, teams can expect views such as:

• current-period usage and reset timing
• API Key Breakdown
• tool-level usage patterns
• recent tool calls
• latency and error visibility

​

Usage Notifications

The portal supports Usage Notifications in the product Settings tab. Current behavior in the customer webapp:

• threshold percentage can be set from 1 to 200
• admins can choose a metric type valid for the product
• one or more notification email addresses can be added

For Sports MCP Server, this is where customer teams decide how early they want to hear about approaching limits.

​

Extra Usage

The Extra Usage card gives admins a self-serve way to decide what happens after included usage is consumed. Current behavior:

• extra usage can be enabled or disabled by an admin
• a monthly spending limit can be set
• if the account is admin-locked, the control becomes informational
• the portal records who opted in and when

​

Billing

The Billing tab in global Settings shows:

• the current billing period for the product
• billed usage
• line items with quantity, unit, and subtotal
• historical billing periods

For Sports MCP Server, the billing unit is shown as tool_call.

​

Exports

Settings -> Exports is where admins can download org-wide usage data. Available controls in the customer webapp:

• From
• To
• Format

Supported formats:

• CSV
• JSON

Good uses for exports:

• finance reconciliation
• executive reporting
• incident review
• internal customer success reporting

​

Users

Settings -> Users is where admins manage the organization team. Key workflows include:

• Invite Members
• change a user’s role
• revoke access
• revoke pending invitations

​

Legal

Settings -> Legal is the portal home for customer-facing legal documents. It is not the daily operating surface, but teams should know where it lives.

​

Response Headers Worth Knowing

When quota headers are returned by the server, the most useful ones are:

​

Operational Advice

• create separate API keys per environment or product surface
• review Usage Notifications before launch, not after the first spike
• make one admin responsible for Extra Usage
• teach support or ops where Exports and Users live

​

Related Pages

• Self-Serve Access and Entitlements
• API Keys and CORS
• Auth, Quotas, and Errors