Skill

morph-identity

Registers AI agent identities on Morph Mainnet per EIP-8004, queries metadata/wallets/reputation, submits/reads feedback via Python CLI commands.

Python

ai-ml

cli-tools

npx claudepluginhub morph-l2/morph-skill --plugin morph-skill

Tool Access

This skill uses the workspace's default tool permissions.

Preview

> EIP-8004 agent identity and reputation on **Morph Mainnet** (Chain ID: 2818).

SKILL.md

Similar Skills

molt-registry

586

Verifies agent identities, registers permanent on-chain IDs, looks up metadata, and rates reputation via Moltbook Registry on Base blockchain. For sovereign agent interactions.

3 files

sundial-org-awesome-openclaw-skills-4

starknet-identity

Registers and manages AI agent identities on Starknet using ERC-8004: NFT-based registration, reputation via feedback, third-party validations.

1 file6 tools

starknet-agentic-skills

erc-8004

Implements ERC-8004 for registering AI agents on EVM chains, managing on-chain identity, reputation, validation, and discovery with Agent0 TypeScript SDK.

8 files

tenequm-skills

Stats

Stars6

Forks1

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Morph Identity — AI Agent Skill

EIP-8004 agent identity and reputation on Morph Mainnet (Chain ID: 2818). All commands output JSON. On-chain via bundled ABIs — no external API keys required.

Activation Triggers

Use this skill when the user wants to: register an agent identity, query agent metadata or wallet, check agent reputation, submit feedback for an agent, or read agent reviews.

Quick Start

pip install requests eth_account eth_abi eth_utils

# Run from repository root
python3 scripts/morph_api.py <command> [options]

No API keys required. Talks directly to Morph RPC using bundled ABI files.

BGW Routing Note

Decide the mode once via the root SKILL.md and docs/social-wallet-integration.md.

This skill owns Morph-side identity and reputation logic.
agent-register and agent-feedback require --private-key (local signing only).
Social Login Wallet users can use read commands (agent-wallet, agent-metadata, agent-reputation, agent-reviews) after resolving their address from BGW, but cannot execute identity writes through this skill today.
Keep BGW for wallet-layer concerns and use this skill for Morph protocol logic.

Agent ID Format

agent_id is a numeric ERC-721 token ID (e.g. 1, 42). It is returned by agent-register in the agent_id field of the JSON response. If the receipt was not parsed, use tx-receipt to inspect the Transfer event logs and extract the token ID.

Commands

`agent-register`

python3 scripts/morph_api.py agent-register --name "MorphBot" --agent-uri "https://example.com/agent.json" --metadata role=assistant,team=research --private-key 0xYourKey

# With altfee gas payment
python3 scripts/morph_api.py agent-register --name "MorphBot" --fee-token-id 5 --private-key 0xYourKey

`agent-wallet`

Read the payment wallet for an agent.

python3 scripts/morph_api.py agent-wallet --agent-id <agent_id>

`agent-metadata`

Read one metadata value by key.

python3 scripts/morph_api.py agent-metadata --agent-id <agent_id> --key name

`agent-reputation`

Read aggregated reputation and feedback count.

python3 scripts/morph_api.py agent-reputation --agent-id <agent_id> --tag1 quality

`agent-feedback`

Submit feedback for an agent. Scores are encoded with 2 decimals. Optionally pass --fee-token-id to pay gas via altfee.

python3 scripts/morph_api.py agent-feedback --agent-id <agent_id> --value 4.5 --tag1 quality --feedback-uri "https://example.com/review/1" --private-key 0xYourKey

# With altfee gas payment
python3 scripts/morph_api.py agent-feedback --agent-id <agent_id> --value 4.5 --fee-token-id 5 --private-key 0xYourKey

`agent-reviews`

Read all feedback entries for an agent.

python3 scripts/morph_api.py agent-reviews --agent-id <agent_id> --include-revoked

`agent-set-metadata`

Set a metadata key-value pair for an agent.

python3 scripts/morph_api.py agent-set-metadata --agent-id <id> --key "role" --value "assistant" --private-key 0xKey

