Coverage

Coverage is published by the API itself so integrations do not depend on a hard-coded state list. Call the coverage endpoint when you enable a workspace and refresh it periodically as supported content expands.

Read current state coverage

curl https://prophit.ai/api/v1/coverage/states \
  -H "Authorization: Bearer itms_test_YOUR_SANDBOX_KEY"

GET /api/v1/coverage/states returns all 50 states and the District of Columbia, the key's environment, a generation timestamp, summary counts, and one coverage record per jurisdiction.

Coverage modes

ModeIntegration meaning
deterministic_dynamicJurisdiction-aware deterministic calculation content is available for supported request facts.
legacy_snapshotDeterministic baseline coverage is available. Read each calculation's authority, precision, and fallback metadata.
no_statewide_sales_taxNo statewide sales tax is imposed. Do not interpret this label as a statement that every local obligation is zero.

Calculation authority

State coverage is a discovery signal; the individual calculation response is authoritative for that request. Use metadata.calculation_authority, metadata.experimental, precision, fallback fields, warnings, and per-line status when deciding whether to accept a result.

  • deterministic results may be used in the workflows documented for the endpoint.
  • experimental results are non-authoritative sandbox research estimates and cannot be committed or used for returns.
  • accuracy_policy=deterministic_only fails closed instead of accepting a degraded result.
  • minimum_address_precision lets the caller require an explicit jurisdiction precision.

Recommended integration behavior

  1. Read /api/v1/config and /api/v1/coverage/states during integration setup.
  2. Configure nexus before creating committed transactions; configured nexus is the default.
  3. Send a known tax code or item mapping when available. Otherwise provide a clear line description so the governed product-identity pipeline can classify the item, and inspect lines[].product_metadatafor the decision and fallback tier.
  4. Persist request IDs, warnings, authority metadata, and transaction codes for support and audit.

See Schemas for the response fields used to evaluate each result.