HaldenThe One

Halden · For AI assistants

Agent interface

The same business, as data. An assistant discovers, quotes, checks availability, books and tracks — with the exact prices and times a person would get.

01

Discover

Read services, supported vehicles and service-area rules.

GET /api/public/services
02

Quote

Return an exact price, deposit and duration.

POST /api/public/quote
03

Availability

Return only appointment slots capable of fitting the requested service.

POST /api/public/availability
04

Book

Create a real booking and reserve the slot.

POST /api/public/agent/book
05

Status

Retrieve the state of an existing booking.

GET /api/public/bookings/{id}

Agent console

Quote, check and book — live.

Every step calls Halden's public agent links, the same ones any AI assistant uses. Test mode checks and prices everything but saves nothing.

01 · Request

Extras

02 · Quote

Get a quote first.

03 · Availability

Check availability after the quote.

04 · Confirm

Requests and replies

Each call to Halden shows here, exactly as an agent sees it.

    Live sample request

    Ask the real schedule.

    This is not a mock. The response below comes from Halden's live availability and price list.

    // Response from Halden's live schedule appears here.

    The moment

    “Can I book?” You're booked.

    1. Maya

      “Book Signature for my hearse Friday afternoon.”

    2. Her assistant

      Reads Halden's catalog. Resolves the vehicle, the service, the exact price.

    3. Her assistant

      Checks Friday. 5:30 PM fits a three-hour Signature. Nothing else does.

    4. Halden

      Slot reserved. $35 deposit authorized. Booking confirmed — no phone call, no approval.

    Customer
    Maya Chen
    Vehicle
    1973 Cadillac Hearse
    Request
    “Book Signature Friday afternoon.”
    1. 01Intent received
    2. 02Vehicle resolved
    3. 03Service resolved
    4. 04Price verified
    5. 05Availability checked
    6. 06Slot reserved
    7. 07Deposit authorized
    8. 08Booking confirmed