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

# Agreement templates

Reusable legal-instrument templates live in the [`/templates`](https://github.com/MetaLex-Tech/cybercorps-contracts/tree/develop/templates) directory and are pre-registered in `CyberAgreementRegistry`.

## cyberSAFE

| Template                                                  | Style                | Filing path         |
| --------------------------------------------------------- | -------------------- | ------------------- |
| `MetaLeX cyberSAFE US style Reg D v 1.0.md`               | YC post-money        | Reg D (US)          |
| `MetaLeX cyberSAFE UK Cayman style Reg S v 1.0.md`        | YC post-money        | Reg S (UK / Cayman) |
| `MetaLeX cyberSAFE jx-neutral-style Reg D raise v 1.0.md` | Jurisdiction-neutral | Reg D (US)          |
| `MetaLeX cyberSAFE jx-neutral-style Reg S raise v 1.0.md` | Jurisdiction-neutral | Reg S               |
| `mlx_safe_reg_d_v1_3.md` / `mlx_safe_reg_s_v1_3.md`       | v1.3 series          | Reg D / Reg S       |

## cyberSAFT

| Template                                            | Filing path |
| --------------------------------------------------- | ----------- |
| `MetaLeX cyberSAFT reg D v.1.0.md`                  | Reg D       |
| `MetaLeX cyberSAFT Reg S raise v 1.0.md`            | Reg S       |
| `mlx_saft_reg_d_v1_3.md` / `mlx_saft_reg_s_v1_3.md` | v1.3 series |

## cyberSAFTE

* `mlx_safte_reg_d_v1_3.md` — Reg D, v1.3.

## cyberTokenWarrant

| Template                                                                      | Filing path              |
| ----------------------------------------------------------------------------- | ------------------------ |
| `MetaLeX cyberTokenWarrant a16z US style reg D v 1.0.md`                      | a16z-derived, Reg D (US) |
| `MetaLeX cyberTokenWarrant a16z jx-neutral-style-issuer Reg D raise v 1.0.md` | jx-neutral, Reg D        |
| `MetaLeX cyberTokenWarrant a16z-jx-neutral-style-issuer Reg S raise v 1.0.md` | jx-neutral, Reg S        |
| `MetaLeX cyberTokenWarrant non-US Reg S v 1.0.md`                             | Reg S                    |
| `mlx_safe_tw_reg_d_v1_3.md` / `mlx_safe_tw_reg_s_v1_3.md`                     | v1.3 series              |

## MetaDAO Futarchy Governance SPC

* `MetaDAO Futarchy Governance SPC - Board Consent - Approval of SegCo v 1.0.md`
* `MetaDAO Futarchy Governance SPC - SegCo combined v 1.0.md`

## LeXcheX agreement

* `MetaLeX LeXCheX Agreement.md` — countersigned by a credential subject when receiving a LeXcheX credential.

## Custom templates

Issuers can register their own templates with `CyberAgreementRegistry.registerTemplate(...)`. For example, the `Three Prime Custom cyberSAFE and cyberTokenWarrant.md` template demonstrates a custom variant.

## See also

* [How-to: Sign a cyberAgreement](/metalex-docs/protocol-how-to-guides/sign-a-cyberagreement.md)
* [`CyberAgreementRegistry`](/metalex-docs/protocol-reference/contracts/cyberagreementregistry.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://gabriel-j-shapiro.gitbook.io/metalex-docs/protocol-reference/templates.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.