---
title: "Audit planet clearance from house cusps across every 12-house system"
method: POST
path: "/api/astro/house-boundary-proximity"
tags: ["Calculations"]
---

# Audit planet clearance from house cusps across every 12-house system

`POST /api/astro/house-boundary-proximity`

## Request

- Base URL: `https://api.cosmicephemeris.com`
- URL: `https://api.cosmicephemeris.com/api/astro/house-boundary-proximity`
- Auth: one of:
  - HTTP bearer
  - API key in header `x-api-key`

Calculates one exact chart and measures 1–10 selected planets against every available 12-house system in Cosmic Ephemeris's fixed inventory. Each system row returns the assigned house, preceding and following cusp, two-sided angular distance, normalized within-house position, nearest-cusp ties, and an inclusive caller-declared threshold flag. Undefined geometries remain explicit unavailable rows; Gauquelin's 36 sectors are excluded and no fallback or system substitution occurs. The result does not reinterpret or reassign cusp-near planets and makes no recommendation, interpretation, prediction, or practitioner-preference claim. One standard quota unit per admitted request; failed or timed-out admitted attempts are not refunded. Do not automatically retry.
Historical mode uses an explicit BCE/CE date object and UT1 conventions. Its response is the versioned historical envelope, not the modern UTC envelope. Read result for calculation fields and metadata for limits and uncertainty.

## Headers

- `X-Cosmic-Ephemeris-Receipt` 'v1'

## Request body

- union
  - HouseBoundaryProximityRequest
    - `birth` HouseSystemReadinessBirth, required
      - `date` string, date, required: Valid Gregorian YYYY-MM-DD local civil date, inclusive 1800-01-01 through 2200-12-31. Calendar validity and timezone conversion are checked by the server.
      - `time` string, required: HH:MM or HH:MM:SS; no offset in this field. Use timezone to select the civil-time zone.
      - `timezone` string, required
      - `lat` number, required
      - `lon` number, required
    - `profile` union, required
      - object
        - `zodiac` 'tropical', required
      - object
        - `zodiac` 'sidereal', required
        - `ayanamsa` 'lahiri' | 'raman' | 'krishnamurti' | 'fagan_bradley' | 'yukteshwar' | 'sassanian' | 'true_chitra' | 'true_revati' | 'true_pushya' | 'galactic_center_0_sagittarius' | 'galactic_alignment_mardyks', required
    - `points` HouseBoundaryProximityPoint[]
    - `threshold_degrees` number
  - HistoricalHouseBoundaryProximityRequest: Explicit historical mode, 1000 BCE (BC)–2500 CE (AD). No year zero, implicit calendar, UTC or IANA zone. Preserve tool-specific mathematical, geographic and search limits; calendar/time conventions and estimated Delta-T are not certified historical accuracy.
    - `birth` HistoricalBirthInput, required
      - `date` HistoricalDate, required: Explicit civil date, 1000 BCE (BC)–2500 CE (AD); no year zero. Calendar validity is checked by the server. Available only on documented connected historical operations, with explicit UT1/fixed-offset conventions.
        - `year` integer, required
        - `era` 'BCE' | 'CE', required: Display BCE (BC) / CE (AD); API values remain BCE / CE. No year zero.
        - `month` integer, required
        - `day` integer, required
        - `calendar` 'proleptic_gregorian' | 'proleptic_julian', required: Explicit choice; applies the selected calendar rules throughout history without a regional adoption switch.
      - `time` string, required: Explicit HH:MM[:SS]; whole seconds only, no leap seconds. Normalized helper output includes seconds.
      - `timezone` string, required: Explicit UT1 or fixed offset UT1+/-HH:MM[:SS], within 14 hours. Local clock minus offset yields UT1, not UTC. No IANA timezone inference. Original offset spelling is preserved.
      - `lat` number, required
      - `lon` number, required
    - `profile` union, required
      - object
        - `zodiac` 'tropical', required
      - object
        - `zodiac` 'sidereal', required
        - `ayanamsa` 'lahiri' | 'raman' | 'krishnamurti' | 'fagan_bradley' | 'yukteshwar' | 'sassanian' | 'true_chitra' | 'true_revati' | 'true_pushya' | 'galactic_center_0_sagittarius' | 'galactic_alignment_mardyks', required
    - `points` string[]
    - `threshold_degrees` number

