x402 paid API · Base USDC · Texas Gulf Coast MVP

Property due diligence, returned as agent-ready JSON.

Give the API one address. It checks whether the property match is trustworthy, then returns parcel, FEMA flood, flood proximity, taxing entities, school district, permit history, Houston zoning context, risk scoring, quality scoring, recommended next steps, and official source links.

Test the API OpenAPI JSON
$0.001Current paid full endpoint price through x402.
3 countiesHarris, Fort Bend, and Brazoria parcel adapters for MVP property-level matching.
Safe gatesZIP, city, or postal-only matches cannot produce parcel, flood, or risk conclusions.
Agent-readyFull and compact response modes, OpenAPI, quote endpoint, and MCP-style tool descriptor.

Try the live endpoint

x402 is the public paid path. API-key access is optional developer/testing access only. Probe the x402 payment challenge to inspect the paid route metadata. If response mode is omitted, the API returns the full response.

Request controls

x402 challenge probe, optional developer API-key testing, discovery checks, and code examples.

Owner names are suppressed by default. Failed property matches return blockers instead of confident parcel/flood/risk conclusions.

These checks use safe Worker proxy routes and public discovery endpoints. They do not make a paid API call.

Copy a practical starting point. Public paid usage should use x402. API-key examples are intentionally not shown here because keys are only for developer/testing access.

Output

Formatted JSON response, quote, discovery result, or code snippet.

Ready idle
{
  "message": "Choose a test action. The paid endpoint defaults to full response mode when response_mode is omitted."
}

What this API is for

Property Risk Passport API is not a listing site or raw data dump. It is a decision packet for AI agents, homebuyer assistants, insurance workflows, mortgage triage, and investor screening.

1

Confirm the match

The API first decides whether the address and parcel are confirmed well enough for property-level conclusions.

2

Check official layers

It queries parcel/CAD, FEMA NFHL, Census/TIGER, tax, permit, and local context where implemented.

3

Score risk and quality

Risk score and data quality score are separated so low confidence does not masquerade as property risk.

4

Return next steps

The response tells the calling agent what to verify next with source links and limitations.

How to read the response

The safest fields are the ones near the top. Agents should read result status, match status, blockers, scores, and recommended next steps before using parcel or flood details.

result_status

completed, completed_with_warnings, completed_with_blockers, or failed. This tells an agent whether the packet is usable.

match_status

Property match state. If usable_for_decision=false, do not rely on parcel, flood, tax, or risk conclusions.

parcel

Confirmed parcel details when situs/address validation passes. Owner names are suppressed by default.

flood_zone

FEMA NFHL zone interpretation with plain language. Shaded Zone X is treated as a warning, not ignored.

taxing_entities

Actual tax entity/rate data where available. It is separate from Census jurisdiction geography.

quality_breakdown

Explains why the data quality score is high, partial, or blocked across parcel, flood, permits, zoning, and tax data.

Safety rule: when in doubt, the API returns not confirmed instead of a confident wrong answer. ZIP/postal/city-only geocodes cannot produce property-level parcel, flood, or risk conclusions.

API reference

The full endpoint is x402-paid. Free endpoints provide quote, pricing, OpenAPI, coverage, and MCP-style tool metadata for agents.

Paid endpointPOST /v1/property-risk-full
Price$0.001 USDC on Base mainnet through x402.
Request{ "address": "...", "response_mode": "full" }. If mode is omitted, default is full.
Compact modeReturns only status, summaries, top warnings, scores, next steps, and source links.
Free quoteGET /v1/property-risk-full/quote
OpenAPIGET /openapi.json
MCP descriptorGET /mcp/evaluate_property_risk.tool.json
{
  "address": "611 Walker St, Houston, TX 77002",
  "response_mode": "full"
}

Built for agent discovery

The paid route declares Bazaar metadata, exposes quote and schema endpoints, and can be called by x402-enabled agents with no manual subscription flow.

CDP Bazaar

Metadata includes name, category, keywords, input schema, output example, and x402 v2 payment requirements.

Agentic.Market

Agents can inspect purpose, pricing, schema, coverage, and route behavior before deciding to pay.

MCP tool

evaluate_property_risk wraps the paid endpoint with address and optional response mode input.