Construction data API and integration documentation

Start with a real Florida project

The deterministic intelligence engine identifies a likely jurisdiction, relevant permit steps, required-document categories, cited sources, confidence signals, and mandatory human-review boundaries.

curl -X POST https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/reports \
  -H "Content-Type: application/json" \
  -d '{"address":"LaBelle, Hendry County, FL","projectType":"Demolition","scope":"Remove a detached structure"}'

Discover live capabilities, registered sources, payment availability, and the published API contract:

curl https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/models
curl https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/sources
curl https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/datasets
curl https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/records
curl https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/ingestion/status
curl https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/reliability
curl https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/payments/status
curl https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/openapi

REST API and route catalog

All routes share the same deployment origin. Public discovery endpoints expose operational evidence; protected or paid operations fail explicitly instead of fabricating results.

MCP: connect construction tools to AI assistants

The public /mcp endpoint accepts MCP JSON-RPC over Streamable HTTP. Free discovery and routing tools expose Florida source information; paid tool execution must honor the same x402 payment and settlement requirements as HTTP requests. Tool availability is discoverable through tools/list.

curl -X POST https://florida-build-intelligence.ubuenv.chatgpt.site/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Claude Code

claude mcp add --transport http florida-build https://florida-build-intelligence.ubuenv.chatgpt.site/mcp

Codex MCP configuration

[mcp_servers.florida_build]
url = "https://florida-build-intelligence.ubuenv.chatgpt.site/mcp"

Compatible MCP client configuration

{
  "mcpServers": {
    "florida-build": {
      "url": "https://florida-build-intelligence.ubuenv.chatgpt.site/mcp"
    }
  }
}

For ChatGPT, Claude Desktop, Gemini, or another host, register the remote endpoint using that host's current connector or MCP-server settings. Marketplace approval and host-specific authentication remain separate from protocol compatibility.

A2A: construction intelligence for agent-to-agent workflows

Agent peers discover capabilities at /.well-known/agent-card.json, then send JSON-RPC requests to /a2a. Include a structured data part containing address, projectType, and scope; unstructured requests cannot safely establish the project or authorize a charge. Payment-gated tasks only complete after the same x402 verification and settlement controls used by the paid API.

curl https://florida-build-intelligence.ubuenv.chatgpt.site/.well-known/agent-card.json

curl -X POST https://florida-build-intelligence.ubuenv.chatgpt.site/a2a \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":"request-1","method":"message/send","params":{"message":{"role":"user","parts":[{"kind":"data","data":{"address":"LaBelle, Hendry County, FL","projectType":"Demolition","scope":"Remove a detached structure"}}],"messageId":"message-1"}}}'

x402 payment-enabled API requests

Use POST /api/v1/x402/report for pay-per-result integration. The server first verifies that payments are enabled, a receiving wallet is configured, a durable payment ledger is available, and a facilitator supports the selected network. An unpaid request then receives a standards-based HTTP 402 Payment Required challenge. A compatible buyer retries with its payment proof; verified, settled requests receive the report.

curl -i -X POST https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/x402/report \
  -H "Content-Type: application/json" \
  -d '{"address":"LaBelle, Hendry County, FL","projectType":"Demolition","scope":"Remove a detached structure"}'

# 503 = settlement is not configured
# 402 = read the payment challenge and authorize payment
# 200 = verified and settled payment; construction report returned

Use PAYMENT-REQUIRED, PAYMENT-SIGNATURE, and PAYMENT-RESPONSE for the x402 v2 challenge, signed payment, and settlement receipt. Idempotency-Key and authorization nonces prevent duplicate settlement attempts. Base Sepolia uses eip155:84532; Base mainnet uses eip155:8453 and requires a production-capable facilitator.

Check GET /api/v1/payments/status before enabling paid user journeys. Settlement production readiness depends on your real recipient wallet, selected network, facilitator, and deployment secrets.

SDK and automation integration patterns

Any JavaScript, TypeScript, Python, SaaS automation, webhook worker, or internal construction tool can consume the same JSON contract. Use an x402-compatible client for paid routes; keep signing keys and provider credentials outside the browser.

JavaScript / TypeScript

const response = await fetch("https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/reports", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    address: "LaBelle, Hendry County, FL",
    projectType: "Demolition",
    scope: "Remove a detached structure",
  }),
});

if (!response.ok) throw new Error(`Construction API: ${response.status}`);
const report = await response.json();

Python

import requests

response = requests.post(
    "https://florida-build-intelligence.ubuenv.chatgpt.site/api/v1/reports",
    json={
        "address": "LaBelle, Hendry County, FL",
        "projectType": "Demolition",
        "scope": "Remove a detached structure",
    },
    timeout=30,
)
response.raise_for_status()
report = response.json()

The published OpenAPI contract can drive typed clients, workflow automation, and low-code integration.

Optional AI provider enrichment

Official-source discovery, local rules, and route selection do not require a model provider. When protected provider secrets are configured, the OpenAI-shaped compatibility route can add server-side synthesis without returning your API keys to clients.

Reliability, payment security, and action boundaries

Guides, operations, and marketplace readiness

Specialist-agent network · Public data catalog · Knowledge base · Source status · County intelligence · Protected operator console

Privacy policy · Terms of service · Support

A public MCP endpoint is an integration prerequisite, not automatic marketplace approval. OpenAI and Anthropic distribution still depend on each platform's current review, identity, policy, and submission requirements.