`agent-set-uri`

Set or update the agent URI.

python3 scripts/morph_api.py agent-set-uri --agent-id <id> --uri "https://example.com/agent.json" --private-key 0xKey

`agent-set-wallet`

Bind an operational wallet to an agent. Requires the new wallet's private key for EIP-712 signing. The signed payload must match AgentWalletSet(agentId,newWallet,owner,deadline) on ERC8004IdentityRegistry, and the deadline must stay within the contract's 5 minute window.

python3 scripts/morph_api.py agent-set-wallet --agent-id <id> --new-wallet-key 0xNewKey --private-key 0xOwnerKey

`agent-unset-wallet`

Unbind the operational wallet from an agent.

python3 scripts/morph_api.py agent-unset-wallet --agent-id <id> --private-key 0xKey

`agent-revoke-feedback`

Revoke previously submitted feedback.

python3 scripts/morph_api.py agent-revoke-feedback --agent-id <id> --feedback-index 0 --private-key 0xKey

`agent-append-response`

Append an owner response to a feedback entry.

python3 scripts/morph_api.py agent-append-response --agent-id <id> --client 0xClientAddr --feedback-index 0 --response-uri "https://example.com/response" --private-key 0xKey

Safety Rules

Always confirm with the user before executing agent-register — show the name, URI, and metadata before signing.
Always confirm with the user before executing agent-feedback — show the target agentId, score, and tags before signing.
Always confirm with the user before executing write commands (agent-set-metadata, agent-set-uri, agent-set-wallet, agent-unset-wallet, agent-revoke-feedback, agent-append-response) — show the target agentId and updated fields before signing.
Private keys are used locally for signing only — never sent to any API.
Read-only commands (agent-wallet, agent-metadata, agent-reputation, agent-reviews) require no private key.

Domain Knowledge

EIP-8004 defines a standard for on-chain agent identity and reputation, enabling agents to register an identity (as an ERC-721 NFT), attach metadata, and receive feedback from other participants.
IdentityRegistry contract: default 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 (override via MORPH_IDENTITY_REGISTRY env var)
ReputationRegistry contract: default 0x8004BAa17C55a88189AE136b182e5fdA19dE9b63 (override via MORPH_REPUTATION_REGISTRY env var)
ABI files bundled under contracts/IdentityRegistry.json and contracts/ReputationRegistry.json
Network overrides: MORPH_RPC_URL, MORPH_CHAIN_ID
For Hoodi testnet, set all env vars to testnet values (see root SKILL.md)

Common Workflows

Register an agent and verify:

agent-register → agent-wallet → agent-metadata --key name

Check an agent's reputation:

agent-reputation → agent-reviews

Submit feedback for an agent:

agent-feedback --value 4.5 --tag1 quality → agent-reputation (verify updated)

Full agent lifecycle:

agent-register → agent-set-metadata → agent-set-uri → agent-set-wallet → x402-register (monetize)

Manage feedback:

agent-reviews (read all) → agent-revoke-feedback (retract) / agent-append-response (respond)

Register agent identity + enable payment collection (x402):

agent-register --name "MyAgent" --private-key 0xKey
  → note the agent_id and the wallet address used
  → x402-register --private-key 0xKey --save --name myagent
    (the same wallet address becomes the x402 payTo — agents can now pay you USDC)
  → x402-server --pay-to 0xWallet --price 0.001 --name myagent
    (expose a local paid HTTP endpoint for testing)

Cross-Skill Integration

Use balance (morph-wallet) to check ETH for gas before agent-register or agent-feedback.
Use tx-receipt (morph-wallet) to inspect transaction logs if agent-register times out before returning agent_id.
Use --fee-token-id on agent-register or agent-feedback if the user wants to pay gas with an alternative token.
If the wallet source is a BGW Social Login Wallet, use BGW to establish the wallet/signing context and use this skill for the Morph-side identity workflow.
morph-x402: after agent-register, use x402-register --save to register the agent wallet as an x402 payment recipient. Then use x402-server to expose a paid HTTP endpoint. Other agents can pay with x402-pay.