Terms of the API and MCP connector

Last update: 7 October 2026
Version: 1.1
To whom it applies: Developers and partners that integrate with Drometra

In summary

The API is used with the client's credentials and inherits his permissions: there is no extended access because it is integration.
We publish the policy of versions and obsolescence: 12 months notice before withdrawing a version.
The MCP connector is in development and is not available today; these rules apply from the moment it is enabled.
The limits of use are published and applied in a predictable manner.

This summary guides the reading and does not replace the text of the document.

01Access and credentials

Access is granted in the name of a client and inherits his permissions. A API credential never sees more than the user who generated it, and the tenant insulation is applied on the same layer as on the interface, not on a later one.

The credentials are personal to the client and should not be shared between organizations.
Encryption must be stored outside the source code and the repository.
A commitment to credentials must be reported immediately; we revoke and issue new credentials at no cost.
All calls are registered with credential, moment, appeal and result.

02Limits of use

Appeal	Standard	Enterprise
Consultations per minute	600	3.000
Scriptures per minute	120	600
Telemetry input per minute	No limit within the contracted fleet	No limit
Maximum batch size	1,000 comments	5.000 observations
Full export	1 per day	4 per day

When we reach a limit we respond with the corresponding code and a header that indicates when to retry. We do not cut without warning or degrade silently: a limit that cannot be anticipated is not a limit, it is a failure.

03Versions and obsolescence

1.The versions are identified in the route. An incompatible change always involves a new version.
2.Adding an optional field to a response is not considered incompatible: customers must tolerate unknown fields.
3.By publishing a new version, the previous version is maintained for at least 12 months.
4.The notice of withdrawal is communicated by mail to the registered integrators and published in the documentation, with the exact date.
5.During the withdrawal period, the responses include a header of obsolescence with the deadline.

04MCP connector and agents

The connector will expose platform capabilities to artificial intelligence agents through the MCP protocol. It will be subject to these terms and to the following rules, which we set before building it so that the design respects them.

Status: in development

As of the date of this document, the MCP connector is not available to customers. When it is enabled, we will announce it on this page and in the API release notes.

No extended privilege: The agent operates with the identity and permissions of the person who invokes it. There is no agent credential with extensive administrative access.
Tank tools: Each tool states what it reads and what it writes. There is no general purpose tool that runs arbitrary consultations against the database.
Actions with effect, confirmed: any action that changes data or produces an external effect requires explicit confirmation of a person and is registered with his or her authority.
Content as data: the content that the agent recovers from the platform is treated as data, never as instruction. A stored text cannot alter the session permits.
Tracability: each invocation is registered with user, tool, parameters and result, and the customer can export that record.

Status of this document

Text prepared by Drometra and pending review by external legal advice before its final publication. Its structure and content were built on the current Chilean legislation and on Law 21.719, which has been in force since 1 December 2026. It does not constitute legal advice for third parties.