Account capabilities
GET /api/v1/capabilities / MCP get_account_capabilities.
Requires account:read. No arguments.
| Result field | Meaning |
|---|---|
account |
Bound account id and name |
check_kinds |
Supported check-kind strings |
fields_by_kind |
Supported kind-specific JSON schema properties |
scopes |
Grant scopes that current role/validity still permits |
limits |
Current plan keys such as check limit, minimum interval and included probe locations |
usage.checks |
Current account check count |
effective_min_interval_seconds |
Effective floor for active probes, including fallback |
renewal_interval_seconds |
Fixed domain/certificate lookup interval |
billing.account |
Account identity to select for an upgrade |
billing.payments_enabled |
Whether self-service payments are enabled |
billing.can_manage_billing |
Whether this connection’s user can manage billing |
billing.upgrade_url |
Available upgrade URL, or null |
Limits can be absent or null; do not interpret absence as zero. The effective minimum is the appropriate cadence floor even when a raw plan key is absent. Usage is a snapshot, not a concurrency-safe quota reservation.
This result guides automation; it does not disclose recipient details or
authorize a purchase. If a quota is reached, report the failure and use
the returned billing guidance. Ask a billing-authorized member when
can_manage_billing is false.
Read check fields for required inputs in addition to the kind-specific properties returned here.