What the report can do
Resolve a likely jurisdiction and permit path, assemble a preliminary document and inspection checklist, surface product-approval research, and preserve official-source provenance.
KNOWLEDGE BASE // V0.3
Use the intelligence without losing the evidence.
Plain-language guidance for contractors and property teams, plus protocol and operating references for developers and AI agents.
What still needs a person
Permit submission, legal interpretation, engineering design, license conclusions, product suitability, and authority-having-jurisdiction confirmation always remain human-controlled.
How freshness works
When monitoring is configured and a check succeeds, the system records a content fingerprint and check time. A changed source creates a review event and queues affected reports. An uninitialized source is labeled honestly—not presented as already checked.
How confidence works
Confidence reflects jurisdiction resolution, source coverage, freshness, and known review boundaries. It is an operational signal—not a guarantee of approval.
How agents should use results
Agents may research, compare, summarize, and draft. They should preserve citations and stop before filings, purchases, representations, or professional decisions without approval.
How payment works
Free discovery identifies the right data lane. Paid machine results require x402 verification and settlement. When a receiving wallet or facilitator is not configured, the service reports unavailable instead of accepting a fake payment.
How source collection works
An allowlisted source registry identifies official state, county, and water-management authorities. Bounded fetches create historical snapshots; source failures, access gates, and missing baselines remain visible.
How agents connect
MCP-compatible assistants discover and call construction tools. Agent peers use an A2A agent card and JSON-RPC endpoint. REST, OpenAPI, and SDK examples serve software and automation builders.
How opportunity signals work
Relevant planning agendas, procurement portals, permitting systems, enforcement records, and environmental sources can reveal construction opportunities. A listed source is not a promise that gated records were ingested.
How specialist agents grow the system
Bounded research agents receive separate assignments for procurement, public datasets, historical backfills, funding, compliance, payment protocols, and security. Each assignment preserves source restrictions and requires an actual configured scheduler before recurring runs can be claimed.
Current Florida coverage
44 curated source records across statewide authorities and 6 county playbooks: Miami-Dade County, Broward County, Palm Beach County, Hendry County, Lee County, Collier County.
A source appearing in the historical data catalog means its authority and URL have been registered; it does not mean a baseline was fetched, a permit record was retrieved, or a weekly schedule is active. Open source reliability for runtime checks, specialist-agent assignments for bounded research lanes, or county intelligence for local guidance.
Payment and deployment status
Check the public payment and wallet status before building a paid flow. A 503 means settlement is unavailable; 402 means a configured deployment is requesting payment; 200 after payment means the protected result was returned.
Software and agent integrations
Review the complete developer documentation, specialist-agent assignments, official government source catalog, and current collection and payment readiness.
Contractors and project teams
Start with the project form, review the cited sources, and save important territories or projects in your workspace.
Analyze a Florida projectSoftware and AI teams
Use REST, MCP, A2A, the OpenAI-shaped subset, or x402 paid execution from one documented engine.
Read developer documentation