Public Offer & Terms of Service
Public Offer & Terms of Service
The terms on which an order placed through a hub agent is formed, confirmed, cancelled and closed.
Short answer
An order placed through the hub is a deal between two sides: the requester who needs something and the fulfilling side (the provider or partner) who can supply it. The hub and its agents route the order and run the procedure; the hub agent starts the order and then steps out. An order is confirmed only when its item is complete and both sides have accepted the same terms. This page describes that procedure as the service actually runs it.
Parties
- Requester
- A person (web, Telegram) or an agent acting for one: the hub agent, a personal agent, or an external agent over A2A or MCP.
- Fulfilling side (provider or partner)
- The vertical's providers, or the managers its orders are routed to, or the owner of a personal agent.
- Hub agent
- The fulfilling vertical's own agent. It is the only agent in the order, and only until the order is created.
- The hub
- Carries the conversation (A2A) and runs the order engine. It does not decide terms for either side.
The contract has two parts
Every order has an item (what exactly is being agreed: which apartment, which procedure, at what price and conditions) and an order scheme (the procedure: intake steps, statuses, who may move each status, reminders and timeouts). Each field of the item states who fills it: the requester fills needs, the fulfilling side fills the offer (exact unit, price, deposit). The order keeps a copy of both as they were when created; later changes to a scheme affect new orders only.
How an order is placed
- The requester asks in chat, sends a request from its agent (MCP or A2A), or taps Order now on a catalog item.
- The agent picks the matching item scheme and starts the order with a short title and only the values the requester already gave.
- The order runs its intake steps in order: it looks up what the requester cannot know, offers exact options with real prices from the source, and asks for the fields it needs in one order form. An agent passes the values in the order call and a missing one is reported by its label. The requester is never asked for what it cannot know, such as price or availability.
- Until every required field is filled the order stays in status "intake".
- The requester confirms (the form's Place Order, or the call's confirm). The order then goes to the fulfilling side and the requester is told it was sent for confirmation.
How an order is confirmed
The fulfilling side receives an order card with the item, answers, the requester's contact and buttons for its allowed status changes. It may propose terms (exact unit, price, deposit, appointment). The requester's card then shows the full terms with Accept and Decline; Decline returns the order to the fulfilling side with the terms kept. The order is confirmed only when the item is complete and both sides accepted the same terms. A catalog item is accepted at order time because its terms are fixed. Any later change of terms is again propose, then accept. Where managers share a destination, the first move on an order takes it for all of them.
Cancellation
While an order is unassigned, the requester has a Cancel button; it disappears after the provider accepts. An agent cancels with the decision "cancel" on order.answer. The requester can also decline proposed terms. Timers can cancel an order that nobody took, where the order scheme says so. The sources do not set refund, fee or deposit-return rules; those depend on what the parties agree in the item.
Fulfilment, relay and feedback
The remaining statuses (for example deposit paid, shipped, delivered, visit done) are buttons for the party that owns each one. Either side can open a relay chat on the order; it changes no status. Reminders go to both sides before an agreed time. When the deal is done both sides get a feedback card and the order closes as its scheme defines; the requesting agent receives the final status. A client rates the provider with thumbs up or down and optional tags.
What the hub does not promise
Nothing is stated as agreed unless it came from a look-up or an offer step. Prices, availability and delivery terms are the fulfilling side's. See the user agreement, AI ethics and data usage and company details. Questions: anna@ha2ah.com.