Public product evidence
Proof, not promises.
Inspect the coverage, live workflow, reproducible sample, source-bound receipts, and failure controls behind CivicDataForge. Internal inventory and ambiguous user counters are intentionally excluded.
Permit coverage
32 U.S. jurisdictions
The STR Permit Registry exposes official short-term-rental permit records through one normalized schema, with source-specific fields and coverage rules retained.
Agent access
10 evidence tools
The stable remote MCP endpoint provides focused property, healthcare, facility, registry, environmental, and routing workflows for compatible AI agents.
Reproducible sample
100 made-up rows
The downloadable sample file is made up, in the same format as real output: the same schema and field names, bound to a SHA-256 you can check without an account. Real output comes from each city’s published registry.
Partner evaluation
10 current records
A dated five-jurisdiction packet exposes normalized evidence, source and retrieval clocks, field-presence states, record hashes, and a packet receipt without publishing the private collection machinery. Addresses and record IDs were redacted on 2026-10-21.
Proof you can reproduce
| Question | Public evidence | What it proves |
|---|---|---|
| Can I see a real run? | Bounded Orlando task | A runnable STR workflow, current input shape, result fields, and official-source links. |
| Can I check one address? | Address evidence API request and the public Actor input schema | The latest build exposes 1–25 address inputs and the complete-scope decision vocabulary. The August 22 owner canary reproduced all three paths against 524 Orlando records; an independent verifier recomputed every bound receipt and the final manifest hash is sha256:6fb4099f387e304dd1f88da7b6b4c114f730d0773f48695043a8d70c04e5c1ac. The canary is testing evidence, not customer evidence. |
| Can I inspect data without an account? | 100-row made-up sample | Published schema and data shape with made-up rows, bound to SHA-256 b602572f3b0511615f91c014af0474fcaff031f6a438f60ae64b121d76c7e0db. |
| Can a partner inspect the current evidence contract? | Ten-record live-source evaluation packet | Five jurisdictions, ten normalized records, source-shape receipts, explicit field states and source clocks. Addresses and record IDs were redacted on 2026-10-21, so the packet hash describes the original run. |
| How are portfolios matched? | Permit Match Audit and its downloadable evidence bundle | Exact-match, review-candidate, invalid-input, and honest no-match classifications with source links and a hash-bound manifest. |
| What happens when a source breaks? | Actor documentation | Complete-monitoring scopes reject caps; count collapse, field loss, and schema drift quarantine an update instead of manufacturing a disappearance. |
| What will a run cost? | Pricing explanation and the live Store listing | Why the public headline can say “from $2.40” while the Free-tier price is $3.00 per 1,000 delivered results. |
Put it to work
Run the public task to inspect the workflow. Bring a property portfolio to match up to 25 addresses in one supported jurisdiction. Then move the proven workflow into usage-priced access or the month-to-month founding monitoring pilot.
Run the public example Match a property portfolio