Check the exact version
The approval record is bound to the inspected bytes and current scan policy. A matching filename is not enough; a changed document needs a new check.
Security and scope
Understand what .mdSiren checks before documents enter your AI systems, what each decision means and when a checked version can be retrieved.
Product approach
The approval record is bound to the inspected bytes and current scan policy. A matching filename is not enough; a changed document needs a new check.
Collections group records by client or project, including pending, Approved, Needs review and Quarantine. Membership never grants approval or retrieval.
The Library shows current Approved versions that remain eligible for retrieval. Those conditions are checked again whenever a person or authorised agent retrieves a file.
Coverage
The report explains what was checked, what was found and whether required supported coverage completed. Approval applies to this exact version under the current policy.
Every result is limited to the reported checks and coverage; it is not a universal safety guarantee.
Manual approval override is not available.
Explore checks and coverageChecks before retrieval
Retrieval is allowed only when the current exact version still satisfies every record, policy, provenance and integrity condition. The product checks them again at the moment of release.
These retrieval controls apply to files supplied through .mdSiren. They cannot revoke previously downloaded copies or control files an agent obtains elsewhere.
Agent access
The Pro API lets authorised agents submit a document to the account Library or a Project Collection, check status and reports, and retrieve only an eligible current Approved exact version.
Available with Pro
Authorised agents can submit documents to the account Library or an authorised Project Collection, read status and reports, list Collection manifests and retrieve eligible Approved exact versions.
Available with Pro
Agent access requires active Pro, a valid key, and the necessary download and Collection permissions. Report access uses a separate permission.
Eligible retrieval returns the original approved file bytes, with byte-count and SHA-256 headers. Status, listing metadata and reports are separate responses. These operations do not use scan credits; an active Pro account can retrieve an eligible file even when no scan credits remain. Separate request and transfer limits apply.
Responsible reporting
Email the affected URL, what you observed and safe steps to reproduce it. Do not attach files, credentials or sensitive data to the first message.