# Verify Agent Identity with AgentLink

AI agents need trusted identity before partner services can verify them. AgentLink guides setup, biomapping, registry checks, and signed request headers on Base.

## Install

```bash
npx skillstore add internet-court/humanode-agentlink
```

## Metadata

- Status: approved
- Slug: internet-court-humanode-agentlink
- Skillstore revision: r1
- Version status: missing
- Tree hash: b964578bad067a4d4a06ac89cd69e24ab8f9dc14e8b2e45d5a7a3e1baea29479
- Author: internet-court
- GitHub username: internet-court
- License: MIT
- Repository: https://github.com/internet-court/internet-court-skill/tree/main/vendored/humanode/humanode-agentlink
- Ref: 3f6e026a3363e0954ede7bef0cfe88d4475de137
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/internet-court-humanode-agentlink
- Manifest: https://skillstore.pages.dev/api/skills/internet-court-humanode-agentlink/manifest

## Capabilities

- Explains how to store or reference an agent private key for AgentLink signing.
- Guides generation of a Linker URL for a biomapped human owner.
- Shows how to confirm linked and active status on Base mainnet.
- Describes SDK and header-based request signing for AgentLink-enabled endpoints.
- Lists supported partner endpoints and their high-level request requirements.

## Use Cases

- Prepare a verified agent wallet: Set up the steps needed before an AI agent can appear as linked and active in the registry.
- Review identity and signing flow: Check how a human owner, agent wallet, registry status, and signed request header work together.
- Plan freemium endpoint access: Map which partner endpoints require AgentLink headers and what operational checks should happen first.

## Prompt Templates

### Check setup readiness

```
Help me prepare to use AgentLink. I have an agent wallet and need the steps to link it to a biomapped owner on Base.
```

### Create a linker checklist

```
Create a checklist for generating an AgentLink Linker URL for owner address {owner_address} and confirming active registry status.
```

### Choose a signing approach

```
Compare raw private key signing and external signer integration for my agent. Recommend the safer option for this deployment: {deployment_context}.
```

### Plan endpoint integration

```
Build an implementation plan for calling {partner_endpoint} with an AgentLink signed header. Include verification, secret handling, and failure handling.
```

## Limitations

- It does not perform biomapping or sign transactions for the human owner.
- It depends on external AgentLink CLI, SDK, registry, and partner services.
- It focuses on Base mainnet and documented AgentLink partner endpoints.
- It does not replace secure key storage or secret-management review.

## Best Practices

- Use an external signer or secret manager when production keys must stay outside the process.
- Verify linked and active registry status before sending signed requests to partner endpoints.
- Keep signed headers, private keys, and owner wallet details out of logs and shared prompts.

## Anti Patterns

- Committing an agent private key or signed header to source control.
- Assuming an agent stays active after the owner no longer meets biomapping requirements.
- Sending AgentLink signed headers to endpoints that do not need or trust AgentLink.

## Security Audit

- Audited at: 2026-07-19T10:11:00.998\+00:00
- Summary: The Markdown backtick and reconnaissance alerts are false positives. Genuine risks include raw wallet-key handling, unpinned npm execution, signed third-party requests, and an endpoint advertising coordinated X activity.

## Stats

- Views: 0
- Downloads: 4
- Favorites: 1
- Popularity score: 0