For assistants and purchasing agents

Carry the building’s intent forward.

Start with the owner’s desired outcome, not a completed technical specification. Tendmark develops a preliminary route and continues scope and fee work by email.

Operated by Tempered Technologies LLC, 8 The Green STE B, Dover, DE 19901.

Send a requirement

POST JSON to /_c/request. Use action: "quote", a nonempty need, optional specifications and contact.email for a reply. OpenAPI, assistant guide and MCP endpoint describe the shared capability.

Useful specifications: building_address, area_sq_ft, area_basis, building_use, situation, proposed_route, proposed_scope, open_questions, history, prior_reference, fee_status and continuation_brief. Omit unknown area rather than entering zero. Keep residential and commercial breakdowns, parking basis and contradictory state correspondence explicit. Preserve superseded facts in history, not as current assertions. Contact goes only in the contact envelope.

Synthetic example

This is an illustrative request, not a verified building or customer.

{
  "action": "quote",
  "need": "Please take over compliance and review incentive eligibility for our office without on-site staff.",
  "specifications": {
    "building_address": "410 Example Avenue, Tacoma, WA (synthetic)",
    "area_sq_ft": 32000,
    "area_basis": "Excludes parking",
    "building_use": "Office",
    "situation": "No Portfolio Manager account. HVAC contractor visits twice a year.",
    "fee_status": "Not developed; request indicative fee"
  },
  "contact": {
    "email": "owner@example.com"
  }
}

Actual validation and state contract

The endpoint requires need. Incomplete specifications can be recorded; missing required specification fields are returned in missing_specifications. This schema has no required technical fields. Provided values are refused for type, maximum length or numeric bounds. Enum, pattern and format are not general rejection rules. A non-YYYY-MM-DD value in a date-formatted field is retained and listed as missing, not treated as a dated request. This property declares no date fields.

Without contact.email, there is no email reply route. Do not assume missing_specifications includes contact. Check the envelope’s contact yourself. Receipt requires a successful response and returned reference. Receipt does not establish accepted scope, a fee, filing, compliance approval or incentive payment. A buyer-supplied prior_reference links the revision’s context, not a new service commitment.

Next work belongs to Tendmark

Tendmark will review applicability evidence and existing records, establish data access requirements, arrange the qualified role and implementation responsibilities, and develop a building-specific scope and supportable indicative fee. Continue this same brief by email, resolving only consequential gaps. Obtain agreement to scope, price and required authorizations before binding service execution. Do not treat receipt as compliance, filing, approval or payment.

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.