3Dogs

Asking: quick answers and deep runs

You ask in plain words and your assistant calls 3Dogs on your behalf. A quick answer takes about a minute. A deep run goes further and takes about three minutes. Either way you get a cited answer, and your assistant tells you which kind you got.

The two tiers

Quick answer (the default)Deep run
How to ask"Run this in 3Dogs""Run it deeper"
ModelsA panel of models from different makers (3 makers), reconciled by a model from yet another makerA larger multi-cloud panel of models from different makers
Live webYesLive web searches
ReviewReconciled by one model into one cited answer3 reviewers from different makers cross-examine the answers against the sources
TimeAbout a minuteAbout 3 minutes
Comes back asA result, or a job id if it is still runningA job id; your assistant checks it until it finishes

Support's reference says a job usually takes 15 to 30 seconds and larger ones longer; the connector's own tier note says a quick answer takes about a minute. Plan on up to a minute.

Quick answers

Hand 3Dogs a question (plus, if useful, a goal, constraints and material). 3Dogs gathers live web research, its own records and your material, sends it to a panel of models from different makers that answer separately, then a model from a different maker than your assistant reconciles them, keeping only claims it can source and showing where the models split.

Your assistant may add its own short independent answer (my_answer, up to 6,000 characters), written before it sees any 3Dogs result. 3Dogs counts it as one more voice beside the panel and reports where you agree or differ.

If the answer is not ready within the connector's wait (it waits up to 15 seconds by default), you get a job id and your assistant polls check_3dogs_job (see Limits, usage and polling).

Deep runs

What comes back

Output options

output_format can be summary, memo, table or json. language takes a language code such as en. goal says why you want the result; constraints is a list (geography, period, budget, jurisdiction, exclusions). context_sources names the sources of your material so citations are accurate. client_request_id is a unique id for idempotency. capability is a capability identifier or auto. All are optional; only question is required.

Good practice

Last updated 11 November 2026