Skip to main content
A universe starts empty. The marketplace stocks it: nodes for OpenAI, Airtable, Slack and AWS, the design system your components render from, and skills your Agents can use. Everything you install writes a row into your own universe’s database. Take what you need, one package at a time.

​
Before you begin

Your universe is running, and you can reach it in a browser.
1

Open the Marketplace

Open your universe, choose studio in the header, then the marketplace tile.The Marketplace open in Studio, with the search box and the category gridInstalled sits beside it, counting what this universe already holds.Browse by category, or search. Search is semantic rather than substring, so describe the job: β€œtranscribe a call” finds the nodes that do it, whatever they are named.
2

Add a package

Open a category. It lists every package in it, expanded to show the nodes each one holds. Three counts sit above the list: packages, nodes, and how many you have already added.The AI category, listing the OpenAI package and its nodesA package is a set of nodes that belong together, such as everything that talks to OpenAI. Click Add and it writes a row per node into your universe.A package row with its Add buttonThe nodes register straight away and appear in the node library in canvas, ready to drag onto a workflow. Nothing restarts, and the button reads Added once they are yours.Add OpenAI now. The next challenge uses OpenAI Stream to build your first Agent.
3

Install the design system

The design system is chosen rather than assumed. A new universe has no components, atoms or styles until you take it. Its card sits in the catalogue grid alongside the node categories. Click Install.Do this before the components challenge. Without it, there is nothing to render.
4

Add credentials where required

Some nodes talk to external services and name the credential they need. Add it in canvas under Credentials. The next challenge walks through this for your OpenAI key.
5

Stay current

The Installed tab carries a badge counting the items whose published version has moved on from the one you hold. Open it and click Update on any of them, or Remove to give one back. An item reading on disk is a local definition of your own, which no row can update.
Installing writes rows into the database of the universe you are in, so what you install in one stays there. Production is its own universe with its own database, so install there too. Nothing rides unoverse deploy, which moves platform images only.

​
Next steps

Create your first Agent

Wire a trigger, a model, and a response together in canvas, and talk to it.

Create your first node

Need something the marketplace does not have? Build it.