Moving Cars Agent/API Examples
Use the live OpenAPI schema and capability manifest on https://quoting.movingcars.com.au/ before submitting production requests.
Complete canonical examples
Use the complete quote-host examples and current OpenAPI for required and conditional payload fields. Read the live capability and readiness manifest first. These links document supported contracts; they do not prove successful execution.
- Household quote (
household_quote): Submit a customer-authorised household quote; provider distribution is held for staff review until cubing is done. Canonical endpoint. - Vehicle quote (
vehicle_quote): Submit a complete vehicle quote payload or use the server-held intake workflow. Results lookup and selected-option booking are separate consent-based actions. Canonical endpoint. - Contact and callback (
contact): Request a callback using a currently available slot from the callback slots endpoint. Canonical endpoint. - Household booking request (
household_booking): Look up a customer-owned priced quote, confirm the selected option, then request booking with its current fingerprint and a stable idempotency key. Canonical endpoint. - Estimate household move volume (
estimate_volume): Estimate cubic metres from customer-authorised inventory; estimates are not guaranteed measurements. Canonical endpoint. - Customer Assistant support (
customer_assistant_support): Ask supported service questions and provide feedback through the canonical FAQ contract; use bounded fallback for unsupported questions. Canonical endpoint.
Required consent and payload rules
- This marketing site provides discovery and browser handoffs; API execution belongs to https://quoting.movingcars.com.au. The shared catalogue describes supported contracts, not confirmed Moving Cars brand applicability or end-to-end availability.
- Read the live canonical manifest, OpenAPI, guide and examples together before acting. Check supported, brand_applicability, hostname_readiness, execution_readiness and activation separately under 2026-10-capability-readiness-v1. Unknown brand applicability does not remove a supported capability or establish that Moving Cars offers it. Before submitting customer data, establish service applicability from authoritative quote-host policy or the operator; if unresolved, stop the API action and offer the official browser handoff without claiming success. Execution can only be established by the separately authorised customer workflow validating current inputs and dependencies.
- Vehicle hostname readiness checks only vehicle_host_tenant_resolution. Recheck GET https://quoting.movingcars.com.au/api/v1/vehicle-quotes/assistant/intake/session before intake. Ready does not prove Company configuration, pricing, booking, communication or successful submission. The other five capability hostname prerequisites and all customer execution remain unverified by discovery.
- If readiness evidence is stale, missing or unavailable, do not infer ready or unsupported. If the exact host is unavailable, stop API intake and ask the operator to verify ownership; if unknown, retry the read later or use the official browser handoff without claiming it succeeded. Never submit customer data to test discovery. WebMCP registration and activation are separate; API support does not enable tools.
- For each action, obtain the customer request and required consent, show the submitted details, and use customer_consent.confirmed=true with the operation-specific customer_consent.basis. Quote and volume requests use customer_requested_quote; callbacks use customer_requested_callback. Results and booking require their own consent bases from the canonical contract.
- Send origin_domain=quoting.movingcars.com.au to this exact quote host. Omit tenant unless separately agreed; vehicle tenancy requires unique active host ownership with no arbitrary fallback. Preserve actual Moving Cars source attribution using source_site=movingcars.com.au and the real source_path; never invent journey or campaign evidence.
- Use the canonical required and conditional fields, authentication and session rules, rate limits and idempotency. Vehicle intake needs the issued session token after draft creation. Preserve stable idempotency keys for retries and household recovery.retry_idempotency_key for corrected rejected fields. Resolve ambiguous locations before retrying.
- Submission, results lookup, booking and payment are distinct. Results require customer ownership verification; booking requires the selected option, current confirmation fingerprint and stable idempotency key. No payment details are accepted by the booking APIs. Return the actual service status; opening a form or submitting a quote does not confirm a price, booking, collection or delivery date. Existing provider automation and staff-review rules still apply.
Household quote examples include customer contact, route, move_date and inventory. Vehicle examples include customer contact, pickup, delivery, make, model, year, is_drivable and any conditional condition or damage fields. Callback examples require a fresh slot token from the canonical slots endpoint. Use the complete canonical examples for volume, results, booking and support; consent to a quote is not consent to a booking.