How it works
Three primitives. Every record lives on Solana — no off-chain database, no signed-message theater.
Pick a subdomain like myagent.alice.sol. One transaction creates the SNS subdomain and writes the agent's signing key + endpoint into records v2.
Try the wizardAnyone issues a fresh nonce; the agent signs it; the signature is checked against the on-chain agent.signing-pubkey. Tamper a byte → instant ✗.
Watch the handshakeStructured grants on-chain: target program, spend cap per period, expiry. Burn the parent .sol → every sub-agent loses authority in the same block.
See permission editorLive agents on devnet
Real on-chain SNSIP-Agent records v2 — fetched live as you read this.
Resolve any .sol
Paste any Solana name. We render the owner and SNSIP-Agent records v2 live from devnet.
swap-bot.solWhy this matters
Every AI agent on Solana today is just a private key. No name. No rules. No audit trail. If that key gets compromised, there is no on-chain way to stop the agent. SNSIP-Agent is the identity layer that fixes this — a .solname carries the agent's signing key, endpoint, structured permissions (target program, spend cap, period, expiry), and reputation events. Anchor programs for Identity / Reputation / Validation are sketched in the repo; the MagicBlock Ephemeral Rollups integration handles sub-50ms agent-to-agent settlement.