> For the complete documentation index, see [llms.txt](https://docs.medcrypt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.medcrypt.com/readme.md).

# Medcrypt Documentation

Medcrypt helps medical device teams build, prove, and maintain cybersecurity across the product lifecycle. Pick the product you're working in to get started.

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>MSI</strong></td><td>AI-assisted regulatory work: threat models, submission documents, audits, and maturity scoring, all grounded in your own evidence.</td><td><a href="/msi/msi.md">MSI overview</a></td></tr><tr><td><strong>MedISAO</strong></td><td>Shared medical device security intelligence: search CVEs and advisories, share remediations with hospitals, and coordinate vulnerability disclosures.</td><td><a href="/medisao/medisao.md">MedISAO overview</a></td></tr><tr><td><strong>Helm</strong></td><td>SBOM and vulnerability management: upload SBOMs, match components, prioritize and remediate risk, and export FDA-ready reports.</td><td><a href="/helm/helm.md">Helm overview</a></td></tr><tr><td><strong>Guardian</strong></td><td>Device security library: C++ APIs for provisioning, secure transport, and cryptographic operations on your device.</td><td><a href="/guardian/guardian.md">Guardian overview</a></td></tr></tbody></table>

### Popular pages

<table data-view="cards" data-full-width="false"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Getting started</strong></td><td><ul><li><a href="/msi/get-started/create-your-first-device.md">Create your first MSI device</a></li><li><a href="/helm/get-started-with-helm/quickstart-process.md">Helm quickstart</a></li><li><a href="/helm/get-started-with-helm/upload-your-first-sbom.md">Upload your first SBOM</a></li><li><a href="/guardian/get-started/quickstart-process.md">Guardian quickstart</a></li></ul></td><td></td></tr><tr><td><strong>FDA readiness</strong></td><td><ul><li><a href="/helm/ensure-fda-readiness/fda-and-cisa-cybersecurity-requirements-for-medical-devices.md">FDA &#x26; CISA requirements</a></li><li><a href="/msi/check-estar-readiness.md">eSTAR readiness check</a></li><li><a href="/helm/ensure-fda-readiness/fda-ready-sbom-and-vulnerability-reports.md">FDA-ready SBOM &#x26; VEX reports</a></li><li><a href="/msi/check-estar-readiness/run-a-regulatory-audit.md">Run a regulatory audit</a></li></ul></td><td></td></tr><tr><td><strong>Reference</strong></td><td><ul><li><a href="/reference/cybersecurity-terminology.md">Cybersecurity terminology</a></li><li><a href="/helm/automate-and-integrate/api-sdk-documentation.md">Helm API SDK</a></li><li><a href="/guardian/api-overview/api-reference.md">Guardian API reference</a></li><li><a href="/helm/changelog.md">Helm changelog</a></li></ul></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.medcrypt.com/readme.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.