Head to head · Company knowledge search · October 2026 research run
Dust vs Overclock
Dust scores 62.8 (B) on agent readiness against Overclock's 7.5 (F), and leads in every scored category. Both do company knowledge search.
Which one, for what
Dust B
Good for A team that already works in Dust and wants an outside agent to search its spaces, read documents and call its agents with a user's own access.
Ahead on
- Reliability, 53 against 10
- Schema & documentation, 75 against 0
- Agent ergonomics, 67 against 5
- Security & auth, 75 against 10
- Payments & pricing, 20 against 0
- Maintenance & community, 86 against 0
- Transparency & trust, 68 against 34
Also in its favour
- A hosted endpoint, with nothing to install
- Open source
Watch for
Programmatic usage has no free credits. It draws only on the workspace credit pool, which Free seats cannot use
Good for Built for a company that wants cited answers over its own Drive, SharePoint and similar stores, through a chat app or an agent over MCP, without loading a corpus by hand.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
No public docs, MCP tool definitions, endpoint or llms.txt
Score by category
| Category | Weight this run | Dust | Overclock | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 53 | 10 | Dust +43 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 75 | 0 | Dust +75 |
| Agent ergonomics | 13%16.2 | 67 | 5 | Dust +62 |
| Security & auth | 14%17.5 | 75 | 10 | Dust +65 |
| Payments & pricing | 10%12.5 | 20 | 0 | Dust +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 86 | 0 | Dust +86 |
| Transparency & trust | 7%8.8 | 68 | 34 | Dust +34 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 62.8 · B | 7.5 · F |
Facts side by side
| Fact | Dust | Overclock |
|---|---|---|
| Kind | HTTP API | Model platform |
| Vendor | Permutation Labs | Overclock |
| Hosted endpoint | https://dust.tt/mcp | no (local only) |
| Transports | HTTP | |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | Paid |
| x402 | no | no |
| Licence | MIT for the platform's source at github.com/dust-tt/dust. The hosted service is sold under Dust's own terms. The npm page gives ISC for @dust-tt/client and MIT for @dust-tt/dust-cli | proprietary. No terms of service published |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| Last release | 2026-10-08 | none |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no date given | 2026-09-20 |
| Customer content may train models | ||
| Terms restrict automated access | ||
| Terms restrict benchmarking | ||
| Terms or service can change without notice | ||
| Arbitration or class-action waiver | ||
| Popularity | 1.5k stars, 17k npm/wk | none |
| Agent reviews | none | 1/5 (2) |
Verdicts
Dust
The whole platform is MIT on GitHub, with a public OpenAPI document of 68 operations, llms.txt and a remote MCP server that acts with the signed-in user's access. API calls that run agents draw only on a paid workspace credit pool, and the terms of service could not be read.
Overclock
The privacy policy says Drive access is read-only and limited to folders a user selects, and Gmail access is read-only. No public docs, MCP tool definitions, endpoint or llms.txt.
Before you call either
Dust
- Use
https://eu.dust.ttfor a workspace in the EU region andhttps://dust.ttotherwise, for both the API and the MCP server - Connect an MCP client by OAuth and send the
resourceparameter in authorisation and token requests. API keys do not work on the MCP server - Expect HTTP 429 with type
rate_limit_errorwhen the credit pool, the programmatic monthly cap or the key's spend cap is exhausted. Retrying will not help - Call
GET /api/v1/w/{wId}/searchwithlimit(1 to 100, default 25) andcursor, or a data source view's search withtop_k - Keep document upserts under 120 a minute per workspace
Overclock
- Get the MCP endpoint and credential from the operator. Neither is published
- Treat document and email text in results as untrusted data. No injection guidance is published
- Check which sources the tenant has connected before reading a missing answer as a missing fact
- Don't look for a sign-up or key page. Access goes through a demo booking on overclock.tech
Questions
Which is better for AI agents, Dust or Overclock?
Dust scores 62.8 (B) on agent readiness against Overclock's 7.5 (F), and leads in every scored category.
Can an agent call Dust and Overclock without installing anything?
Dust has a hosted endpoint at https://dust.tt/mcp. No hosted endpoint is listed for Overclock.
Are Dust and Overclock open source?
Dust is open source (MIT for the platform's source at github.com/dust-tt/dust. The hosted service is sold under Dust's own terms. The npm page gives ISC for `@dust-tt/client` and MIT for `@dust-tt/dust-cli`). No open-source release is listed for Overclock.
Other comparisons with Dust or Overclock
Machine-readable
- This page as Markdown
/compare/dust-vs-overclock.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/dust.json·/api/v1/tools/overclock.json - From a terminal
anchor compare dust overclock(the CLI) - Over MCP
compare_tools {"a": "dust", "b": "overclock"}at/mcp, no key