This page gathers, at a predictable address, what a developer, or an agent, needs to understand how to integrate with Dulyx. The platform is in early access: the full API reference and the OpenAPI specification are released along with the key, and what is here is the public contract.

The call

The integration is one HTTP request. The agent receives the question as text and returns a ready answer, already grounded in the data it is allowed to see:

POST /api/v3/agent/chat
Authorization: Bearer <token>
Content-Type: application/json

{ "question": "Release John Doe's order.", "agentId": 3 }

The response carries the text for the user, the session identifier and, when the request implies a change, a confirmation block with what would be done (method, target and changes) instead of executing it directly.

Scope and permission

Access is by token scoped by context: each token sees only the contexts it was granted, and each context exposes only the knowledge and Actions registered in it. The rule works both ways: the model receives no URL or credential, and an Action outside the scope does not exist for that agent. A write never runs on the first try: it returns a proposal that needs confirmation.

MCP connection

The granted contexts can become tools inside the assistant your team already uses: Claude, ChatGPT, Cursor and everything else that speaks Model Context Protocol. The data funnel runs on the Dulyx side, the external model receives the question and the answer as text, and writes still stop at confirmation. The address is public (api.dulyx.com.br/api/v3/mcp); what is per organization is the authorization.

Ready-made integrations

More than twenty sources come pre-registered: Trello, GitHub, Slack, Jira, Stripe, HubSpot, Zendesk, Notion, Google Workspace and others. Connecting means filling in the credential: the base URL, the authentication and the Actions are already described. The full catalog is in the integrations section, and what is not in it comes in through your own REST API.

Specification, OAuth and MCP

/openapi.json: OpenAPI 3.0 of the public surface (v3 routes by API Token, MCP server, OAuth flow and widget), generated from the API's full spec with no manual editing. The interactive reference is at api.dulyx.com.br/api/docs.
OAuth 2.0: authorization code with PKCE (S256) and dynamic client registration (RFC 7591). The issuer is https://api.dulyx.com.br: RFC 8414 metadata at /.well-known/oauth-authorization-server and RFC 9728 at /.well-known/oauth-protected-resource, with scopes_supported: ["mcp"]. The same paths on this domain redirect there.
MCP server: POST https://api.dulyx.com.br/api/v3/mcp (Streamable HTTP, JSON-RPC). It accepts an API Token or an OAuth access token with the mcp scope; with no credential it responds 401 with WWW-Authenticate pointing to the metadata, which is how Claude and other clients start the authorization. Manifest at /.well-known/mcp.json.

Machine-readable files

/llms.txt: the platform summary as text, with what it does, when to use it and how to call it.
/sitemap.xml: all public addresses.
/robots.txt: crawling rules.
The home page responds text/markdown to anyone who asks via Accept, and nonexistent addresses return a real 404, with recovery paths in the body.

How to get a key

Key generation is not self-service yet: access comes through the waitlist, and technical questions go to contato@dulyx.com.br. When general availability arrives, this page will point to the full reference and to the test environment.