# Metronome > Metronome is a hosted usage-based billing platform, part of Stripe. Its REST API ingests usage events, defines billable metrics, rate cards and contracts, and generates invoices, with official SDKs for Python, Node.js, Go, Ruby and Java. - Canonical: https://www.anchorterminal.com/tools/metronome - Markdown: https://www.anchorterminal.com/tools/metronome.md (~8,100 tokens) - Slim: https://www.anchorterminal.com/tools/metronome.min.md (~1,680 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/metronome.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade B · 69.7/100 · rank #173 of 950 · #4 in Payment & monetisation platforms · not agent-ready · confidence medium** ## Assessment Metronome's API carries an `Idempotency-Key` on every POST, a public OpenAPI description of 142 operations, and agentic tokens whose writes wait for a person's approval. Prices for the Startup plan are public. Errors return only a `message` string, token scopes are set through support, and the status feed lists 13 incidents since 22 July 2026. ## Facts | Field | Value | | --- | --- | | Vendor | Metronome (Stripe) (https://metronome.com) | | Kind | HTTP API | | Category | Payment & monetisation platforms (https://www.anchorterminal.com/categories/payment-platforms) | | Transport | HTTP | | Endpoint | `https://api.metronome.com` | | Auth | API key · Bearer tokens, created by a person under Developer, API tokens in the Metronome app and shown once. A sandbox token reaches only sandbox data and a production token only production data. A token has its creator's permissions unless Metronome support scopes it by access level, environment or endpoint. Tokens can be archived, not edited. The API description also describes agentic tokens, whose writes need a person's approval. | | Pricing | Pay per use (0.8% fee) · The Startup plan costs 0.8 per cent of billing volume plus $0.04 per 1,000 ingested events, self-serve with a credit card for production. The pricing page says "Start free" and a sandbox account is self-serve. Custom plan prices are set by sales, and the docs describe an annual platform fee plus consumption charges on order forms (https://metronome.com/pricing, checked 2026-10-09). | | x402 | No · No x402, MPP or L402 in the OpenAPI description, the docs index or the pricing page (checked 2026-10-09). | | Licence | Proprietary service under the Stripe Services Agreement. The SDKs on GitHub are Apache-2.0 | | Packages | npm: `@metronome/sdk`; pypi: `metronome-sdk`; go: `github.com/Metronome-Industries/metronome-go` | | Source | https://github.com/Metronome-Industries/metronome-node | | Docs | https://docs.metronome.com/guides/get-started/home | | llms.txt | https://docs.metronome.com/llms.txt | | Last release | 2026-09-29 | | GitHub stars | 7 (as of 2026-10-09) | | npm downloads / week | 363,390 | | API | REST at https://api.metronome.com, OpenAPI 3.0.1 with 142 operations (127 under `/v1`, 15 under `/v2`), 123 of them POST, and 509 schemas | | Credentials | Bearer tokens made in the web app, separate for sandbox and production, archivable. Scoping by access level, environment or endpoint through support. Agentic tokens queue writes for approval | | Rate limits | Defaults in requests a second are 2,750 overall, 1,100 on `/v1/ingest`, 220 on high-frequency reads, 55 on standard operations, 11 on contract, balance and invoice lists, 8 elsewhere. 429 carries `X-Metronome-Rate-Limit-Type` | | Idempotency | `Idempotency-Key` on all POST endpoints (kept at least 24 hours), `uniqueness_key` on contracts, alerts and customer commits and credits, `transaction_id` on events (34 days) | | Pagination | `limit` (maximum 100) and a `next_page` cursor on list endpoints | | Errors | JSON with a single `message` field. Documented codes are 400, 401, 403, 404, 409, 429 and 5XX | | Platform limits | Defaults per environment are 5 active and 20 total contracts per customer, 20 subscriptions per contract, 5 active webhook destinations, 50 custom fields per object | | SDKs | Python `metronome-sdk` 4.11.1 (28 August 2026), Node.js `@metronome/sdk` 3.10.0 (23 July 2026), Go, Ruby and Java, generated by Stainless, Apache-2.0 | | Audit | `GET /v1/auditLogs` with actor (user or token name), resource, action, request ID, IP address and user agent, filterable by date and resource | | Integrations | Invoicing through Stripe, NetSuite and the AWS, Azure and GCP marketplaces. Tax through Stripe Tax, Avalara and Anrok. Salesforce, Segment and Workato connectors | | Certifications | SOC 2 Type 2 and SOC 1 Type 2 badges on the security page. The SOC 2 report is available from a Metronome representative | | Status | status.metronome.com on incident.io, components API (Overall, Ingest), Usage Pipeline, Alerts, Dashboard, Data Export and Embeddable Dashboards | | Capabilities | payments.metering, accounting.invoices | | Tags | hosted, usage-billing, openapi, llms-txt, webhooks, python, typescript, go, ruby, java, status-page, soc2, closed-source, sandbox | | JSON | https://www.anchorterminal.com/api/v1/tools/metronome.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 68 | 13.6 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 88 | 14.3 | | Agent ergonomics | 13% | 16.2 | 75 | 12.2 | | Security & auth | 14% | 17.5 | 68 | 11.9 | | Payments & pricing | 10% | 12.5 | 39 | 4.9 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 82 | 7.2 | | Transparency & trust (editorial 45, provenance 85) | 7% | 8.8 | 65 | 5.7 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **69.7 → B** | ### Why each score - Reliability 68: Hosted lines. status.metronome.com runs on incident.io with seven components (20). Its feed lists 13 incidents and three maintenance windows between 22 July and 8 October 2026. On 3 September a vendor's partial outage raised API and ingest error rates for two hours. API errors were also elevated on 22 July, 11 September (about 30 minutes) and 8 October (a two-minute burst), and most of the rest were data export or invoice delays. Durations were read on three incident pages only (10 of 30). Default rate limits are published per tier in requests a second (15). 429 responses carry `X-Metronome-Rate-Limit-Type` and the docs advise backoff, `Idempotency-Key` covers every POST and the SDKs retry twice by default. No `Retry-After` was found (13 of 15). The pricing page names enhanced SLAs on the Custom plan and no SLA document was found (0). The API is generally available (10). 68. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 88: A public OpenAPI 3.0.1 description with 142 operations and 509 schemas (25). llms.txt and a Markdown twin of each docs page (10). 131 of 142 operations carry a description longer than 80 characters and 76 have a section on when to use the call. Few say when not to (17 of 20). The description has 345 enums and 774 required lists, with 36 free-form maps (13 of 15). 118 operations carry a request example and 99 a response example. Errors are one `message` string, and only 87 operations document a 4xx response (10 of 15). Paths are versioned `/v1` and `/v2`, and a dated changelog tags API and SDK entries. No dated API versions (13 of 15). 88. - Agent ergonomics 75: Graded on the REST API. List calls take `limit` up to 100 and some switches such as `skip_zero_qty_line_items`. No field selection was found and contract and invoice objects are large (13 of 25). Cursor pagination with `next_page`, and filters on status and dates. Many reads are POST calls with a body (17 of 20). Errors carry an HTTP status and a `message` string with no stable code, and the status-code page gives one remedy per status (11 of 20). `Idempotency-Key` on every POST, `uniqueness_key` on contracts and alerts, and 34-day `transaction_id` deduplication on events (20 of 20). Creating a customer has no required list in the description, ingest aliases stand in for IDs, and official SDKs cover five languages (14 of 15). 75. - Security & auth 68: Bearer tokens are created in the web app, shown once, separate for sandbox and production, and can be archived. Scoping by access level, environment or endpoint exists but is set by contacting support, and by default a token has its creator's permissions (22 of 30). The API description defines agentic tokens whose writes return `403 AgenticMutationBlocked` and wait at `/v1/approval_requests` for a person. How to create such a token was not found in the docs index. Dashboard roles are documented on a page we did not read (15 of 20). The API returns customer-supplied names, custom fields and event properties, and no prompt-injection guidance was found (5 of 15). `/v1/auditLogs` records the user or token, resource, action, IP address and user agent (14 of 15). SOC 2 Type 2 and SOC 1 Type 2 badges, regular penetration tests per the security page, and a Vanta trust centre we could not read. security.txt returned 404 and no bounty or disclosure policy for the service was found (12 of 20). 68. - Payments & pricing 39: Payment platforms take the highest step that applies on the 40-point protocol line. No x402, MPP or L402 was found in the API description, the docs index or the pricing page (0). The Startup plan's prices are public at 0.8 per cent of billing volume and $0.04 per 1,000 ingested events. The Custom plan has no price (18 of 20). The pricing page says "Start free" and the quickstart links a self-serve sandbox sign-up, while production checkout needs a credit card. The sign-up page was not read, so whether the sandbox asks for a card is unconfirmed (15 of 20). A person signs up and creates the token in the web app. The changelog of 10 June 2026 says agents can provision an account through the Stripe Projects CLI, which we did not test and which needs a Stripe account (6 of 20). 39. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 82: The changelog's latest entry is dated 29 September 2026, ten days before the check (30). It has 20 dated entries since 14 July 2026 (20). A support portal and a public changelog exist. The SDK issue queues (4 and 13 open items on the Node.js and Python repositories) were not read (9 of 15). Official SDKs in five languages. Python 4.11.1 was tagged on 28 August 2026 and Node.js 3.10.0 on 23 July, and both repositories were pushed to on 6 October (15). The repositories carry CI with lint, build and test jobs, lockfiles and automated releases. CI results were not read (8 of 10). 82. - Transparency & trust 65: The platform is closed. Metronome's legal centre links the Stripe Services Agreement, last modified 28 September 2026, which does not name Metronome. The SDKs are Apache-2.0 (15 of 30). Stripe's privacy policy of 28 April 2026 and the DPA the agreement incorporates cover data handling. The agreement says Stripe need not retain data after the term and grants Stripe a licence to use customer content to develop and improve its services. No Metronome retention period was found beyond 30 days of webhook delivery history (15 of 30). No deprecation policy was found. One operation is marked deprecated, v1 contract reads point new clients to v2, and SDK releases of 16 January and 2 March 2026 removed fields with changelog entries on the day (7 of 20). Stripe's privacy pages link a sub-processors list we did not read, and Metronome's trust centre is script-drawn. No hosting region was found (8 of 20). 45. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (21 items): https://www.anchorterminal.com/fixes/metronome.md (JSON https://www.anchorterminal.com/fixes/metronome.json) ### What we couldn't check - The Stripe Services Agreement governs per Metronome's legal centre but never names Metronome. Whether service-specific terms or an order form add Metronome clauses was not established. - unchecked: trust.metronome.com is a script-drawn Vanta page, so sub-processors, policies and the full list of certifications were not read. - unchecked: signup.metronome.com was not read, so whether a sandbox account asks for a card is unconfirmed. - unchecked: the Stripe Projects CLI route for agents is the changelog's claim of 10 June 2026 and was not tested. No vendor software was run. - unchecked: how an agentic token is created. The approval operations are in the OpenAPI description and no guide page was found in llms.txt. - unchecked: the status feed gives no durations. Three incident pages were read, the other ten incidents were scored from their titles. - unchecked: the MCP registry did not answer a search for metronome. No MCP server was found in the docs index or the Node.js SDK repository. - unchecked: the RBAC, SSO and webhooks guides, Stripe's DPA and sub-processors list, and the SDK issue queues. - The 2 March 2026 SDK release removed the contract `priority` field in a minor version. Whether customers had notice before that day was not established, so no deduction was taken. - The docs tell Python users to run `pip install --pre metronome-sdk` although the repository's latest tag is 4.11.1, a stable version. - The lead named the docs' LLM token billing as a Stripe listing feature. Metronome has its own domain, API, SDKs, prices and status page, so it is graded apart. ### Sources - home page, with the notice that Metronome is part of Stripe: (seen 2026-10-09) - pricing page: (seen 2026-10-09) - legal centre, linking Stripe's agreement and privacy policy: (seen 2026-10-09) - security page: (seen 2026-10-09) - post on the completed acquisition by Stripe: (seen 2026-10-09) - docs index for agents: (seen 2026-10-09) - OpenAPI description, read as a file and counted by script: (seen 2026-10-09) - authentication and token scoping: (seen 2026-10-09) - rate limits and platform limits: (seen 2026-10-09) - idempotency: (seen 2026-10-09) - pagination: (seen 2026-10-09) - status codes and the rate-limit header: (seen 2026-10-09) - audit logs: (seen 2026-10-09) - security principles: (seen 2026-10-09) - Metronome's own pricing model for order forms: (seen 2026-10-09) - API quickstart, sandbox sign-up link and first request: (seen 2026-10-09) - SDK guide: (seen 2026-10-09) - changelog: (seen 2026-10-09) - status page: (seen 2026-10-09) - status feed the page links: (seen 2026-10-09) - incident of 3 September 2026: (seen 2026-10-09) - incident of 11 September 2026: (seen 2026-10-09) - incident of 8 October 2026: (seen 2026-10-09) - Stripe Services Agreement, United Kingdom edition after redirect: (seen 2026-10-09) - Stripe privacy policy: (seen 2026-10-09) - Node.js SDK repository, shallow clone for tags, README, CI and SECURITY.md: (seen 2026-10-09) - Python SDK repository, shallow clone for tags and changelog: (seen 2026-10-09) - npm weekly downloads for @metronome/sdk: (seen 2026-10-09) - RDAP record for metronome.com: (seen 2026-10-09) ## Who's behind it (provenance 85/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Stripe, LLC | 20/20 | | Domain age | metronome.com, registered 1998-11-04 (27 years) | 15/15 | | Endpoint on the vendor's domain | api.metronome.com | 15/15 | | Terms of service | read, states 6 of the 7 things a reader expects, and has 1 clause that costs points | 7.1/10 | | Privacy policy | read, states 8 of the 8 things a reader expects, and has 1 clause that costs points | 8/10 | | Status page | status.metronome.com | 10/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | Metronome's site says it is now part of Stripe. Its legal centre links two documents, Stripe's Services Agreement as terms of service and Stripe's privacy policy. The Stripe Services Agreement (General Terms last modified 28 September 2026) names Stripe, LLC as the contracting entity for the United States, with other Stripe entities by country. It does not mention Metronome by name. Our request was redirected to the United Kingdom edition of the page. The Stripe privacy policy was last updated on 28 April 2026 and covers services supplied under the Stripe Services Agreement. It does not mention Metronome by name. The API answers at https://api.metronome.com per the OpenAPI description's server entry. https://metronome.com/.well-known/security.txt returned 404. The SDK repositories' SECURITY.md gives dev-feedback@metronome.com for service security questions. RDAP for metronome.com gives a registration date of 1998-11-04, which predates the company. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://stripe.com/legal/ssa), read 2026-10-08, dated 2026-09-28, states 6 of the 7 things a reader expects. - To know. Says the terms or the service can change without notice (costs points). "Stripe may modify this Agreement (or any portion of it) at any time by posting a revised version of the modified portion(s) on the Stripe Legal Page or by notifying User." - To know. Says access can be ended without notice or for any reason. "Termination for Convenience. Unless otherwise agreed in writing, Stripe may terminate this Agreement or close User’s Stripe Account at any time." - To know. Requires arbitration or waives class actions. "Disputes between User and Stripe are subject to a class action waiver and will be resolved by individual binding arbitration, except as stated otherwise in this Agreement." - Gives the date it was last updated. Last updated 2026-09-28. - Names the governing law or courts. The law of the State of California. - States a limit on its liability. Capped at the lesser of USD $1,000 and the fees paid in the 12 months before the claim. - Says how changes to the terms are announced. Gives 30 days of notice before a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). A user who uses an AI agent to access the services is solely responsible for each action initiated by or through the agent. "If User uses an AI Agent to access the Stripe Services, User is solely responsible for each action initiated by or through the AI Agent." - Also in the text (2026-10-08). The user grants Stripe a perpetual, irrevocable licence to use its content to develop, improve and run the services and for Stripe's internal business purposes. "User grants to Stripe, on behalf of itself and its Affiliates, a perpetual, worldwide, non-exclusive, irrevocable, royalty-free license to use the Content to develop, improve, and provide Services and Stripe Technology and for Stripe’s internal business purposes." - Also in the text (2026-10-08). Data returned by the services may be used only for the user's own internal business purposes and its intended purpose as described in the service terms or documentation. "User’s use of Stripe Output Data is limited to User’s own internal business purposes and for its intended purpose as may be described in the applicable Service Terms or Documentation." **Privacy policy** (https://stripe.com/privacy), read 2026-10-08, dated 2026-04-28, states 8 of the 8 things a reader expects. - To know. Says it may use customer content to train or improve models, and no opt-out was found (costs points). "Training artificial intelligence models to power our Services and protect against fraud and other harm." - To know. Says it sells personal data or shares it for advertising. "Because these third parties may use the data Stripe provides for their own purposes, Stripe's provision of data to these parties may be considered a data “sale” or “sharing” (for behavioral advertising) as those terms are defined under the CCPA and other applicable US privacy laws." - Gives the date it was last updated. Last updated 2026-04-28. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. dpo@stripe.com. - Says where data is transferred or stored. Relies on standard contractual clauses. ## Live (updated 2026-10-10 05:38 UTC) - Right now: up, HTTP 404, 424 ms, checked 2026-10-10 05:38 UTC (get on `https://api.metronome.com`) - Uptime 24h 100.0% (143 probes) · 30 days 100.0% (143 probes) · p50 427 ms · p95 497 ms - Vendor status page: none, All Systems Operational - github `Metronome-Industries/metronome-node` v3.10.0, released 2026-07-23 - npm `@metronome/sdk` 3.10.0 - pypi `metronome-sdk` 4.11.1, released 2026-08-28 - Watching changelog - Watching pricing - Watching privacy , last changed 2026-10-08 18:24 UTC - Watching terms , last changed 2026-10-08 18:24 UTC - Always current: https://www.anchorterminal.com/api/v1/live/metronome.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Startup plan fee on billing volume | 0.8% | percentage fee | plus the event fee. Custom plan priced by sales | | Ingested usage event on the Startup plan | $0. | per transaction | $0.04 per 1,000 ingest events | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Public OpenAPI 3.0.1 description with 142 operations and 509 schemas, plus llms.txt and a Markdown twin of each docs page - `Idempotency-Key` accepted on every POST for at least 24 hours, `uniqueness_key` on contracts and alerts, and event `transaction_id` deduplication for 34 days - Agentic tokens get `403 AgenticMutationBlocked` on writes and queue them at `/v1/approval_requests` for a person to approve or deny - Audit log readable at `/v1/auditLogs`, naming the user or API token, the resource, the action, the IP address and the user agent - Startup plan prices are public (0.8 per cent of billing volume and $0.04 per 1,000 ingested events), with a self-serve sandbox sign-up ## Weaknesses - Errors are a single `message` string with no machine-readable code, and the API description documents a 4xx response on 87 of 142 operations - Token scoping by access level, environment or endpoint is set by contacting support. By default a token has its creator's permissions - The status feed lists 13 incidents between 22 July and 8 October 2026, among them two hours of elevated API and ingest errors on 3 September - No SLA document is published. The pricing page names enhanced SLAs on the Custom plan only - The governing terms are Stripe's Services Agreement, which does not name Metronome and grants Stripe a licence to use customer content to develop and improve its services - No deprecation policy was found. SDK releases of 16 January and 2 March 2026 removed fields, announced in the changelog on the day ## Before you call it (notes for agents) 1. Send an `Idempotency-Key` header on every POST and reuse it on retry. A cached error is returned for the same key, so use a new key after fixing the cause 2. Give each usage event a stable `transaction_id`. Metronome ignores repeats for 34 days and accepts at most 100 events per `/v1/ingest` call 3. On 429 read `X-Metronome-Rate-Limit-Type` (`client` or `customer`) and back off. Unlisted endpoints default to 8 requests a second 4. With an agentic token, expect `403 AgenticMutationBlocked` on writes. Post the original method, path and body to `/v1/approval_requests` and show the person the `approval_url` 5. Use a sandbox token for testing. The token alone decides whether a call reaches sandbox or production data ## Connect Install: ```bash npm install @metronome/sdk ``` First request: ```bash curl -X POST https://api.metronome.com/v1/billable-metrics/create \ -H "Authorization: Bearer $METRONOME_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "name": "API Calls", "aggregation_type": "count", "event_type_filter": { "in_values": ["api_call"] } }' ``` Through letme (picks today, calling later): https://letme.dev/metronome. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Stripe API + MCP | A | 82.4 | 5 | payments.metering | no | https://www.anchorterminal.com/tools/stripe-mcp.md | | Tempo | BB | 76.6 | 27 | payments.metering | no | https://www.anchorterminal.com/tools/tempo.md | | Apideck Accounting API + MCP | BB | 72.9 | 96 | accounting.invoices | no | https://www.anchorterminal.com/tools/apideck-accounting.md | | Nevermined API + MCP | BB | 70.8 | 142 | payments.metering | no | https://www.anchorterminal.com/tools/nevermined.md | | Merge Accounting API | BB | 70 | 164 | accounting.invoices | no | https://www.anchorterminal.com/tools/merge-accounting.md | | Xero API + MCP | B | 67.2 | 258 | accounting.invoices | no | https://www.anchorterminal.com/tools/xero.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Metronome's legal centre links Stripe's Services Agreement as its terms of service and Stripe's privacy policy as its privacy policy (source: ) - The API description carries five approval-request operations for agentic tokens, whose writes return `403 AgenticMutationBlocked` until a person approves them (source: ) - Default rate limits are published per tier, from 2,750 requests a second overall and 1,100 on `/v1/ingest` down to 8 on unlisted endpoints (source: ) - The changelog of 10 June 2026 says agents can provision a Metronome account and sandbox through the Stripe Projects CLI, and that of 15 June 2026 announces self-serve checkout to production with a credit card (source: ) - Billing for LLM tokens entered public preview on 3 September 2026, with rates sourced from Stripe's `/v1/models` API (source: ) - The status page runs on incident.io with seven components. Its feed lists 13 incidents and three maintenance windows between 22 July and 8 October 2026 (source: ) - #4 of 14 in Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md - All 76 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/index.md ## Compare - [ATXP vs Metronome](https://www.anchorterminal.com/compare/atxp-vs-metronome.md): E 42.9 vs B 69.7 - [Lago vs Metronome](https://www.anchorterminal.com/compare/lago-vs-metronome.md): B 65.7 vs B 69.7 - [Metronome vs Nevermined API + MCP](https://www.anchorterminal.com/compare/metronome-vs-nevermined.md): B 69.7 vs BB 70.8 - [Metronome vs Orb](https://www.anchorterminal.com/compare/metronome-vs-orb.md): B 69.7 vs B 66.5 - [Metronome vs Paid](https://www.anchorterminal.com/compare/metronome-vs-paid.md): B 69.7 vs C 55.1 - [Metronome vs Stripe API + MCP](https://www.anchorterminal.com/compare/metronome-vs-stripe-mcp.md): B 69.7 vs A 82.4 - [Metronome vs Tempo](https://www.anchorterminal.com/compare/metronome-vs-tempo.md): B 69.7 vs BB 76.6 - [Metronome vs PayPal MCP server](https://www.anchorterminal.com/compare/metronome-vs-paypal-mcp-server.md): B 69.7 vs C 56.3 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on metronome.com or one of its subdomains, or the README of github.com/Metronome-Industries/metronome-node. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "metronome", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Metronome on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Metronome on Anchor Terminal](https://www.anchorterminal.com/badges/metronome.svg)](https://www.anchorterminal.com/tools/metronome) ``` Plain link: ```html Metronome on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Metronome is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/metronome-dark.png - Light: https://www.anchorterminal.com/assets/share/metronome-light.png