​

Agent Skill Instructions

When an AI agent connects to the Cred Protocol MCP server, it automatically receives the following instructions during initialization. These guide the agent on tool selection, score interpretation, and best practices.

---

​

When to Use These Tools

Use Cred Protocol tools when users ask about:

• Wallet creditworthiness, trust, or risk assessment
• Financial health or portfolio analysis of an Ethereum address
• Identity verification or attestation checks
• Sybil detection (is this a real person or a bot?)
• DeFi lending eligibility or underwriting decisions
• Comparing multiple wallets or batch assessments
• Transaction flow and counterparty analysis
• AI agent discovery, reputation, or on-chain registration

​

Tool Selection Guide

Start here — pick the right tool for the job:

​

Escalation Patterns

Wallet assessment (most common): Deep dive on a wallet:

1. get_credit_score for the headline number
2. get_comprehensive_report for the full multi-chain breakdown
3. get_sybil_score if trust/humanity is in question
4. get_transaction_graph to visualize the wallet’s network

Agent reputation workflow:

1. search_agents or list_agents to find the agent
2. get_agent to confirm details
3. get_agent_reputation to read existing on-chain feedback
4. submit_agent_reputation to add new feedback (costs 10 CU, async)
5. get_reputation_status to track the on-chain submission

​

Authentication

All tools require a CRED_API_KEY to access the live Cred Protocol API. All responses include source: "live" indicating real on-chain data.

​

Understanding Credit Scores

Scores range from 300 to 1000 (like traditional credit scores): Score factors (available with include_factors: true):

• Borrowing History — Loan repayment track record across DeFi protocols
• Wallet Composition — Asset diversity and stablecoin ratio
• Wallet Health — Collateralization ratios and liquidation distance
• Interactions — Protocol breadth and ecosystem participation
• Trust — Identity attestations (ENS, Gitcoin Passport, POAPs)
• New Credit — Recent changes in borrowing behavior

​

Understanding Sybil Scores

The get_sybil_score tool returns a score from 0-100 with a risk level: Key indicators to highlight:

• wallet_age_days — Older wallets are more trustworthy
• transaction_time_entropy — Higher entropy = more human-like timing
• identity_attestations — More attestations = harder to fake
• count_unique_counterparties — Diverse interactions suggest real usage

​

Reading Financial Summaries

Key fields in the financial summary report:

​

Identity Attestations

Attestations are verified on-chain identity credentials: More attestations generally indicate a more established, trustworthy identity.

​

Transaction Graphs

The get_transaction_graph tool returns a tripartite graph:

• Nodes with group: "wallet" are Ethereum addresses
• Nodes with group: "token" are ERC-20 tokens (USDC, WETH, etc.)
• Edges with label: "SENT" go from wallet to token
• Edges with label: "RECEIVED" go from token to wallet

This is useful for visualizing money flow, identifying major counterparties, and spotting wash trading patterns.

​

Agentic Reputation (ERC-8004)

The agent tools interact with the ERC-8004 Identity and Reputation Registries on Base (chain ID 8453). Identity Registry — where agents are registered as ERC-721 tokens:

• Each agent has an agent_id (token ID), owner address, and metadata (name, description, image)
• Use get_agent_count, list_agents, search_agents, get_agent to browse

Reputation Registry — where feedback about agents is stored on-chain:

• submit_agent_reputation computes credit score, sybil risk, and identity count for a given address, then writes the results on-chain as feedback for the specified agent
• get_agent_reputation reads the aggregated feedback summary
• Submissions are async — use get_reputation_status to track

You can combine agent tools with wallet tools: look up an agent’s owner via get_agent, then score the owner with get_credit_score to assess the human behind the agent.

​

Supported Chains

Data is aggregated across 10 EVM networks:

​

Input Format

All address-based tools accept either:

• Ethereum addresses: 0x742d35Cc6634C0532925a3b844Bc9e7595f32345 (42 characters, hex)
• ENS names: vitalik.eth, username.base.eth

Agent tools use integer agent_id values (starting at 1).

​

Best Practices