Product reference

For agents and developers

Use one source-aware service through REST, Markdown, or MCP. Select tools by task, not by a preferred venue or commercial outcome.

Six public tools

  • search_coastal_venues — find candidates matching supplied requirements.
  • get_venue_profile — read one rights-cleared venue profile and field-level context.
  • evaluate_visit_constraints — evaluate scoped rules without claiming inventory.
  • estimate_event_cost — calculate known components and preserve unknown totals.
  • compare_venue_options — compare two to five options using identical requirements.
  • calculate_membership_break_even — apply the simple stable-savings formula.

Do not use these tools to

  • Claim a venue is available or booked without an explicit inventory and acceptance signal.
  • Infer an unknown fee, tax, eligibility condition, rating, or partnership.
  • Treat published hours as space availability.
  • Send a quote request from a public read or tool-discovery call.

Private quote workflow

Preparing a draft persists private data; submitting may cause external delivery. Those operations require user authentication, object ownership, the correct scopes, a valid server-side consent bound to the current draft version, and an approved venue channel. Check the capability inventory because private MCP and external sending can be disabled independently.

REST request example

GET /api/v1/venues?area_id=eastern-suburbs&activity_type=private_event&group_size=20
Accept: application/json

Always inspect the returned restrictions, conditions to confirm, source dates, rights view, and data version. An empty production result is a valid result.