Paperspace (BYOK)
Read your Paperspace machines, deployments, projects, datasets and models and check GPU machine availability with your own API key
Read your Dust (US region) workspace agents, skills, spaces, data sources, tables, documents, apps and triggers with a workspace API key
Unify Dynamics LLC
Real questions, and the tools your agent calls to answer them.
list_agentssearch_agentsget_agentlist_spaceslist_data_sourceslist_data_source_viewsDust (BYOK) lets an AI assistant read your own Dust data through the Dust API with a key you supply (Dust workspace API key). Read-only: 11 tools (list_agents, search_agents, get_agent, list_spaces, list_data_sources, list_data_source_views, list_tables, list_documents, list_apps, list_skills, list_triggers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to dust.tt. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Dust. Dust and its logos are trademarks of their owners and are used only to say which service the connector works with.
Sources: Live from the Dust API (dust.tt) with a BYOK key; documentation: https://docs.dust.tt/api-reference/agents/list-agents. Endpoints checked against that documentation on 2026-10-16.
The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.
11 tools, grouped by job. Every one is read-only or compute-only.
https://byok-dust.connectorbay.com/mcpThree ways in, the same 11 tools.
https://byok-dust.connectorbay.com/mcpPOST https://byok-dust.connectorbay.com/v1/tools/<tool>https://connectorbay.com/openai/byok-dust.jsonhttps://connectorbay.com/v1/chat/completions · how it worksX-Upstream-Key header (get one at dust.tt).Dust (BYOK) lets an AI assistant read your own Dust data through the Dust API with a key you supply (Dust workspace API key). It is a hosted MCP server with 11 tools such as List agents, Search agents, Get agent, List spaces, List data sources, List data source views, published by Unify Dynamics LLC. It is independent and not affiliated with Dust.
Add the MCP endpoint https://byok-dust.connectorbay.com/mcp to your client's MCP, connector or integration settings (streamable HTTP, no OAuth). For REST, POST JSON to https://byok-dust.connectorbay.com/v1/tools/<tool>; the OpenAPI description is at /openapi.json. For OpenAI function calling, load https://connectorbay.com/openai/byok-dust.json.
Yes: this is a bring-your-own-key connector. Create a Dust workspace API key at https://dust.tt/ and send it in the X-Upstream-Key header. ConnectorBay uses it for that one call only and never stores, logs or caches it.
Yes. Every tool reads or computes. Nothing is created, changed, sent, paid or deleted in your account.
Yes. It is free to use within the published rate limits; an optional Pro key raises them. There is no account to create.
Read your Paperspace machines, deployments, projects, datasets and models and check GPU machine availability with your own API key
Search your Papertrail logs and read your systems, groups, saved searches and log destinations with BYOK
Read your Parallel web research monitors and their change events, task runs and task groups with your own API key
Read your Parasail model list, invoices, spend breakdowns and dedicated deployment status with your own API key
Browse and query the open datasets of the City of Paris open data portal (Opendatasoft Explore API) with your own portal API key
Read your Particle IoT devices, their online status and firmware, and product fleets with BYOK
https://byok-dust.connectorbay.com/mcpPOST https://byok-dust.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-dust.connectorbay.com/openapi.jsonX-Upstream-Key header of every request (never stored, logged or cached)https://byok-dust.connectorbay.com/health · Tool schemas: https://byok-dust.connectorbay.com/tools.jsonDust (BYOK) lets an AI assistant read your own Dust data through the Dust API with a key you supply (Dust workspace API key). Read-only: 11 tools (list_agents, search_agents, get_agent, list_spaces, list_data_sources, list_data_source_views, list_tables, list_documents, list_apps, list_skills, list_triggers). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to dust.tt. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Dust. Dust and its logos are trademarks of their owners and are used only to say which service the connector works with.
Ask your assistant things like:
list_agents: List the agents of a workspace with model, status, scope, version, skills and tags; choose the view (all, workspace, published, global, favorites).search_agents: Find agents by name (case-insensitive substring) among global and accessible published agents.get_agent: Get one agent's configuration: name, description, instructions, model, skills, tags and step limit.list_spaces: List the spaces you can access with kind and whether access is restricted.list_data_sources: List the data sources of a space with name, description, connector provider and creation time.list_data_source_views: List the data source views of a space with category, kind, owning data source and last update.list_tables: List the tables of a data source with title, description, MIME type, tags, column schema and timestamp.list_documents: List the documents of a data source with title, MIME type, tags, source URL, size and chunk count (text bodies are not returned); paged by offset.list_apps: List the Dust apps of a space with name and description.list_skills: List the workspace's custom skills with status, source, availability and descriptions.list_triggers: List agent triggers (schedules and webhooks) with kind, status and the agent they run; needs an admin API key.You bring your own Dust Dust workspace API key (https://dust.tt/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to dust.tt over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.
Live from the Dust API (dust.tt) with a BYOK key; documentation: https://docs.dust.tt/api-reference/agents/list-agents. Endpoints checked against that documentation on 2026-10-16.
Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Dust. Dust and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Dust account.
Built for: Worldwide. Languages: English.
Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.
What Dust (BYOK) is. Dust (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Dust data: Read your Dust (US region) workspace agents, skills, spaces, data sources, tables, documents, apps and triggers with a workspace API key. You bring your own Dust Dust workspace API key; the assistant sends it to us with each request.
BYOK key. The key you supply is used to make the one Dust call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to dust.tt, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Dust rejects it, we say so without repeating it.
What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Dust receives. The request we make on your behalf, including the key and the arguments, under Dust's own terms and privacy policy. Dust acts at your direction and is the only recipient of the data of your request besides our hosting provider.
What we return. The answer Dust gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.
What we do not do. We do not build a profile, sell or share personal information, or keep your Dust data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.
Sub-processors. Dust (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).
Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Dust at any time to end all access.
Children. Dust (BYOK) is a general-audience service operated by the adult using the assistant, under Dust's own age rules.
Changes. We will post changes here with a new effective date.
Effective 24 October 2026. These terms govern use of the Dust (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").
Email agent@connectorbay.com. We answer within two business days.
https://byok-dust.connectorbay.com/mcphttps://byok-dust.connectorbay.com/openapi.jsonWhen you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Dust (BYOK) never asks for them.