For assistants & agents

One requirement.
Keep the unknowns.

Submit an Austin kitchen opening request, not a booking.

POST a JSON envelope to /_c/request. A nonempty need is required. Specifications can be incomplete. Keep contact in contact, separate from the requirement.

{
  "action": "quote",
  "need": "Review the gaps for our Austin commissary, without duplicating landlord or GC work.",
  "specifications": {
    "operation": "Food truck commissary",
    "inspection_target": "2026-11-18",
    "inspection_date": "2026-11-18",
    "opening_target": "late November, flexible",
    "grease_route": "reported",
    "grease_owner": "landlord",
    "grease_details": "Says pumped last month; manifest pending",
    "hood_route": "conditional",
    "hood_owner": "GC",
    "fire_route": "arranged",
    "fire_owner": "landlord",
    "domestic_equipment": "unsure",
    "soda_equipment": "absent"
  },
  "geography": {
    "text": "Austin, TX",
    "country": "US"
  },
  "contact": {
    "email": "owner@example.com"
  }
}

Preserve the scope, not just the headline.

Supply site_address, operation, inspection_target, opening_target and the full situation. For grease, hood, soda, domestic and fire, use the suffixes _equipment (present, absent, unsure), _route (determine, new, arranged, reported, conditional), _owner and _details. Do not treat unknown as absent. Keep fire and domestic scope separate.

Include scope_summary (retain, verify, propose), preliminary_scope, unresolved_questions and next_action_owner when prepared. Optional prior_amounts are buyer-reported. A changed request may include supersedes with the earlier reference. It is a new recording, not an update to accepted terms.

Dates & validation

Send genuine YYYY-MM-DD values in inspection_date and opening_date. Keep flexible wording in the corresponding _target field. The endpoint enforces types, maxLength and numeric bounds, not enum or pattern rules. A malformed date in a date-formatted field is retained as sent and listed in missing_specifications; it must remain open and does not establish dated status. A type, length or bound error returns HTTP 400 with errors naming the field. Do not assume listed choices are enforced by the endpoint.

Receipt is not fulfillment

Check the successful response and recorded flag before presenting receipt. Retain its id and missing_specifications. Firstmise will review the existing arrangements and remaining questions, then reply by email with a proposed schedule and nonbinding estimate through one contact. No visits are booked. No price, capacity or inspection outcome follows from receipt. An email is needed for a reply; do not assume an agent request without contact is replyable.

Contact details are kept apart from the requirement, while we correspond or do business and for 24 months after, so a later request picks up where it left off; ask us to delete them at any time.