Vendor domain: dust.tt · vendor page id dust-tt
A live handshake means the URL answered an MCP initialize as a server on the probe date. It is liveness and nothing more: nobody has run its tools. A tool being catalogued means a server names it, by answering tools/list, in its own source, or in the vendor's documentation. None of them has been called. A tool count of 0 means not measured, never zero tools.
Dust connects your company knowledge, tools, and teams so you can create, share, and run agents across real workflows. Use different models for different tasks, with people in control.
1 of 1 gate unknown, not established from public sources and published as unknown.
The gate is the api_gate field on each product entry, established by hand on the last_checked date shown above. It records whether a solo operator can get API access without a contract. Money is not tracked.
No job tag on any product of this vendor.
An empty list means nobody has tagged these entries, not that the tools do nothing.
No product of this vendor records an MCP endpoint or docs URL that the probe could classify.
npm install -g @dust-tt/dust-cliquoted from https://docs.dust.tt/docs/developer-platform/dust-cli/dust-cli on 2026-09-27, via npm
Login or key hint: dust login
7 subcommands seen, harvested 2026-09-27, all on the tool page.
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it.
No GitHub organisation could be tied to dust.tt with evidence on 2026-09-15.
Recorded by the harvest: not checked: gh CLI missing or not logged in.
A job tag is a vendor claim: it means the vendor says the product does this, and it is not a test result. A listed tool has not been run: the catalogue says what an agent could try, not what works. 1 of 1,252 directory entries are bench tested, meaning somebody personally ran the tool on a stated date, and 0 of this vendor's 1 product are among them. There is no verdict here on whether this vendor is better than another.
Vendor pages group the directory's canonical product entries by vendor_domain. The vendor name is the product display name that matches the domain when several products share it; nothing on this page is typed by hand. Data baked 2026-09-27 by build_directory.py (phase 1).