Biotope
Biotope is a framework that helps your AI agents build and maintain purpose-driven knowledge representations. Imagine you need to build a knowledge graph that uses messy clinical data to find promising drug targets, or maintain a database of all people, events, and resources of a distributed organization. You can give raw data and the purpose statement to the biotope agent and it will build the graph topology, mapping, entity and conflict resolution, following the industry best practices. Biotope simplifies the process of building and maintaining the data project, but semantic authority and final decisions on the representation stays with the human.
How data projects that are created by the biotope agent work:
- Inputs. Structured files are described automatically using croissant-baker: CSV, TSV, Excel, Parquet, JSON, HDF5 and AnnData, FHIR, VCF, BAM, FASTA, DICOM, NIfTI, images and more. Unstructured documents, such as papers and web pages, become records through an extractor the agent writes, and each value keeps the quote it came from.
- Output. Neo4j import files or one SQLite file. Every node and edge names the source rows it came from.
- Maintainability. The biotope-created data project is plain Python in a fixed layout and static type-checking for all entities and mappings. New data of the same shape rebuilds with commands only, and a change in the data's structure is reported before the build.
- Versioning. Everything Biotope writes is a plain file that you commit with your own git. Each build records its code, data revisions and library versions.
Get started
You need uv and an agentic harness (e.g Claude Code, Codex, open-code, etc.).
-
In your agentic harness, add the Biotope marketplace and install the plugin:
/plugin marketplace add biocypher/biotope#biotope-v1.0.0 /plugin install biotope@biotope
-
Start your agent in your project folder.
-
Tell it where the data is and what the graph is for:
Use biotope to build a knowledge graph from the files in
data/. It is for our institute's staff, who look up who works on which topic, in which group and on which projects.
The agent installs Biotope into the project's own environment, agrees the purpose with you and asks for the decisions only you can make. Get started walks through each step, including Cursor and Codex.
Documentation
- Working with the agent: the purpose statement, your decisions and the review.
- Use the result: load the graph into Neo4j or query it in SQLite.
- Your project: what to commit and how to rebuild after new data.
- CLI reference.
Contribute
See CONTRIBUTING.md. Report problems through GitHub issues.
Typed authoring and modular topology construction were informed by Paul Ka Po To's kg-build-system. Biotope does not depend on that engine.
Copyright © 2025–2026 BioCypher Team. Apache 2.0.
Metadata
Release files for biotope 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| biotope-1.0.0.tar.gz | 529.6 kB | With provenance | Details for biotope-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| biotope-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for biotope-1.0.0-py3-none-any.whl |
Total release size: 797.2 kB
Release files / biotope-1.0.0.tar.gz
| Download URL | biotope-1.0.0.tar.gz |
|---|---|
| Size | 529.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e0030a6950ae002948e3657792c740fb5157f3a46804b0a91e590a59f8c07611
|
|
BLAKE2b-256 checksum How to use checksums |
8b9bc7754bfbea001dd10196c974de5178e727c8ae5d831fa35461887c6e8053
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / biotope-1.0.0-py3-none-any.whl
| Download URL | biotope-1.0.0-py3-none-any.whl |
|---|---|
| Size | 267.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
889bdd06a273b8d8011b76e1cd185a558042504f02426c20002d464859fcec92
|
|
BLAKE2b-256 checksum How to use checksums |
75e7fa805def2dac5af646da80851a386a2fd7c0c3dbf17cd8096b0e6bc2ed58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logSecurity for biotope 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for biotope-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.