United States
US company evidence is distributed across federal and state systems. There is no single source that answers every identity, legal-status, exclusion, filing, licence, invoice, payee, and payment question. RunOnProof therefore declares US coverage by source, jurisdiction, state, entity type, and claim.
Federal and state layers
Federal sources may support restriction, contracting, securities, spending, tax, or other specialized claims. State sources usually control formation and recorded company status. A federal result does not replace state identity evidence, and a state record does not replace federal restriction checks.
Why state coverage is explicit
States expose different access paths, schemas, identifiers, fees, terms, and freshness. A capability active in one state cannot be assumed active in another. The production catalog must identify which states and claims are supported now.
Typical workflow
- Resolve the company to a legal entity and formation jurisdiction.
- Read supported state status evidence.
- Check required federal evidence for the action.
- Add invoice, payee, licence, or other checks only where coverage exists.
- Apply the named customer policy.
- Return a scoped decision with limitations.
Restriction evidence
Different lists answer different questions. A screening step must name the source families included, match logic, observation time, and handling of possible matches. “No result” in one list is not “clear everywhere.” A source quota or access failure must not become a negative result.
Example: approving a vendor
A Delaware corporation operates in Texas and supplies a customer in California. Formation evidence may come from Delaware, but a policy can also require Texas or California evidence depending on the activity. Federal restriction screening is another layer. RunOnProof should show exactly which layers were checked and which were not; it should not compress them into a universal US approval.
Limited and conditioned coverage
Some US capabilities may be active only for selected states, limited by public-source access, or conditioned on legitimate human registration or API access. A free source can still impose quotas and terms. RunOnProof does not bypass access controls or substitute unofficial evidence to make coverage appear complete.
Safe operational behavior
Use a unique business identifier whenever possible, keep federal and state claims separate, monitor quota and schema health, cache only within declared rules, and preserve REVIEW when a required system is unavailable. Consult the live catalog before presenting any state or federal capability as purchasable.