Metronome

PASS consensus from 2 PASS, 1 PARTIAL.

The quickstart joins token creation to /v1/ingest, but its March 2026 timestamps exceed the documented 34-day window on the test date. The guides API quickstart carries the token prerequisite, the sandbox signup link, a runnable curl against https://api.metronome.com/v1/ingest with the Bearer header, and a Step 7 block that explains what a 200 means and how to verify the event in the dashboard. The quickstart links to the send-usage-events guide which documents the /ingest endpoint structure, and the SDK README provides the ingest call code.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The limits page gives the 2,750 global cap and per-environment platform defaults, while two ingest pages claim 100,000 and 110,000 events per second. The Limits page states the global cap of 2,750 req/sec, an ingest tier of 1,100 req/sec, and ten per-object platform limits in one table, but three other pages give ingest ceilings and defaults that do not reconcile with it: 110,000 events/sec with a 5,000 events/sec default on the scale guide, and 100,000 events/sec on the ingest reference. Values are stated in one authoritative page with tiered API rate limits and a separate platform-limits table. No contradictions found across pages.

PASS consensus from 3 PASS.

The status and ingestion pages identify client versus customer scope, then prescribe delayed retries with exponential backoff. The status codes page names the cause, documents the X-Metronome-Rate-Limit-Type header with its client and customer values, and the send usage events guide adds exponential backoff plus the assurance that transaction_id makes retries safe. The docs name the cause, recommend backoff with exponential retry, and the Python SDK auto-retries 429 errors by default.

PASS consensus from 2 PASS, 1 PARTIAL.

The page documents HTTPS receipt and HMAC-SHA256 verification, but only its Slack subsection states the destination-creation steps. The page covers destination setup, payload shapes per webhook type, source IPs, deduplication, the five-minute staleness rule, the bytes-not-parsed-JSON warning, and a worked example whose published signature I recomputed to a byte-exact match; the bash snippet is the one weak spot, since echo -n does not expand \n without -e. End-to-end process documented: webhook destination setup, event receipt, acknowledgment, signature verification with HMAC-SHA256, and code examples in bash, JavaScript, and Go.

PARTIAL consensus from 1 PASS, 2 PARTIAL.

The SDK install and ingest example are clear, but its numeric tokens property conflicts with the usage guide’s string-only rule. The SDK page gives pip install --pre metronome-sdk, the from metronome import Metronome constructor, and a client.v1.usage.ingest example, but that example sends "tokens": 1000000 as an integer while the usage events guide instructs that all property values be strings, so the canonical example contradicts the canonical rule. Minimal working example matches the API form shown on the docs (POST /v1/ingest with the same event schema).