RevHost

Mark a reminder as completed

Mark a task done, optionally with a short note about what was done.

Create one or more vehicle expenses. For a single expense pass the fields directly. For recurring/batch expenses (e.g. "$150/mo insurance for 6 months"), pass an "entries" array — each entry uses the same fields as a single expense (name, category, amount, date are required per entry). When "entries" is provided, the top-level single-expense fields (name, category, amount, date) are ignored. Returns ids of all created expenses.

STEP 2 OF 2 — create the geofence that preview_geofence described, after the host has confirmed the location. Pass the confirmToken unchanged; it is cryptographically bound to the exact coordinates that were previewed, so a fence can only ever be created where the host was shown. Creates both the boundary and the rule that arms it.

Create a new private rental reservation from the guest's name and one way to reach them (email or phone). Returns the reservation and an editUrl: give the user that link so they can finish the booking in the RevHost dashboard, where any remaining guest details are entered. Never ask for or accept identity documents, licence numbers or dates of birth in chat.

Create a new vehicle reminder

Create a task: work a person or a team must do ("have someone wash the Camry by 3pm", "ask the VA to call the guest"). Not for vehicle maintenance reminders — use create_reminder for those. Call list_task_assignees first when the user names a person or a team. Give assigneeUserId OR assigneeRole, never both; give neither and the task is assigned to the caller. If urgency is high or urgent and no deadline was stated, ask for one; never invent a deadline. The assignee gets a push notification (held until 07:00 overnight unless urgent).

Create a new (non-Turo) vehicle

Delete an expense permanently

Get expense totals and a per-category breakdown for the user's licensed vehicles. Optionally filter by vehicle, start date, and end date.

Which vehicles are FREE between two dates. Use this for "what can I rent this weekend", "which cars are available", "do I have anything free on Friday" — NOT a loop of check_vehicle_availability, which answers for ONE vehicle and costs one call per car (24 calls on a small fleet, 200 on a large one, and it will run out of steps before it answers). This does the whole comparison in one query. It returns a PAGE of results plus `totalAvailable`: report the page and say how many more there are rather than listing everything — a host with 200 cars does not want 200 names in a chat reply. Raise `limit` or ask for `page` 2 only if the host asks to see more.

Read DIRECT-BOOKING (private rental) daily prices for a vehicle over a date range — the prices guests pay on the host's own booking site. Returns each date's price, the vehicle's defaultPrice (the fallback used for any date with no specific price), and the host's minimum allowed price. Dates with no specific price fall back to defaultPrice; if defaultPrice is null the vehicle CANNOT be booked and is hidden from the booking site. This is NOT the Turo calendar — use get_pricing_calendar for that.

Get a specific expense by ID

Get revenue, expenses, and net profit for a date range, with a per-vehicle breakdown. Revenue counts trips that ENDED in the range with status COMPLETED or ACTIVE, at full totalAmount without proration; figures approximate the Financials dashboard, which prorates multi-month/active trips. Use for questions like "what did I make in June?" or "how is the Tesla performing?".

Get a guest profile by ID (Turo or private)

Get a specific invoice with line items

Get aggregated invoice statistics (totals, counts by status)

List recorded trips for a vehicle in a date range, with start/end times and distance.

Get daily prices for a vehicle in a date range

Get details of a specific private reservation

Get a specific reminder by ID

Get one assigned task with its full activity log (who created, assigned, started, noted, finished it).

Get details of a specific Turo reservation (read-only)

Full record for one vehicle by ID — every field, so call it only when the summary from list_vehicles or vehicle_search is not enough. Deleted vehicles are never returned.

Get a vehicle's last known GPS position, how old the fix is, and whether it is moving right now.

What is missing from a host's knowledge base, ordered by how much guest messaging each gap would remove. Use this to decide what to ask the host about next.

Read a host's knowledge base: voice and policies, per-location pickup facts, and per-vehicle handoff details. Access and lockbox codes are never returned — you get hasAccessCode / hasLockboxCode instead, because a code is only releasable inside a trip's pickup window.

Set a host's voice, policies and escalation contact. This is a MERGE: fields you omit keep their stored value, so setting the fuel policy cannot erase the toll policy. Send an explicit null to clear a field.

Cut the starter relay so a vehicle cannot be restarted. Refuses while the vehicle is moving. Requires an explicit reason, which is written to the audit log.

List vehicle expenses for the authenticated user. Use startDate/endDate to filter by date range. Only expenses for licensed vehicles are returned.

List the geofences available to this host — their own, plus published shared ones.

List all guests (Turo + private) across all your vehicles

List cohost invoices for the authenticated user

List private (non-Turo) reservations for the authenticated user. Use startDate/endDate to limit results to a specific time window.

List vehicle reminders for the authenticated user

List ALL reservations (Turo + private) in one call. IMPORTANT: Always use date filters to limit results — there may be thousands of historical reservations. Filter guide: - "upcoming reservations" → startDate=today - "next 7 days" → startDate=today, endDate=7 days from now - "tomorrow's pickups" → pickupFrom=tomorrow 00:00, pickupTo=tomorrow 23:59 - "tomorrow's dropoffs" → dropoffFrom=tomorrow 00:00, dropoffTo=tomorrow 23:59 - "who has my cars right now" → status=ACTIVE Response includes: vehicle info, guest name + phone, delivery/pickup location, dates, cost, and source (turo/private).

Who tasks can be assigned to for this host: people (with ids) and roles (host, employee = Ground Team, va = Back office) with how many members each has. Call this BEFORE create_task or update_task whenever the user names a person or a team, and use the id it returns — never guess an id.

List assigned tasks (work handed to a person or a team: the host, the Ground Team, or back office). view: mine (assigned to or started by me), pool (tasks for a role), created (asked for by me), all. Defaults to open and in-progress, overdue first. Each task has dueAtLocal — quote it; do no timezone math.

List telematics alerts (geofence, tamper, low battery, fault codes) across the fleet or one vehicle.

List Turo reservations (read-only). IMPORTANT: Always use startDate/endDate to limit results — there may be thousands of reservations. For upcoming trips use startDate=today. For active+upcoming use status filters with date range.