Evidence-backed facts
- protocols.io documents protocol, step, material, workspace, collection, file, comment, and supporting API records. informative
- Requests require documented OAuth or application credentials where applicable; reads do not grant protocol ownership, publication, execution, validation, or protocols.io authority. informative
- Clients must bind API version, resource identifier, workspace or collection, visibility, pagination, credential, representation, and update state. informative
- Published protocols can be revised, incomplete, access-limited, or unvalidated and do not prove experimental reproducibility, safety, authorship, or outcome. informative