Agent discovery
Registration files let clients discover a token-bound agent profile and its public metadata path.
This page documents how Signalbound fits together: ERC-721 collection, sealed reveal, on-chain renderer, agent registration, and holder-gated tools.
Agent protocols are additional rails. They do not replace the NFT standard. The token remains the anchor for ownership, art, reveal state, and access decisions.
// renderer path
tokenURI(tokenId)
-> read reveal state
-> derive token DNA
-> load shared fragments
-> compose SVG
-> return base64 JSON
Registration files let clients discover a token-bound agent profile and its public metadata path.
The agent can be bound to the current token owner so control follows NFT ownership.
Trait reads can be exposed through an adapter without changing the ERC-721 collection contract.
Tool routes can require holder verification and clearance before returning protected results.
Public token pages remain sealed before reveal.
The stack separates art fragments, rendering, and ERC-721 ownership behavior.
Final trait combinations are not surfaced before the reveal seed is fixed.
After the target block is available, tokenURI resolves final SVG and traits.
Registration, token pages, Arena, and gated tools can use resolved agent data.
Original Signalbound art and project-generated token output are released for open reuse under the project's CCO rights layer. Third-party dependencies, wallets, marketplaces, providers, and protocols keep their own terms.