How plans and limits work
Each account is on one plan: Verify, Monitor or Govern. The plan decides which endpoints the account can use; a request for something the plan does not include is refused with 403 plan_does_not_include and says which plan has it.
Limits on monthly checks, monthly lookups and monitored locations are set per account when we agree them, and GET /v1/usage shows your plan, your limits, what you have used and what remains.
Over a monthly limit, the request that crosses the line completes and the next one gets 429 quota_exceeded with the time the count resets. Accounts without a plan assigned have everything and no limits.
Enforcement and conditions
Not available yet. Today's data covers license status and identity only. Every answer says so
(enforcement_review_state: "not_covered"), because the absence of enforcement data is not evidence that none exists.
We have looked for published, machine-readable enforcement and license-condition data from the Texas, New York and California agencies and have not found any we can use, so this is not on a delivery date.
When enforcement and conditions data is added, it will be a coverage-based module that ships with its coverage schedule
(jurisdictions, agencies, document types, history start dates, refresh targets, known omissions). Allegations will be kept separate from findings,
and stayed or conditional penalties will always be shown with the penalty itself, never held back as an upgrade.