An ensurance group is an onchain namespace that organizes agents under a shared mandate. Creating one takes about 5 minutes through two different paths: apply (free, reviewed) or permissionless (instant, costs ETH).
tl;dr
To create a group:
- Go to /groups/create
- Choose Apply (free, reviewed by team) or Permissionless (instant, ~10 ETH)
- Enter your group name (becomes
.yourname) - Add display name, tagline, and description
- Submit application or confirm transaction
Your group is a namespace. After creation, you can mint agents inside it.
understanding what you are creating
Before you begin, know what a group is and is not:
| A Group Is | A Group Is Not |
|---|---|
A namespace (like .basin) | A vault or pool |
| A contract you own | A shared wallet |
| A category for agents | An agent itself |
| A coordination layer | A funding mechanism |
Groups organize agents. Agents hold assets and do things.
When you create .mygroup, you can then mint agents like water-project.mygroup or local-steward.mygroup. Each agent gets its own tokenbound account (wallet) to hold assets.
step 1: choose your path
Go to /groups/create. You will see two options:
option a: apply (recommended for most users)
Cost: Free Time: 1-3 business days for review Requirements: Email address
The apply path is curated. The ensurance team reviews applications to ensure alignment with the protocol mission. Approved groups are created at no cost.
Best for:
- Organizations new to the ecosystem
- Groups that want onboarding support
- Those who prefer curation over speed
option b: permissionless
Cost: ~10 ETH (set by the SITUS Factory contract) Time: Instant (one transaction) Requirements: Connected external wallet with sufficient ETH
The permissionless path requires no approval. Pay the factory fee, sign the transaction, and your group exists onchain immediately.
Best for:
- Experienced web3 users
- Time-sensitive launches
- Full autonomy from day one
step 2: name your group
Your group name becomes your namespace. Choose carefully—it cannot be changed after creation.
Format: .yourname (lowercase, alphanumeric, hyphens allowed)
Examples:
.watershed→ for agents likeupper-colorado.watershed.regen→ for agents likesoil-carbon.regen.localcoop→ for agents likemember-001.localcoop
Tips for naming:
- Keep it short and memorable
- Consider what agents inside will be named
- Check availability before committing (the form shows this automatically)
- Avoid trademarked terms
step 3: add metadata
Optional but recommended:
| Field | Purpose | Example |
|---|---|---|
| Display Name | Human-readable name | "Ogallala Aquifer Network" |
| Tagline | Short description | "Protecting the High Plains aquifer system" |
| Description | Longer context | Mission, goals, membership info |
| Website | External link | Your organization URL |
This metadata appears on your group page and helps others understand what your group is about.
step 4: configure agent settings (permissionless only)
If using the permissionless path, you set two additional options:
Agent Price — How much (in ETH) others must pay to mint agents in your group
- Set to
0for free agent creation - Set higher to gate membership
- You can change this later
Public Minting — Whether anyone can create agents, or only you
- Enable for open communities
- Disable if you want to control who can mint
step 5: submit
for apply path:
- Connect your email through Privy
- Fill out the form
- Click "Submit Application"
- Wait for review email (1-3 days)
- Once approved, your group is created
for permissionless path:
- Connect your external wallet (not embedded)
- Fill out the form
- Click "Create Group"
- Confirm the transaction in your wallet
- Wait for transaction confirmation
- Your group exists immediately
what happens after creation
Once your group exists:
- View your group at
/groups/yourname - Mint agents at
/groups/yourname/create(once available) - Configure settings through the group contract
- Appear in the ecosystem on
/groupsand in agent discovery
next steps for new groups:
| Action | Why It Matters |
|---|---|
| Create your first agent | Agents are where assets and activity happen |
| Add group imagery | Orb and banner images appear throughout the app |
| Configure proceeds routing | Define how value flows to your group |
| Invite members | Others can mint agents if public minting is enabled |
frequently asked questions
can I change my group name after creation?
No. Group names are permanent onchain identifiers. Choose carefully.
what is the difference between a group and an agent?
A group is a namespace (like .basin). An agent is an account inside that namespace (like elk.basin). Groups organize agents; agents hold assets and execute actions.
why does permissionless creation cost ETH?
The fee prevents namespace squatting and ensures commitment. It also supports protocol development. The fee is set by the SITUS Factory contract and may change.
can I create agents immediately after my group exists?
Yes. Once your group contract is deployed, you can mint agents into it. Each agent gets its own tokenbound account.
who controls a group?
The group creator (owner) controls the contract. They can set pricing, enable/disable minting, update metadata, and transfer ownership.
can multiple people manage a group?
Currently, groups have a single owner address. For shared management, the owner could be a multisig wallet or DAO.
technical details
For developers and advanced users:
Contract: Groups are created through the SITUS Factory at 0x67c814835e1920324634fd6da416a0e79c949970 on Base.
Standard: Each group is an ERC-721 contract. Agents minted inside are ERC-721 tokens with ERC-6551 tokenbound accounts.
Resolver: Group names resolve through the SITUS Resolver at 0x30EF3151Ca370562F25ea6F3611fEFD70B5a93df.
Chain: Groups exist on Base (Chain ID 8453).
ready to create?
Explore existing groups for inspiration →