## Response `200`

Bounded cross-system house-boundary clearance audit

- union
  - HouseBoundaryProximityResponse
    - `type` 'house_boundary_proximity', required
    - `status` 'current', required
    - `input` object, required
      - `birth` Input, required (unresolved $ref)
      - `profile` Profile, required (unresolved $ref)
      - `points` HouseBoundaryProximityPoint[], required
      - `threshold_degrees` number, required
    - `systems` HouseBoundaryProximitySystem[], required
      - `id` 'equal' | 'whole_sign' | 'placidus' | 'porphyry' | 'meridian' | 'campanus' | 'regiomontanus' | 'alcabitius' | 'koch' | 'morinus' | 'topocentric' | 'sripati' | 'vehlow' | 'horizon' | 'krusinski' | 'sunshine' | 'sunshine_alt' | 'savard' | 'pullen_sd' | 'pullen_sr' | 'carter' | 'apc' | 'equal_mc' | 'natural' | 'gauquelin', required
      - `name` string, required
      - `status` 'available' | 'unavailable' | 'excluded', required
      - `reason_code` 'undefined_for_input_geometry' | 'non_twelve_sector_system', nullable, required
      - `points` HouseBoundaryProximityMeasurement[], nullable, required
        - `name` 'sun' | 'moon' | 'mercury' | 'venus' | 'mars' | 'jupiter' | 'saturn' | 'uranus' | 'neptune' | 'pluto', required
        - `longitude` number, required
        - `house` integer, required
        - `start_cusp_house` integer, required
        - `end_cusp_house` integer, required
        - `start_cusp_longitude` number, required
        - `end_cusp_longitude` number, required
        - `house_span_degrees` number, required
        - `distance_from_start_degrees` number, required
        - `distance_to_end_degrees` number, required
        - `normalized_house_position` number, required
        - `nearest_boundary` 'start' | 'end' | 'tie', required
        - `nearest_cusp_houses` integer[], required
        - `clearance_degrees` number, required
        - `within_threshold` boolean, required
    - `point_summaries` HouseBoundaryProximityPointSummary[], required
      - `name` 'sun' | 'moon' | 'mercury' | 'venus' | 'mars' | 'jupiter' | 'saturn' | 'uranus' | 'neptune' | 'pluto', required
      - `longitude` number, required
      - `available_system_count` integer, required
      - `within_threshold_system_count` integer, required
      - `within_threshold_systems` HouseSystemReadinessSystemId[], required
      - `minimum_clearance_degrees` number, required
      - `minimum_clearance_systems` HouseSystemReadinessSystemId[], required
      - `clear_across_all_available_systems` boolean, required
    - `summary` object, required
      - `inventory_system_count` 25, required
      - `comparable_system_count` integer, required
      - `unavailable_system_count` integer, required
      - `excluded_system_count` 1, required
      - `point_count` integer, required
      - `measurement_count` integer, required
      - `within_threshold_measurement_count` integer, required
    - `fallback` object, required
      - `performed` unknown, required
      - `selected_system` unknown, required
    - `metadata` object, required
      - `model` 'cosmicephemeris-house-boundary-proximity-v1', required
      - `fixed_inventory` unknown, required
      - `unweighted_systems` unknown, required
      - `max_system_evaluations` 24, required
      - `max_measurements` 240, required
      - `threshold_is_caller_declared` unknown, required
      - `threshold_changes_assignment` unknown, required
      - `gauquelin_comparable` unknown, required
      - `recommendations` unknown, required
      - `interpretations` unknown, required
      - `predictions` unknown, required
      - `request_time_network` unknown, required
    - `receipt` CalculationReceipt
      - `schema` 'cosmicephemeris-calculation-receipt-v1', required
      - `kid` string, required
      - `algorithm` 'Ed25519', required
      - `canonicalization` 'cosmicephemeris-canonical-data-v1', required
      - `input_normalization` 'public-request-canonical-data-v1', required
      - `route` string, required
      - `release` string, required
      - `issued_at` string, date-time, required
      - `normalized_input_sha256` string, required
      - `result_sha256` string, required
      - `calculation_profile` object, required
      - `service_dataset_versions` object, required
      - `calculation_fingerprint` string, required
      - `verification_uri` string, required
      - `signature` string, required
  - HistoricalHouseBoundaryProximityHouseBoundaryProximityResponse
    - `schema` 'cosmicephemeris-historical-calculation-v1', required
    - `status` 'historical', required
    - `type` 'house-boundary-proximity', required
    - `input` HistoricalHouseBoundaryProximityRequest, required: Explicit historical mode, 1000 BCE (BC)–2500 CE (AD). No year zero, implicit calendar, UTC or IANA zone. Preserve tool-specific mathematical, geographic and search limits; calendar/time conventions and estimated Delta-T are not certified historical accuracy.
      - `birth` HistoricalBirthInput, required
        - `date` HistoricalDate, required: Explicit civil date, 1000 BCE (BC)–2500 CE (AD); no year zero. Calendar validity is checked by the server. Available only on documented connected historical operations, with explicit UT1/fixed-offset conventions.
          - `year` integer, required
          - `era` 'BCE' | 'CE', required: Display BCE (BC) / CE (AD); API values remain BCE / CE. No year zero.
          - `month` integer, required
          - `day` integer, required
          - `calendar` 'proleptic_gregorian' | 'proleptic_julian', required: Explicit choice; applies the selected calendar rules throughout history without a regional adoption switch.
        - `time` string, required: Explicit HH:MM[:SS]; whole seconds only, no leap seconds. Normalized helper output includes seconds.
        - `timezone` string, required: Explicit UT1 or fixed offset UT1+/-HH:MM[:SS], within 14 hours. Local clock minus offset yields UT1, not UTC. No IANA timezone inference. Original offset spelling is preserved.
        - `lat` number, required
        - `lon` number, required
      - `profile` union, required
        - object
          - `zodiac` 'tropical', required
        - object
          - `zodiac` 'sidereal', required
          - `ayanamsa` 'lahiri' | 'raman' | 'krishnamurti' | 'fagan_bradley' | 'yukteshwar' | 'sassanian' | 'true_chitra' | 'true_revati' | 'true_pushya' | 'galactic_center_0_sagittarius' | 'galactic_alignment_mardyks', required
      - `points` string[]
      - `threshold_degrees` number
    - `result` object, required: Complete historical calculation adapter result. Times are explicit UT1 date records, never UTC strings; derived times may include fractional seconds and years outside the input range.
    - `metadata` object, required
      - `time_standard` 'UT1', required
      - `historical_accuracy_certified` unknown, required
      - `warnings` string[], required

