Flood Intelligence docs

Make the first request.

curl -G 'https://daleads.com.au/api/v1/property?address=4%20Golf%20Links%20Road%20Rocklea%20QLD&components=scores.flood,hazards.flood' \
  -H 'Authorization: Bearer dk_your_key'

No key yet? Open the committed keyless sample.

Read the result and its evidence together.

{
  "scores": {
    "flood": {
      "score": 7,
      "label": "Very High Risk",
      "flood_depth": {
        "depth_m": 0.72,
        "aep": "1% AEP",
        "source": "Oxley Creek Flood Study"
      }
    }
  },
  "meta": {
    "coverage_note": "Missing flood_depth does not mean zero depth."
  }
}

Requested components: scores.flood, hazards.flood. Runtime responses also carry completeness, coverage status, model/source version and attribution for the fields actually delivered.

Do not turn missing evidence into a clean result.

The authenticated Property OpenAPI reference contains the complete field contract and response-specific attribution. Internal provider endpoints and model recipes are not part of the public guide.

1,000 unique addresses per calendar month.

The meter is address-based. Repeating the same resolved property during the same period does not consume another unit. Read usage.billing_period_key, usage.period_quota and usage.resets_at from the response.

Sample before calling.

uvx daleads-mcp

property_sample()
property_sandbox_addresses()
property_intelligence(address="…", components="scores.flood, hazards.flood")

Errors remain actionable.