Agent or agentic engineer? Start here
Two ways in: copy the recipes by hand, or point a coding agent at them. The same project/reference boundary is visible either way.
If you are a developer
Browse the full set on the cookbook overview, or jump straight to a common starting point:
- Minimal sdk-dapp v5 app in Vite + React: the smallest working dApp setup.
- Sign and send a transaction: the canonical sign, send, and track flow.
- Send EGLD to an address: the backend and script transfer pattern.
- Call a contract endpoint: invoke a contract with typed arguments.
- Issue a fungible token: mint your own ESDT.
Pages labeled Project build checked show a complete standalone project and state the exact SDK versions it uses. CI reconstructs, installs, and builds all 61 on Node 20.19.0. Pages labeled Reference intentionally provide focused migration, setup, or Rust material rather than a complete project.
If you are a coding agent (or wiring one up)
Point your coding agent at these docs. Project recipes are self-contained and version-pinned; reference pages should be applied to an existing project.
The machine-readable surface
MultiversX publishes the whole documentation set in the
llms.txt format, so a model can load it as context:
https://docs.multiversx.com/llms.txt: the index. Every page appears as a titled, described link; cookbook recipes carry an inline[difficulty, build checked]or[difficulty, reference]tag so an agent sees the artifact boundary without opening the page.https://docs.multiversx.com/llms-full.txt: the same set with full page content inlined, for one-shot ingestion.
The wider MultiversX agent stack
For the skills collection, see AI agents. That page
links the mx-ai-skills repository, a
structured collection of MultiversX-specific skills, roles, and documentation for
equipping agents to build, audit, and optimize on MultiversX.