The same service, through public interfaces

Bring the group requirement.
Keep each site intact.

Fluefold coordinates kitchen exhaust cleaning throughout Dallas–Fort Worth. Start with an incomplete roster; we develop scope, access options and comparable nonbinding terms by email.

Submit a useful requirement

Use the shared request operation with action: quote and a required need. Send current site facts in specifications.location_account, the proposed route in prepared_approach, documentation, open questions and source/correction history. Keep contact email in contact.email, not the requirement.

{
  "action": "quote",
  "need": "Coordinate a group exhaust-cleaning proposal, retaining current cleaners until terms are agreed.",
  "specifications": {
    "location_account": "Dallas East: two hood systems, gas, last cleaned 2026-08-18, contract every three calendar months. Mondays or Tuesdays 23:00 to 05:00, reopen by 06:00. Fort Worth North: one hood, gas, last cleaned 2026-09-02, contract every three calendar months. Tuesdays only 00:00 to 05:00.",
    "documentation": "Dated reports and before/after hood, duct and fan photographs by site.",
    "open_questions": "Fluefold to reconcile overnight labels, system coverage, local requirements, duration and terms."
  },
  "geography": {
    "text": "Dallas–Fort Worth, Texas",
    "country": "US"
  },
  "contact": {
    "email": "operations@example.com"
  }
}

Interpretation and date behavior

Keep records currently held separate from requested future reports and photographs; requested deliverables belong in documentation, not existing evidence or equipment. Keep inspection versus cleaning, opening month versus preferred start, equipment presence versus unknown dimensions and possible coverage versus completed work distinct. A reported monthly instruction belongs only to its site. Obtain the actual notice before deriving a local obligation. Contract baselines use calendar months, not 90-day substitutions.

Optional preferred_start is a date field. Send YYYY-MM-DD for exact dates; keep month-only or uncertain timing in timing.text. The shared runtime records malformed date words as sent, also lists the date field in missing_specifications, and does not call the requirement dated. Type, length and numeric-bound violations return field errors; enum, pattern and other format hints are not enforced. Missing specification values do not prevent initial help. Inspect raw response fields rather than assuming an exact date from text.

Return and continue privately

The successful receipt supplies id, token and status_url. Keep credentials private. Use request_status to inspect the recorded requirement and any linked authorized offers. Add a corrected requirement through the ordinary envelope with continuation: {id, token}. The original remains on record; a public reference alone grants no access.

Buyer-held drafts or reconstructed links are unverified. A failed status read leaves status unresolved. Inspect exact authorized offer terms before acceptance using its terms_sha256; acceptance places an order. Only shared verified processor state establishes payment. This property does not create offers, bookings or payment state.

What happens next

Fluefold will reconcile the site requirements, seek suitable provider scope and window options, and develop comparable nonbinding terms by email. No visits are booked by a request; scope, timing and price are agreed before commitment.

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. Privacy