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

# Protocol — Reference

- [Overview](https://docs.metalex.tech/protocol-reference/reference.md): The dry facts: contract APIs, roles, events, and deployments
- [Core contracts](https://docs.metalex.tech/protocol-reference/contracts.md): What each core contract does and how the suite fits together
- [CyberCorp](https://docs.metalex.tech/protocol-reference/contracts/cybercorp.md)
- [IssuanceManager](https://docs.metalex.tech/protocol-reference/contracts/issuancemanager.md): The issuance authority: printers, cyberCERTs, scrip, security classes, secondary transfers
- [LedgerEntryToken (CyberCertPrinter)](https://docs.metalex.tech/protocol-reference/contracts/ledgerentrytoken.md): The ERC-721 register of cyberCERTs (formerly CyberCertPrinter)
- [CyberScrip](https://docs.metalex.tech/protocol-reference/contracts/cyberscrip.md)
- [CyberShares](https://docs.metalex.tech/protocol-reference/contracts/cybershares.md)
- [DealManager](https://docs.metalex.tech/protocol-reference/contracts/dealmanager.md): Deal lifecycle and the secondary-trading venue with settlement escrow
- [RoundManager](https://docs.metalex.tech/protocol-reference/contracts/roundmanager.md): Multi-investor fundraising rounds with escrowed officer signatures
- [LeXscroWLite](https://docs.metalex.tech/protocol-reference/contracts/lexscrowlite.md)
- [CyberAgreementRegistry](https://docs.metalex.tech/protocol-reference/contracts/cyberagreementregistry.md)
- [SafeCertificateConverter](https://docs.metalex.tech/protocol-reference/contracts/safecertificateconverter.md)
- [LexChex / LeXcheXBadge / LexChexMinter](https://docs.metalex.tech/protocol-reference/contracts/lexchex.md)
- [CertificateUriBuilder](https://docs.metalex.tech/protocol-reference/contracts/certificateuribuilder.md)
- [Factories](https://docs.metalex.tech/protocol-reference/factories.md)
- [Certificate extensions](https://docs.metalex.tech/protocol-reference/extensions.md): Certificate and corp extensions: per-security-type data and JSON rendering
- [Hooks](https://docs.metalex.tech/protocol-reference/hooks.md)
- [Conditions](https://docs.metalex.tech/protocol-reference/conditions.md): Condition contracts that gate state transitions, including the secondary-trading family
- [Access control (BorgAuth)](https://docs.metalex.tech/protocol-reference/access-control.md): BorgAuth numeric authority levels and who can call what
- [Upgrade model](https://docs.metalex.tech/protocol-reference/upgrade-model.md)
- [Agreement templates](https://docs.metalex.tech/protocol-reference/templates.md)
- [Security types](https://docs.metalex.tech/protocol-reference/security-types.md)
- [Deployments](https://docs.metalex.tech/protocol-reference/deployments.md): Deployed addresses and versions per chain
- [Glossary](https://docs.metalex.tech/protocol-reference/glossary.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.metalex.tech/protocol-reference.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.