> 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/using-the-apps.md).

# Using the apps

- [Getting started](https://docs.metalex.tech/using-the-apps/webapp.md): Who the MetaLeX apps are for, how to sign in, which app does what, and what it costs
- [Form a company](https://docs.metalex.tech/using-the-apps/formation.md): Form an LLC or incorporate a C-Corp in the cyberCORPs app for a flat $1,000 in USDC, then keep its filings, mail and annual reports in one place
- [Run your company](https://docs.metalex.tech/using-the-apps/company.md): Bring an existing company onchain and run it in the cyberCORPs app: mission control, the Incorporation Hub, Documents, the public company page and v5 upgrades
- [Tokenization Hub](https://docs.metalex.tech/using-the-apps/company/tokenization-hub.md): Set up a company's security classes and series, issue Ledger Entry Tokens (LETs), enable scrip and approve de-scripification
- [The cap table](https://docs.metalex.tech/using-the-apps/company/captable.md): One cap table for tokenized and untokenized positions, with AI-assisted import, versioned legal terms, partial tokenization and LLC records
- [Cap table records, modeling and compliance](https://docs.metalex.tech/using-the-apps/company/captable-tools.md): Stockholder lists, 409A and Rule 701 records, tax trackers, token claims and scenario modeling beside a corporation's cap table
- [Token grants and onchain vesting](https://docs.metalex.tech/using-the-apps/company/grants.md): Equity awards with onchain vesting, covering options, RSUs and restricted stock escrowed through MetaVesT
- [The boardRoom](https://docs.metalex.tech/using-the-apps/company/boardroom.md): Officers, directors, governance documents and board consents for a cyberCORP
- [cyberSign](https://docs.metalex.tech/using-the-apps/cybersign.md): Propose, review, sign and countersign agreements in MetaLeX's signing app
- [cyberRAISE](https://docs.metalex.tech/using-the-apps/cyberraise.md): Run a raise as an issuer or invest in one, from the first draft to the issued security
- [ACE](https://docs.metalex.tech/using-the-apps/ace.md): Raise from a token community with a SAFE priced in its token, inside cyberRAISE
- [For holders: your securities](https://docs.metalex.tech/using-the-apps/holders.md): My holdings, LET pages and PDFs, transfers, scripify, conversion back from scrip and private sale drafts, from the holder's side
- [Your profile](https://docs.metalex.tech/using-the-apps/profile.md): Your MetaLeX identity, linked wallets, visibility settings, notifications and Safe signing delegation
- [LeXcheX](https://docs.metalex.tech/using-the-apps/lexchex.md): Prove accredited-investor status onchain without revealing your balances
- [Launchpads: MetaDAO and Umia](https://docs.metalex.tech/using-the-apps/launchpads.md): Form the entity a MetaDAO or Umia launch prescribes, and browse the companies each launchpad has formed


---

# 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.metalex.tech/using-the-apps.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.