Inspect the current public data boundary and understand where authenticated Product contracts stop. No customer API package, credential, or data-feed right is implied.
The public coverage contract is available without a customer credential. Authenticated filing, metadata, watchlist, alert, export, and access contracts serve only their existing Product surfaces and permission boundaries.
The current catalog defines programmatic API access but offers it through no launch tier. External API credentials, customer developer documentation, service commitments, redistribution rights, and commercial data-feed terms are not available.
A team evaluating an integration needs to separate an inspectable public contract from authenticated application APIs and from a customer API product that is not sold today.
Use the public coverage response to review its returned definition, scope axes, source, as-of time, staleness policy, and exceptions. Treat all other application contracts as surface-specific unless RateFileAI explicitly grants customer programmatic access.
The output is a clear available-or-unavailable disposition with a next step. It is not an API key, schema catalog, uptime promise, bulk filing feed, or license to redistribute data.
The page points to live contracts and current Product authority; it does not invent payloads or access.
The response itself supplies its contract version, definition, source, scope axes, as-of and generated times, staleness policy, exceptions, and measured summary. Missing fields remain missing rather than becoming zero or “complete.”
A data lead can open the coverage contract, confirm whether the returned jurisdictions, lines, filing types, timing, and exceptions fit a proposed workflow, then review the published methodology. If that evidence is insufficient, the correct result is “not established,” followed by a demo request—not an inferred feed or credential.
Every contract must keep source, scope, freshness, authorization, and commercial rights distinct.
No launch tier currently offers customer programmatic API access. Existing signed-in Product routes continue to use their own authenticated contracts; this public page does not broaden them.
Source facts can be normalized or calculated, model output remains labeled, inference stays distinct, and a person’s conclusion remains attributable to that person.
Observed public record.
Mapped with its source retained.
Derived on a named basis.
Classification, not observation.
Hypothesis, not filing intent.
Human-authored judgment.