## Other responses

- `400`: Invalid request, malformed JSON, out-of-range date/location, unknown model, invalid timezone or ambiguous/nonexistent clock-change time. Invalid attempts reaching quota reservation consume one unit.
- `401`: Missing, invalid, revoked API key or unavailable activated key owner. Dashboard cookies do not authenticate calculation routes.
- `403`: Origin not allowed by production CORS policy. Server-to-server requests can omit Origin.
- `429`: Monthly quota exhausted, per-user two-request concurrency reached, or nginx rate/connection admission refused. Retry-After: 2 is sent for application per-user concurrency only, not a promise that monthly quota resets in two seconds.
- `502`: Engine unavailable, unsuccessful internal server response or invalid upstream JSON. No engine internals are exposed.
- `503`: Four-request global calculation pool full (Retry-After: 2), maintenance or upstream service unavailable.
- `504`: Application engine timeout: 15 seconds normally; planetary events, house ingresses, aspect windows, event calendar, eclipse geometry, electional search, and event-rule search use 30 seconds; Nakshatra Timeline plus the explicitly enumerated readiness, robustness, location, uncertainty, and electional-audit family use 60 seconds. Timer includes response-body parsing; an admitted timeout consumes quota.

---

[API](https://skmtc.dev/cosmicephemeris/apis/cosmic-ephemeris-calculation-api.md) · [All operations](https://skmtc.dev/cosmicephemeris/apis/cosmic-ephemeris-calculation-api/llms.txt) · [OpenAPI document](https://skmtc.dev/cosmicephemeris/apis/cosmic-ephemeris-calculation-api/revisions/f041e924cea3?raw)
