Docs
Integrate a genome
How to get a genome file into IntelliNix and read it from your own code, with the real status of each way.
Installing a genome has three steps: get the file, verify it, import it. Nixtra covers the first two on the site. The import happens in IntelliNix. These guides give the exact calls for each way of doing it, the prerequisites, what to expect and what to do when it fails.
Read the status first
Some ways are not built yet. The SDK import methods, an import through the public API and an import through MCP are examples. Every guide marks them “Not available yet” and shows what to use today. There is no one-click install.
Guides
- IntelliNix: Import in the web app: preview, consent, undo.
- REST: The import routes with curl, and the public /genome/v1 API.
- Python: A script for the import routes, and the SDK for reading a genome.
- JavaScript: A fetch script for the import routes, and the SDK for reading a genome.
- MCP: The genome MCP endpoint, its six tools and a client configuration.
The general overview, with a file checker and a list of common problems, is on the install page.
Status of each way
| Way to install | Status | Details |
|---|---|---|
| IntelliNix (import) Import in Settings, Workspace policy, Transfer | Needs an IntelliNix workspace with the genome flags on | Preview, consent and undo. The Transfer section appears only when the agent_genome and genome_format flags are on for the workspace, and only an administrator can import. |
| Python SDK import methods (import_preview, import_consent, import_undo) | Not available yet | The methods exist in the SDK, but the routes they call are not mounted on the platform. Each call raises NotFoundError (404). |
| Python Plain HTTP script against the workspace import routes | Needs an IntelliNix workspace with the genome flags on | Python standard library only. Same flags and administrator rule as the IntelliNix import. |
| Python Check the file checksum with hashlib | Works today | Needs nothing from IntelliNix. |
| JavaScript SDK import methods | Not available yet | The JavaScript SDK has no import methods. |
| JavaScript fetch against the workspace import routes | Needs an IntelliNix workspace with the genome flags on | Node 18 or newer. Same flags and administrator rule as the IntelliNix import. |
| REST Workspace import routes under /genome | Needs an IntelliNix workspace with the genome flags on | Preview, consent and undo with curl. Needs the agent_genome and genome_format flags and an administrator. |
| REST Import through the public /genome/v1 API | Not available yet | The /genome/v1 import routes are not mounted. The public API can read, compile and export a genome, not import one. |
| MCP Import a pack through MCP | Not available yet | The genome MCP endpoint has six tools and none imports a file. |
| MCP Read, compile or export the genome of an agent already in your workspace | Needs an IntelliNix workspace with the genome flags on | Needs the genome_public_api and agent_genome flags and an API key with the genome scopes. |
| Verify the file Check a downloaded file in your browser, or with sha256sum, Get-FileHash or hashlib | Works today | The browser check needs JavaScript on this page. The command-line checks need nothing from Nixtra or IntelliNix. |
| One-click install from Nixtra into IntelliNix A button on a pack page that installs it into your workspace | Not available yet | There is no link between the two sites. You download the file here and import it there. |
Placeholders
Snippets use [YOUR-INTELLINIX-API] for your IntelliNix API address and [YOUR-API-KEY] for
your key. Replace them with your own values. Never paste a real key into a page, a chat or a repository.