Developer docs
Build NFT-bound agents with Dappa
Register Adapter8004 agents, download agent skills, and set up whitelabeled Juno agents for NFT collections.
Quickstart
Register an NFT as an agent
Adapter8004 gives any ERC-721, ERC-1155, or ERC-6909 token an agent record. Dappa presents real and counterfactual registrations as one record per NFT, with a counterfactual flag until a real ERC-8004 registration overrides it.
- 01
Choose the NFT binding
Start from the collection chain, token contract, token ID, and token standard. The NFT is the durable identity; Adapter8004 adds the agent URI, metadata, and optional wallet layer on top.
- 02
Pick the registration path
Use a real registration when the caller controls the NFT and can mint the ERC-8004 identity now. Use a counterfactual registration when a project wants to stage the same NFT-agent binding before the holder claims.
- 03
Write the agent record
Real registrations call register, then update by agentId. Counterfactual registrations call counterfactualRegister, then update by the token tuple. Both paths describe one unified Dappa agent record for the NFT.
- 04
Upgrade when ready
Counterfactual is not a different product. It is the lighter registration path, and later the holder can carry the staged URI, metadata, and wallet into a full ERC-8004 record to make the agent more onchain.
Contract reference
Adapter8004 contract documentation
Use Adapter8004.xyz for the canonical contract overview, then use the skills below for Dappa-specific chain addresses, API lookups, metadata conventions, and registration examples.
Skills
Downloadable SKILL.md files
These are the same agent skills previously listed on /skills. Their direct download routes stay stable for agents and scripts.
Adapter8004 Agent Skill
adapter8004-agent
Register and manage onchain agents via Adapter8004 — chains, addresses, real vs counterfactual, write functions, the reserved agent-binding key, and viem examples.
Download SKILL.mdDappa API Skill
dappa-api
Query the Dappa public indexer API — base URL, REST endpoints, recordType semantics, cursor pagination, by-collection/by-token lookups, and response examples.
Download SKILL.md
Whitelabeled agents
Create Juno agents for any NFT collection
NFT projects can use Dappa as the control plane for branded agent signup. The collection keeps its visual identity while Dappa handles project configuration, Adapter8004 registration, and the hosted public-agent runtime path described in the plan.
- 1
Project verifies collection ownership or an approved admin path in Dappa.
- 2
Dappa stores project copy, theme, collection profile, and whitelabel signup configuration.
- 3
Collectors choose an agent template, create or select a Juno endpoint, and bind it to their NFT through the real or counterfactual Adapter8004 path.
- 4
The hosted public agent exposes REST-AP surfaces such as /.well-known/restap.json, /talk, and /mcp while the collection experience keeps the project brand.