next_question

shallow

com.sigoseguros/auto-quote · Verify this server

Step 1 of 3: call it until ready_to_quote is true, sending back the collected it returns each time and each answer under answer_as.key. Then start_quote. Returns the one question to put to the customer now, in their language, with the options to offer when the field has a fixed set. Call it before each question and again after every answer, until `ready_to_quote` is true, then call `start_quote`. Send only what the customer said this turn, in `answered`, together with the `collected` from the last call. The connector keeps the record of the conversation, so nothing is repeated and an answer given before its turn is not lost. When `ready_to_quote` turns true, `summary` is what the customer has said: read it back and let them correct it before quoting. It exists so the order and the pace are the connector's rather than a matter of judgement: Sigo's customers are working people, often quoting on a phone, and a turn that asks for four things at once is where they give up. Once a ZIP is given it is checked here, so a customer outside the states Sigo is licensed in is told before being walked through the rest. There are two stretches. `stage: "first_quote"` is the one that ends in estimates. `stage: "second_round"` is for a customer who saw those estimates and wants to finish the application so the carrier can quote it for real: it asks where the car is kept, the VIN, who owns it, the licence, and a few more. The prices it leads to are still estimates; the final quote comes after the carrier's own questions, in Sigo's link. `get_quote` says when that is worth offering. A vehicle a business uses for its work is commercial auto and is not quoted here: use commercial_next_question. Someone who drives only for apps like Uber or DoorDash stays here.

100.0/100

1 trials · measured 2 days ago

next_question scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.sigoseguros/auto-quote, measured 6 Oct 2026 under methodology v0.2.0. Every measured component scored 100.

Component breakdown

ComponentWeightValue
Reliability35%not applicable
Schema integrity25%100.0
Failure behaviour15%not applicable
Latency15%not applicable
Concurrency10%not applicable

Tool details

Transport
remote
Credential class
self-provisionable
Input schema
not declared
Output schema
not declared
Side-effect classification
unclassified

Score history

DayScoreTierMethodology
2026-10-06100.0shallowv0.2.0

Probe evidence

ProbeOutcomes
schema_integritypass: 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.

Vouch score: next_question
[![Vouch score](https://vouch.tools/api/tools/4fcc9757-a5a1-40a6-87c6-030b3bd9b1b4/badge.svg)](https://vouch.tools/tools/4fcc9757-a5a1-40a6-87c6-030b3bd9b1b4)
next_question — Vouch