Builders
Everything you need to integrate ERC-8170 into your project.
Why integrate ERC-8170?
Standard interface
One identity primitive across all Ethereum-compatible chains. No proprietary lock-in.
Composable stack
Works with ERC-721, ERC-8171, ERC-4626, and ERC-4337 out of the box.
Two integration paths
AI-Native tokens for new projects. Registry binding for existing collections.
Integration patterns
AI-Native NFT (ANIMA)
The agent IS the NFT. Mint an ERC-8170 token, the agent generates its own EOA, gets a TBA, and starts earning certifications.
Registry-bound agent
Attach an agent to ANY existing ERC-721. No migration needed. The agent binds via the ERC-8171 registry (extends ERC-6551 pattern).
Clone distribution
Create agents and distribute clones. Each clone has its own identity but inherits lineage from the original.
Use cases
Personal AI companion
A persistent AI assistant with portable identity. Change devices, switch platforms, keep the same agent.
Agent-based vault operator
An AI fund manager with on-chain track record. ERC-4626 vault integration with verifiable agent identity.
Enterprise assistant identity
Company-owned agents with clear certification trails. Transfer between departments, audit on-chain.
Research agent lineage
Lab director spawns specialists. Track which agents came from which, what they know, and how they evolved.
Licensed branded agent
An agent carrying brand identity on-chain. Certifications and permissions define what the holder can do.
NFT-bound reputation
Agent earns SBT certifications via AgentCert. Reputation follows the identity, not the platform.
Resources
Key contracts (Pentagon Chain)
| Contract | Address | Type |
|---|---|---|
| AINFT Genesis | 0x4e8D...172d Explorer ↗ | ERC-8170 Token |
| AINFTRegistry | 0x3271...f486 Explorer ↗ | Agent Binding Registry |
| ATSBadge | 0x8342...738d Explorer ↗ | Agent Trust Score (SBT) |