Metronome
Metronome is a usage-based billing platform providing real-time metering, pricing, invoicing, and revenue recognition for API and cloud services.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Metronome the way a machine reads it — 45 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Metronome scores 40.5/100 (developing), with a separate agent-readiness read of 32/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Metronome's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/metronome/"
title="Metronome on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/metronome.svg"
alt="Metronome Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/metronome/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/metronome/"
title="Metronome on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/metronome/card.svg"
alt="Metronome Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Metronome
Each block below is one kind of artifact we hold for Metronome. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Metronome Alerts API
[Alerts](https://docs.metronome.com/connecting-metronome/alerts/) monitor customer spending, balances, and other billing factors. Use these endpoints to create, retrieve, and ar...
Metronome Billable Metrics API
The Billable Metrics API from Metronome — 5 operation(s) for billable metrics.
Metronome Contracts API
A contract defines a customer’s products, pricing, discounts, commitments, and more. Use these endpoints to create and update contracts data.
Metronome Credits and commits API
Credits and commits are used to manage customer balances.
Metronome Custom fields API
[Custom fields](https://docs.metronome.com/integrations/custom-fields/) enable adding additional data to Metronome entities. Use these endpoints to create, retrieve, update, and...
Metronome Customers API
[Customers](https://docs.metronome.com/provisioning/create-customers/) in Metronome represent your users for all billing and reporting. Use these endpoints to create, retrieve, ...
Metronome Integrations API
The Integrations API from Metronome — 1 operation(s) for integrations.
Metronome Invoices API
[Invoices](https://docs.metronome.com/invoicing/) reflect how much a customer spent during a period, which is the basis for billing. Metronome automatically generates invoices b...
Metronome Named schedules API
Named schedules are used for storing custom data that can change over time. Named schedules are often used in custom pricing logic.
Metronome Notifications API
The Notifications API from Metronome — 6 operation(s) for notifications.
Metronome Packages API
The Packages API from Metronome — 3 operation(s) for packages.
Metronome Payments API
The Payments API from Metronome — 3 operation(s) for payments.
Metronome Products API
Products are the items that customers purchase.
Metronome Rate cards API
Rate cards are used to define default pricing for products.
Metronome Security API
[Security](https://docs.metronome.com/developer-resources/security/) endpoints allow you to retrieve security-related data.
Metronome Settings API
Use these endpoints to configure a billing API key, a webhook secret, or invoice finalization behavior.
Metronome Threshold billing API
The Threshold billing API from Metronome — 1 operation(s) for threshold billing.
Metronome Usage API
[Usage events](https://docs.metronome.com/connecting-metronome/send-usage-data/) are the basis for billable metrics. Use these endpoints to send usage events to Metronome and re...
Scroll within the panel for all 18 ·
Open Collections 20
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONMetronome Alerts API
OPEN COLLECTIONMetronome Alerts Billable Metrics API
OPEN COLLECTIONMetronome Alerts Contracts API
OPEN COLLECTIONMetronome Alerts Credits and commits API
OPEN COLLECTIONMetronome Alerts Custom fields API
OPEN COLLECTIONMetronome Alerts Customers API
OPEN COLLECTIONMetronome Alerts Integrations API
OPEN COLLECTIONMetronome Alerts Invoices API
OPEN COLLECTIONMetronome Alerts Named schedules API
OPEN COLLECTIONMetronome Alerts Notifications API
OPEN COLLECTIONMetronome Alerts Packages API
OPEN COLLECTIONMetronome Alerts Payments API
OPEN COLLECTIONMetronome Alerts Products API
OPEN COLLECTIONMetronome Alerts Rate cards API
OPEN COLLECTIONMetronome Alerts Security API
OPEN COLLECTIONMetronome Alerts Settings API
OPEN COLLECTIONMetronome Alerts Threshold billing API
OPEN COLLECTIONMetronome Alerts Usage API
OPEN COLLECTIONMetronome
OPEN COLLECTIONScroll within the panel for all 20 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Metronome Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Metronome Finops
FINOPSSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Metronome — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/metronome · machine-readable index on apis.io
This is an independent, third-party profile of Metronome, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.