How do users, Agents and tokens relate?
A user account identifies a participant, a wallet authorizes asset actions, a Creator Passport describes a creator identity, an Agent represents a workflow, and a token is a separately identified on-chain asset. Linking these records does not make them interchangeable.
Who this is for
Creators designing an Agent or associating a token with their identity.
Follow the identifiers
Confirm the account, wallet address, creator profile, Agent identifier and token contract separately. Public social details are not proof of control over a wallet or contract.
Official and community labels
Official creator selection requires the applicable verified Passport binding. Entering a social handle in a launch form does not establish verification. Community-issued assets must retain their distinct label.
Permissions remain explicit
An Agent profile or linked token does not grant spending rights. Read, prepare and execution capabilities have separate boundaries; wallet approval remains necessary where an executable path requires it.
Does buying a token control the Agent?
Do not assume ownership, governance or revenue rights from the association. Such rights require explicit asset-specific terms and an implemented mechanism.
Build configuration reference
Configuration is not live verification. Provider approval, permissions and receipts must be checked separately. These pages do not run wallet code.
| Feature | Availability & scope |
|---|---|
| Agent workbench | Flag on · verify execution |
| Agent creation surface | Flag on · verify execution |
Source references
- web/kolmarket-pc/src/pages/module-creator-launch-v3/launchIdentity.ts
- plugins/kolmarket-codex/skills/kolmarket/SKILL.md