LEGAL
API terms
Terms for programmatic access to OpenDeco services and released scientific artifacts.
On this page
Launch gate: these terms must be approved alongside the production API scope, authentication model, quotas, privacy notice and operator details before programmatic service access is offered.
Scope
The production terms must identify the public API surface and distinguish it from private browser or administrative interfaces.
Access and authentication
Public research metadata should remain account-free where practical. Account-linked data, saved work and sustained application access require authenticated credentials with explicit scopes.
Availability and limits
Published quotas, rate limits, change policy and availability expectations must match the deployed service. They should protect service reliability without restricting ordinary access to public research records.
Data and attribution
Responses must preserve the release identity, source licence, citation requirement and access restrictions attached to the underlying record. API access does not widen a third-party licence.
Acceptable use and security
The final terms must define prohibited automation, credential handling, abuse response and suspension. Security testing follows the vulnerability-disclosure policy.
Safety boundary
The API is not intended for real-time decompression control, dive planning or other safety-critical operation.