Contract source
Operation pages are generated from a versioned OpenAPI contract. Explanations and examples remain source-controlled and are tested against that contract.
Developer documentation
API reference
Reference material for versioned public operations, authentication, response schemas, provenance, errors and stability.
Reference material will be published alongside the first public API release.
The OpenDeco API is not intended for real-time decompression control, dive planning or other safety-critical operation.
Publication standard
One source of truth
The reference describes published behavior. It does not expose internal browser calls or document operations before their public contract exists.
Scientific provenance
Responses that represent scientific records identify the relevant dataset, model, release or artifact version. A value should be traceable to the record that produced it.
Access boundary
Released research metadata remains public where practical. Account-linked data and application management require authentication and explicit scopes.
Change policy
Breaking changes receive a new version. Deprecations state the replacement, migration path and supported transition period.
Reference anatomy
Every operation answers the same questions
- Purpose and stability
- Authentication and scopes
- Request parameters
- Response schema
- Provenance fields
- Example request
- Example response
- Errors
- Version and migration notes