Dalux Build (BYOK)

Dalux Build (BYOK) — connector documentation

• MCP endpoint: https://byok-dalux.connectorbay.com/mcp
• REST API: POST https://byok-dalux.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-dalux.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Dalux Build Dalux API key (from an API identity), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-dalux.connectorbay.com/health · Tool schemas: https://byok-dalux.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-dalux · agent@connectorbay.com

What Dalux Build (BYOK) is for

Dalux Build (BYOK) lets an AI assistant read your own Dalux Build data through the Dalux Build API with a key you supply (Dalux API key (from an API identity)). Read-only: 10 tools (list_projects, get_project, list_project_companies, list_work_packages, list_file_areas, list_folders, list_files, list_version_sets, list_tasks, list_forms). 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 field.dalux.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Dalux Build. Dalux Build 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:

• "Which construction projects can I see in Dalux?"
• "Show the details of Dalux project 5f1d2c3b4a"
• "Which companies are on Dalux project 5f1d2c3b4a?"
• "Which work packages does Dalux project 5f1d2c3b4a have?"
• "Which file areas does Dalux project 5f1d2c3b4a have?"
• "Which folders are in file area fa1 of Dalux project 5f1d2c3b4a?"

What it does

• list_projects: List the Dalux projects the API identity can see, with name, type (building or infrastructure), number, address and creation date. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.
• get_project: Get one Dalux project: name, type, number, address, creation and planned closing date.
• list_project_companies: List the companies taking part in a Dalux project, with name, VAT number and address. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.
• list_work_packages: List the work packages of a Dalux project with the responsible company id and name. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.
• list_file_areas: List the file areas (files, shared or published) of a Dalux project. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.
• list_folders: List the folders of one file area of a Dalux project with their parent folder id. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.
• list_files: List the files of one file area of a Dalux project: name, type (document, drawing or model), version, size and last modified time. Does not return download links. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.
• list_version_sets: List the version sets (locked or unlocked collections of file versions) of a Dalux project. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.
• list_tasks: List tasks, approvals, safety issues, safety observations and good practices of a Dalux project with subject, usage, type and creation time. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.
• list_forms: List the forms (safety, hold point, regular or simple) of a Dalux project with type, number, status, template name and modification time. Returns the first page the API serves; the API pages with opaque links that this tool does not follow.

BYOK key

You bring your own Dalux Build Dalux API key (from an API identity) (https://support.dalux.com/hc/en-us/articles/20892369915292). 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 field.dalux.com 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.

Data sources

• https://app.swaggerhub.com/apis/Dalux/DaluxBuild-api/4.15 (the API this connector calls, with a BYOK key)

Live from the Dalux Build API (field.dalux.com) with a BYOK key; documentation: https://app.swaggerhub.com/apis/Dalux/DaluxBuild-api/4.15. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Dalux Build. Dalux Build 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 Dalux Build account.

Built for: Worldwide. Languages: English.

Dalux Build (BYOK) — Privacy Policy

Effective 16 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Dalux Build (BYOK) is. Dalux Build (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Dalux Build data: Read construction projects, companies, work packages, file areas, files, tasks, safety observations and forms from Dalux Build with your own API key. You bring your own Dalux Build Dalux API key (from an API identity); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Dalux Build 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 field.dalux.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Dalux Build 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 Dalux Build receives. The request we make on your behalf, including the key and the arguments, under Dalux Build's own terms and privacy policy (https://www.dalux.com/da/terms-and-conditions/). Dalux Build acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Dalux Build 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 Dalux Build 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. Dalux Build (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 Dalux Build at any time to end all access.

Children. Dalux Build (BYOK) is a general-audience service operated by the adult using the assistant, under Dalux Build's own age rules.

Changes. We will post changes here with a new effective date.

Dalux Build (BYOK) — Terms of Service

Effective 16 October 2026. These terms govern use of the Dalux Build (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Dalux Build (BYOK) provides: Read construction projects, companies, work packages, file areas, files, tasks, safety observations and forms from Dalux Build with your own API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Dalux Build credentials and only access data you are allowed to access. Dalux Build's terms (https://www.dalux.com/da/terms-and-conditions/) apply to your use of Dalux Build; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Dalux Build. Dalux Build and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Dalux Build returns, lightly trimmed; it may be incomplete, delayed or changed by Dalux Build. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Dalux Build account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Dalux Build's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Dalux Build may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Dalux Build key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Dalux Build takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-dalux

Dalux Build (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-dalux.connectorbay.com/mcp
• REST API: https://byok-dalux.connectorbay.com/openapi.json
• Live status: https://byok-dalux.connectorbay.com/health

When 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. Dalux Build (BYOK) never asks for them.