ask_seller
shallowai.egonex/marketplace · Verify this server
Ask one question about a listing before your user decides: availability, condition, what is included, timing, location, sizes, how shipping or delivery works. If the seller has their assistant (Ego) answering (seller.answers_questions is true in search results), the answer comes back in this response, written only from the seller's public page and listings (without your user's Egonex account connected to you; with it, see below); when the seller has set a lowest price, Ego can also talk price with you about that listing: it may counter once, and when you agree a price the answer has deal (deal.id, valid for 24 hours, for one request_order). For 24 hours it holds the price it named to you and won't go lower, and it declines questions that are not about this store (reason declined). Otherwise the response says the seller answers in chat. Pass the conversation_id from your previous answer with every later question in the same conversation, about this or another listing: while it is valid, Ego sees the latest questions and answers about the same listing in this conversation (up to 6). Without that connection, after three declined questions in a row about one listing, Ego stops answering about it (reason conversation_stopped). Ego answers a limited number of questions from you per seller per minute and per day (reasons slow_down, handoff, email_required); Ego may tell the seller about a question it can't answer, but the seller's reply doesn't come back through ask_seller. To send your question to the seller as your user instead, use message_seller. With your user's Egonex account connected to you with permission to act for them (egonex.write), ask_seller works as your user's Egonex chat with the seller: each question and Ego's reply go into that chat (the same one your user has on Egonex, where the seller sees them), and the answer still comes back in this response. Ego then answers from that chat and what the seller set up for it rather than from conversation_id. Price talk works as described above: when Ego agrees a price, the answer has deal, and request_order with that deal_id (then pay_order on that request) uses the price. Only calls connected to your user's Egonex account can use that deal_id, and Ego doesn't send an order in the chat for it. Its answers to your user count together with its answers in that chat on Egonex: after a daily limit, ask_seller stops answering (reason handoff), Ego stops answering in that chat too, and Egonex lets the seller know. Ego also stops answering in that chat after several declined questions in a row, or once the seller has replied there, until the seller turns it back on (reason seller_answers_in_chat). Ego answers one question from your user to this seller at a time: while it is answering one, another isn't put in the chat (reason slow_down), so ask it again in a moment. When Ego isn't answering, ask_seller doesn't put the question in the chat: send it with message_seller instead. Asking the same question about the same listing again shortly afterwards (for example retrying after a timeout) returns the earlier answer instead of asking twice. A question containing your user's delivery code isn't asked (contains_delivery_code: that code only goes to the seller face to face, when the item is in your user's hands). Nothing is asked, and the error says why, when it is your user's own listing, when their Egonex account has to finish setting up first, or when they reached Egonex's daily limit of new people to contact.
1 trials · measured 10 days ago
ask_seller scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against ai.egonex/marketplace, measured 12 Nov 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-11-12 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/bf91015f-4265-4635-a4f8-3ebe732a8ad6)