API Meter

create_account and get_ingest_snippet are clearly distinct, and get_usage vs export_usage are differentiated by intent (interactive grouped query vs billing-ready rows/CSV). However, both usage tools return monthly usage data, so an agent may occasionally hesitate over which to pick.

All four tools follow a strict verb_noun snake_case pattern (create_account, export_usage, get_ingest_snippet, get_usage). The convention is fully predictable with no deviations.

Four tools map cleanly to the core flow (sign up, set up ingestion, query usage, export billing data), and each earns its place. It sits at the thin edge of the ideal range, but nothing is redundant.

The core lifecycle (account creation, ingestion, usage query, export) is covered, but keys are shown once with no rotation/regeneration tool, and there is no listing, updating, or deleting of accounts/APIs. These are notable gaps that could strand an agent that loses the slug or ingest key.