# MetaLeX Docs

## Docs

- [Welcome](https://docs.metalex.tech/readme.md): Private securities recorded as Ledger Entry Tokens, anchored in each issuer's governing law, and the MetaLeX apps that run on them.
- [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
- [Formation packets and signing](https://docs.metalex.tech/using-the-apps/formation/formation-packets.md): Prepare founder documents, invite signers, collect signatures and connect the completed packet to issuance
- [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): Choose public, private, email, offchain or mixed signing and track the evidence each flow produces
- [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
- [Overview](https://docs.metalex.tech/how-cybercorps-works/explanation.md): Why the protocol is designed as it is, what it relies on in law, and how far MetaLeX's control over a deployed company reaches.
- [Constitutive vs. pointer tokenization](https://docs.metalex.tech/how-cybercorps-works/constitutive-vs-pointer.md): Why a cyberCORP's onchain records can be its legal securities ledger, and what the company's governing documents must say for that to be true.
- [Ledger Entry Tokens and scrip](https://docs.metalex.tech/how-cybercorps-works/lets-and-scrip.md): How a Ledger Entry Token records a holding on the register, how scrip trades apart from it, and where the two meet.
- [Legal mappings across jurisdictions](https://docs.metalex.tech/how-cybercorps-works/legal-mappings.md): Which statutes and governing documents anchor the onchain register for Delaware corporations and LLCs, Cayman and BVI entities, English companies and funds.
- [Compliance architecture](https://docs.metalex.tech/how-cybercorps-works/compliance-architecture.md): Where compliance runs: condition contracts on every legally significant transition, the credentials they read, and the point where scrip becomes a Ledger Entry Token again.
- [Upgrades and what MetaLeX controls](https://docs.metalex.tech/how-cybercorps-works/upgrades-and-control.md): What MetaLeX can and cannot do to a cyberCORP: published implementations, opt-in upgrades, fees, templates, shared contracts, and the owner role the deploying factory keeps.
- [Composability and DeFi](https://docs.metalex.tech/how-cybercorps-works/composability.md): What scrip can do in AMMs, lending markets and vesting contracts, and what its transfer restrictions and compliance powers cost in integrations.
- [Regulatory context](https://docs.metalex.tech/how-cybercorps-works/regulatory-context.md): The US exemptions and SEC staff statements the protocol is built around, and what lies outside it. Not legal advice.
- [Guides](https://docs.metalex.tech/building-on-the-protocol/how-to.md): What developers can build on the cyberCORPs contracts, which contracts each MetaLeX product uses, and the order to read the guides in
- [Incorporate a cyberCORP](https://docs.metalex.tech/building-on-the-protocol/how-to/incorporate-a-cybercorp.md): Deploy a cyberCORP and its contract suite, create a LET contract for its common stock, and issue the founder's first Ledger Entry Token
- [Run a cyberRAISE round](https://docs.metalex.tech/building-on-the-protocol/how-to/run-a-cyberraise-round.md): Create a SAFE round on a cyberCORP, take an investor's Expression of Interest, allocate it and close the round
- [Issue a LET](https://docs.metalex.tech/building-on-the-protocol/how-to/issue-a-let.md): Create a LET contract for a security class and series and issue Ledger Entry Tokens from it
- [Configure BorgAuth roles](https://docs.metalex.tech/building-on-the-protocol/how-to/configure-roles.md): Add and remove officers, set BorgAuth levels directly, and transfer or renounce ownership of a cyberCORP's ACL
- [Restrict scrip and LET transfers](https://docs.metalex.tech/building-on-the-protocol/how-to/restrict-transfers.md): Install transfer-restriction hooks on scrip and LETs, use or permanently disable scrip compliance powers, and cap scrip holders
- [Gate state transitions with conditions](https://docs.metalex.tech/building-on-the-protocol/how-to/gate-with-conditions.md): Attach condition contracts to scripification, rounds, deals and secondary settlement, and write a custom condition
- [Run a secondary trade](https://docs.metalex.tech/building-on-the-protocol/how-to/run-a-secondary-trade.md): Post, accept and finalize a secondary offer on a cyberCORP's DealManager under an exemption pathway
- [Scripify and settle a secondary trade](https://docs.metalex.tech/building-on-the-protocol/how-to/scripify-and-settle.md): Turn part of a LET into scrip, trade the scrip, and convert it back into a LET in the buyer's name
- [Convert SAFEs to equity](https://docs.metalex.tech/building-on-the-protocol/how-to/convert-safe-to-equity.md): The intended SafeCertificateConverter flow for converting SAFE LETs into equity in a priced round; the converter is a stub
- [Sign a cyberAgreement](https://docs.metalex.tech/building-on-the-protocol/how-to/sign-a-cyberagreement.md): Register a template, create a multi-party agreement, collect EIP-712 signatures and finalize or void it in the CyberAgreementRegistry
- [Integrate from a frontend](https://docs.metalex.tech/building-on-the-protocol/how-to/integrate-from-frontend.md): Read and write the cyberCORPs contracts from a TypeScript or React app, build EIP-712 signatures, and pick the right ABI for v4 and v5 companies
- [Upgrade a cyberCORP](https://docs.metalex.tech/building-on-the-protocol/how-to/upgrade-a-cybercorp.md): Move an existing cyberCORP to v5 by upgrading its four proxies and two beacons together, then backfill and open its LET contracts
- [Deploy a PumpCorp for ACE](https://docs.metalex.tech/building-on-the-protocol/how-to/deploy-pumpcorp-ace.md): Deploy a cyberCORP and its ACE round in one transaction through PumpCorpFactory
- [Deploy a MetaDAO SPC](https://docs.metalex.tech/building-on-the-protocol/how-to/deploy-metadao-spc.md): Deploy a futarchy-governed Cayman segregated portfolio company and its SegCos through MetaDAOFactory
- [Deploy a LiquiLeX pool](https://docs.metalex.tech/building-on-the-protocol/how-to/deploy-liquilex-pool.md): Pair a company's scrip against a stablecoin in a Uniswap v4 pool with MetalexIssuerFeeHook, under a whitelisted or open compliance model
- [Reference](https://docs.metalex.tech/building-on-the-protocol/reference.md): Contract APIs, roles, events and deployed addresses
- [Core contracts](https://docs.metalex.tech/building-on-the-protocol/reference/contracts.md): What each core contract does and how the suite fits together
- [CyberCorp](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/cybercorp.md)
- [IssuanceManager](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/issuancemanager.md): The issuance authority: LET contracts, LETs, scrip, security classes and secondary transfers
- [LedgerEntryToken](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/ledgerentrytoken.md): The LET contract, the ERC-721 that mints and registers a series' Ledger Entry Tokens (LETs)
- [CyberScrip](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/cyberscrip.md)
- [CyberShares](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/cybershares.md)
- [DealManager](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/dealmanager.md): Primary deals and the secondary-trading venue with settlement escrow
- [RoundManager](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/roundmanager.md): Multi-investor fundraising rounds with escrowed officer signatures
- [LeXscroWLite](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/lexscrowlite.md)
- [CyberAgreementRegistry](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/cyberagreementregistry.md)
- [ZKPassportFinalizer](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/zkpassportfinalizer.md)
- [SafeCertificateConverter](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/safecertificateconverter.md)
- [LexChex / LeXcheXBadge / LeXcheXMinter](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/lexchex.md)
- [CertificateUriBuilder](https://docs.metalex.tech/building-on-the-protocol/reference/contracts/certificateuribuilder.md)
- [Factories](https://docs.metalex.tech/building-on-the-protocol/reference/factories.md)
- [Certificate extensions](https://docs.metalex.tech/building-on-the-protocol/reference/extensions.md): Certificate and corp extensions: per-security-type data and JSON rendering
- [Hooks](https://docs.metalex.tech/building-on-the-protocol/reference/hooks.md)
- [Conditions](https://docs.metalex.tech/building-on-the-protocol/reference/conditions.md): Condition contracts that gate state transitions, including the secondary-trading family
- [Access control (BorgAuth)](https://docs.metalex.tech/building-on-the-protocol/reference/access-control.md): BorgAuth numeric authority levels and who can call what
- [Upgrade model](https://docs.metalex.tech/building-on-the-protocol/reference/upgrade-model.md)
- [Agreement templates](https://docs.metalex.tech/building-on-the-protocol/reference/templates.md)
- [Security types](https://docs.metalex.tech/building-on-the-protocol/reference/security-types.md)
- [Deployments](https://docs.metalex.tech/building-on-the-protocol/reference/deployments.md): Deployed addresses and versions per chain
- [Glossary](https://docs.metalex.tech/building-on-the-protocol/reference/glossary.md)
- [Documentation status and source review](https://docs.metalex.tech/building-on-the-protocol/reference/documentation-status.md): Dated source revisions, prior documentation updates, changes covered and verification limits


---

# 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
This site has an agentic ask interface you may use to query the documentation dynamically 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/index.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.