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

# Citing Biodock

*What you'll get: a citation to copy into your paper or reference manager.*

## Cite Biodock

If you used Biodock for annotation, analysis or prediction in a paper or presentation, please cite it. Use the year you used Biodock:

```
Biodock, AI Software Platform. Biodock 2026. Available from www.biodock.ai.
```

For a reference manager, paste this BibTeX entry and change the year if needed:

```bibtex
@misc{biodock,
  author       = {{Biodock}},
  title        = {Biodock, AI Software Platform},
  year         = {2026},
  howpublished = {\url{https://www.biodock.ai}}
}
```

## Cite the models you ran

* **Your own model**: name the project and the model version you ran, as they appear in the app.
* **Structure prediction**: also cite the co-folding model you ran, such as Boltz-2, Chai-1, Protenix or OpenFold3, following that model's own citation guidance. Each prediction's page shows which model made it.

## Academic accounts and papers

Academic accounts are for non-commercial work only. Papers that include significant authorship from a commercially affiliated author generally require a paid account. See [Academics and startups](https://docs.biodock.ai/about/academics-and-startups.md).

## A Biodock co-author

In most cases we're happy to help write a methods section, with a Biodock co-author, at no charge. Email <support@biodock.ai> to ask.


---

# 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.biodock.ai/about/citing-biodock.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.
