Casa Intelligence Casa Daily — Spatial API

The Casa Daily — Spatial API from Casa Intelligence — 1 operation(s) for casa daily — spatial.

Operations 1

GET /api/v1/cd-spatial/nearby-parcels Nearby Parcels #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/casaintelligence-com-au:casaintelligence-com-au-casa-daily-spatial-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

casaintelligence-com-au-casa-daily-spatial-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Casa Intelligence Engine Casa Daily — Spatial API
  description: Proprietary data ingestion, analysis, and prediction engine for Queensland property development intelligence.
  version: 2.0.0
tags:
- name: Casa Daily — Spatial
paths:
  /api/v1/cd-spatial/nearby-parcels:
    get:
      tags:
      - Casa Daily — Spatial
      summary: Nearby Parcels
      description: 'Cadastral parcels intersecting a bbox of `distance` m around (lat, lng).


        Sourced live from the QLD DCDB ArcGIS service. Use this when the

        in-DB ST_DWithin RPC returns empty for a property whose neighbours

        weren''t ingested yet (regional/rural addresses primarily).


        Two input modes:

        1. Pass `lat` + `lng` directly (callers that already have them).

        2. Pass `property_id` (UUID) and the endpoint looks up the

        centroid from ci_properties.centroid via ST_Y/ST_X. Saves the

        caller one DB round-trip; this is what casa-daily uses.


        On upstream timeout or error returns HTTP 503 — callers should treat

        that as "click-to-amalgamate unavailable for this lookup" and render

        the rest of the map normally.'
      operationId: nearby_parcels_api_v1_cd_spatial_nearby_parcels_get
      security:
      - APIKeyHeader: []
      parameters:
      - name: lat
        in: query
        required: false
        schema:
          anyOf:
          - type: number
            maximum: 90
            minimum: -90
          - type: 'null'
          description: Centre latitude (WGS84). Required unless property_id is given.
          title: Lat
        description: Centre latitude (WGS84). Required unless property_id is given.
      - name: lng
        in: query
        required: false
        schema:
          anyOf:
          - type: number
            maximum: 180
            minimum: -180
          - type: 'null'
          description: Centre longitude (WGS84). Required unless property_id is given.
          title: Lng
        description: Centre longitude (WGS84). Required unless property_id is given.
      - name: property_id
        in: query
        required: false
        schema:
          anyOf:
          - type: string
          - type: 'null'
          description: ci_properties.id (UUID). When given, the endpoint looks up the property's centroid and uses it as (lat,lng), so callers don't need to do a separate centroid query first.
          title: Property Id
        description: ci_properties.id (UUID). When given, the endpoint looks up the property's centroid and uses it as (lat,lng), so callers don't need to do a separate centroid query first.
      - name: distance
        in: query
        required: false
        schema:
          type: number
          maximum: 500
          minimum: 10
          description: Radius in metres; clamped 10-500.
          default: 150.0
          title: Distance
        description: Radius in metres; clamped 10-500.
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/NearbyParcelsResponse'
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    NearbyParcelsResponse:
      properties:
        type:
          type: string
          title: Type
          default: FeatureCollection
        features:
          items:
            $ref: '#/components/schemas/NearbyParcelFeature'
          type: array
          title: Features
      type: object
      required:
      - features
      title: NearbyParcelsResponse
      description: GeoJSON FeatureCollection, ready to feed straight into MapLibre.
    NearbyParcelFeature:
      properties:
        type:
          type: string
          title: Type
          default: Feature
        id:
          anyOf:
          - type: string
          - type: 'null'
          title: Id
        geometry:
          anyOf:
          - additionalProperties: true
            type: object
          - type: 'null'
          title: Geometry
        properties:
          additionalProperties: true
          type: object
          title: Properties
      type: object
      title: NearbyParcelFeature
      description: 'GeoJSON Feature with cadastral properties.


        Geometry is a Polygon (or null if ArcGIS returned no rings — those

        rows are filtered out before this model is constructed, so callers

        can assume geometry is present).'
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer
    APIKeyHeader:
      type: apiKey
      in: header
      name: X-API-Key