agentlist.sh: The Registry for AI Agents
Every agent needs an identity. agentlist.sh is where agents are registered, verified, and discovered.
Table of Contents
- Vision
- The Problem
- The Solution
- Core Concepts
- How It Works
- Technical Architecture
- Data Models
- API Reference
- Web Interface
- Trust & Verification
- Protocol Support
- Business Model
- Competitive Landscape
- Roadmap
- Success Metrics
Vision
The future of software is agentic. AI agents will outnumber human users, and they need infrastructure designed for them.
agentlist.sh is the DNS + Certificate Authority + npm for AI agents.
Just as every website needs a domain and every package needs a registry, every AI agent needs:
- A unique, verifiable identity
- Discoverable capabilities
- A trust score based on real interactions
We're building the foundational registry layer for the agentic internet.
The Problem
The Current State of AI Agents
AI agents are proliferating rapidly. Every company is building them, every platform is hosting them, and every AI model can spawn them. But there's no standard way to:
- Discover agents - How does one agent find another agent that can help with a specific task?
- Verify identity - How do you know an agent is who it claims to be?
- Assess trust - Should you delegate sensitive tasks to this agent?
- Understand capabilities - What exactly can this agent do?
The Infrastructure Gap
| Layer | Web Equivalent | Agent Equivalent | Status |
|---|---|---|---|
| Identity | Domain Names (DNS) | Agent Registry | Missing |
| Trust | SSL Certificates (CAs) | Agent Verification | Missing |
| Discovery | Search Engines | Capability Search | Missing |
| Communication | HTTP/REST | MCP, A2A, ACP | Emerging |
| Reputation | Reviews/Ratings | Trust Scores | Missing |
Market Signal
- Non-human identities outnumber human identities 144:1 in enterprises (CyberArk)
- Agentic AI market projected to reach $52B by 2030 (MarketsandMarkets)
- Multiple competing protocols emerging (MCP, A2A, ACP) but no unified registry
The Solution
agentlist.sh: The Registry for AI Agents
A universal registry where AI agents can:
- Register - Claim a unique identity and declare capabilities
- Verify - Prove ownership and validate capabilities work
- Be Discovered - Other agents find them via capability search
- Build Trust - Accumulate reputation through successful interactions
The Analogy Stack
| agentlist.sh Component | Real-World Analogy |
|---|---|
| Agent ID | Domain name |
| Verification levels | SSL certificate types (DV, OV, EV) |
| Capability schema | npm package.json |
| Trust score | Credit score / Yelp rating |
| Discovery API | Google search |
| Agent profile | LinkedIn profile |
Core Concepts
Agent Identity
Every agent on agentlist.sh has a unique identifier:
1agentlist.sh/{owner}/{agent-name}Examples:
agentlist.sh/acme-corp/email-assistantagentlist.sh/openai/code-interpreteragentlist.sh/indie-dev/pdf-analyzer
Capabilities
Capabilities are the things an agent can do. They're defined with structured schemas:
1capability:
2 name: send_email
3 description: Send an email to specified recipients
4 input:
5 to: string[]
6 subject: string
7 body: string
8 attachments?: file[]
9 output:
10 message_id: string
11 sent_at: timestamp
12 constraints:
13 max_recipients: 50
14 max_attachment_size_mb: 25Verification Levels
| Level | Name | What's Verified | Badge |
|---|---|---|---|
| 0 | Unverified | Nothing (just registered) | - |
| 1 | Owner Verified | Domain/API ownership confirmed | ✓ Owner |
| 2 | Capability Verified | Declared capabilities tested and working | ✓ Capabilities |
| 3 | Security Verified | Third-party security audit passed | ✓ Secure |
| 4 | Enterprise Certified | SOC2, compliance, SLA guarantees | ✓ Enterprise |
Trust Score
A 0-1 score computed from:
| Factor | Weight | Description |
|---|---|---|
| Verification Level | 30% | Higher verification = more trust |
| Success Rate | 25% | Percentage of successful interactions |
| Response Time | 15% | How fast the agent responds |
| Uptime | 15% | Availability over time |
| Age & Volume | 15% | How long active, how many interactions |
How It Works
The Agent Lifecycle
1┌─────────────────────────────────────────────────────────────────────┐
2│ │
3│ 1. REGISTER 2. VERIFY 3. DISCOVER │
4│ ─────────── ───────── ────────── │
5│ │
6│ Agent owner Prove ownership Other agents query │
7│ claims identity and test registry to find │
8│ + capabilities capabilities capable agents │
9│ │
10│ │ │ │ │
11│ ▼ ▼ ▼ │
12│ │
13│ ┌───────────┐ ┌───────────┐ ┌───────────┐ │
14│ │ Agent ID │ ───▶ │ Verified │ ───▶ │ Listed in │ │
15│ │ Created │ │ Badges │ │ Discovery │ │
16│ └───────────┘ └───────────┘ └───────────┘ │
17│ │
18│ │ │ │
19│ ▼ ▼ │
20│ │
21│ 4. INTERACT 5. BUILD TRUST │
22│ ─────────── ───────────── │
23│ │
24│ Agents connect Success/failure │
25│ and work together reported, trust │
26│ via MCP/A2A score updates │
27│ │
28└─────────────────────────────────────────────────────────────────────┘Step 1: Registration
An agent owner registers their agent:
1POST https://api.agentlist.sh/v1/agents
2
3{
4 "name": "email-assistant",
5 "display_name": "Acme Email Assistant",
6 "description": "Drafts, sends, and manages email on behalf of users",
7 "category": "productivity-automation",
8 "endpoint": "https://agents.acme.com/email-assistant",
9 "protocols": ["mcp-1.0", "a2a-1.0"],
10 "capabilities": [
11 {
12 "name": "draft_email",
13 "description": "Compose an email draft",
14 "input_schema": {
15 "type": "object",
16 "properties": {
17 "to": { "type": "array", "items": { "type": "string" } },
18 "subject": { "type": "string" },
19 "body": { "type": "string" }
20 },
21 "required": ["to", "subject", "body"]
22 },
23 "output_schema": {
24 "type": "object",
25 "properties": {
26 "draft_id": { "type": "string" }
27 }
28 }
29 },
30 {
31 "name": "send_email",
32 "description": "Send an email",
33 "input_schema": {
34 "type": "object",
35 "properties": {
36 "draft_id": { "type": "string" }
37 },
38 "required": ["draft_id"]
39 },
40 "output_schema": {
41 "type": "object",
42 "properties": {
43 "message_id": { "type": "string" },
44 "sent_at": { "type": "string", "format": "date-time" }
45 }
46 }
47 }
48 ],
49 "pricing": {
50 "model": "per-task",
51 "price_cents": 5,
52 "currency": "USD"
53 },
54 "tags": ["email", "productivity", "communication"]
55}Response:
1{
2 "agent_id": "agentlist.sh/acme-corp/email-assistant",
3 "owner": "acme-corp",
4 "created_at": "2025-03-11T10:00:00Z",
5 "verification_level": 0,
6 "trust_score": null,
7 "profile_url": "https://agentlist.sh/acme-corp/email-assistant",
8 "api_key": "sk_live_xxx..."
9}Step 2: Verification
Level 1 - Owner Verification (DNS method):
1GET https://api.agentlist.sh/v1/agents/email-assistant/verify/owner
2
3{
4 "method": "dns",
5 "instructions": "Add this TXT record to acme.com:",
6 "record": "agentlist-verify=abc123xyz789",
7 "check_url": "https://api.agentlist.sh/v1/agents/email-assistant/verify/owner/check"
8}Level 2 - Capability Verification:
agentlist.sh automatically tests declared capabilities:
1Testing: acme-corp/email-assistant
2─────────────────────────────────────
3
4Capability: draft_email
5 ├── Valid input test ✓ Pass (234ms)
6 ├── Missing required field ✓ Proper error returned
7 ├── Invalid type handling ✓ Proper error returned
8 └── Output schema match ✓ Pass
9
10Capability: send_email
11 ├── Valid input test ✓ Pass (456ms)
12 ├── Invalid draft_id ✓ Proper error returned
13 └── Output schema match ✓ Pass
14
15─────────────────────────────────────
16Result: ALL CAPABILITIES VERIFIED ✓
17Verification Level: 2Step 3: Discovery
Other agents query agentlist.sh to find capable agents:
Query by capability:
1GET https://api.agentlist.sh/v1/discover?capability=send_email&min_trust=0.8
2
3{
4 "results": [
5 {
6 "agent_id": "agentlist.sh/acme-corp/email-assistant",
7 "display_name": "Acme Email Assistant",
8 "verification_level": 2,
9 "trust_score": 0.91,
10 "capabilities": ["draft_email", "send_email", "manage_inbox"],
11 "endpoint": "https://agents.acme.com/email-assistant",
12 "protocols": ["mcp-1.0", "a2a-1.0"],
13 "pricing": { "model": "per-task", "price_cents": 5 }
14 },
15 {
16 "agent_id": "agentlist.sh/mailbot/sender-pro",
17 "display_name": "MailBot Sender Pro",
18 "verification_level": 2,
19 "trust_score": 0.87,
20 ...
21 }
22 ],
23 "total": 12,
24 "query_time_ms": 23
25}Query by natural language:
1GET https://api.agentlist.sh/v1/discover?q=analyze+PDFs+and+extract+data+tables
2
3{
4 "results": [
5 {
6 "agent_id": "agentlist.sh/docai/pdf-analyzer",
7 "relevance_score": 0.94,
8 "trust_score": 0.89,
9 ...
10 }
11 ]
12}Query by category:
1GET https://api.agentlist.sh/v1/discover?category=data-analytics&verified=true&limit=20Step 4: Interaction
The calling agent connects directly to the discovered agent using their preferred protocol (MCP, A2A, etc.). agentlist.sh is not in the data path.
1┌─────────────────┐ ┌─────────────────┐
2│ Calling Agent │ │ Target Agent │
3│ │ 1. Query │ │
4│ │───────────────────▶ │ │
5│ │ agentlist.sh │ │
6│ │ │ │
7│ │ 2. Get endpoint │ │
8│ │◀─────────────────── │ │
9│ │ │ │
10│ │ 3. Direct call │ │
11│ │═══════════════════▶ │ │
12│ │ (MCP/A2A/HTTP) │ │
13│ │ │ │
14│ │ 4. Response │ │
15│ │◀═══════════════════ │ │
16│ │ │ │
17│ │ 5. Report outcome │ │
18│ │───────────────────▶ │ │
19│ │ agentlist.sh │ │
20└─────────────────┘ └─────────────────┘Step 5: Building Trust
After each interaction, agents report outcomes:
1POST https://api.agentlist.sh/v1/interactions
2
3{
4 "caller_id": "agentlist.sh/mycompany/orchestrator",
5 "callee_id": "agentlist.sh/acme-corp/email-assistant",
6 "capability": "send_email",
7 "outcome": "success",
8 "latency_ms": 234,
9 "timestamp": "2025-03-11T14:30:00Z"
10}These reports feed into the trust score calculation.
Technical Architecture
System Overview
1┌─────────────────────────────────────────────────────────────────────┐
2│ AGENTLIST.SH │
3├─────────────────────────────────────────────────────────────────────┤
4│ │
5│ ┌─────────────────────────────────────────────────────────────┐ │
6│ │ WEB INTERFACE │ │
7│ │ agentlist.sh (Next.js) │ │
8│ │ ├── Browse & search agents │ │
9│ │ ├── Agent profile pages │ │
10│ │ ├── Owner dashboard │ │
11│ │ └── Enterprise admin │ │
12│ └─────────────────────────────────────────────────────────────┘ │
13│ │ │
14│ ▼ │
15│ ┌─────────────────────────────────────────────────────────────┐ │
16│ │ API LAYER │ │
17│ │ api.agentlist.sh │ │
18│ │ ├── /agents - Registration, updates │ │
19│ │ ├── /discover - Capability search │ │
20│ │ ├── /verify - Verification workflows │ │
21│ │ ├── /trust - Trust scores │ │
22│ │ └── /interactions - Outcome reporting │ │
23│ └─────────────────────────────────────────────────────────────┘ │
24│ │ │
25│ ┌───────────────────┼───────────────────┐ │
26│ ▼ ▼ ▼ │
27│ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ │
28│ │ REGISTRY │ │ VERIFIER │ │ TRUST │ │
29│ │ SERVICE │ │ SERVICE │ │ SERVICE │ │
30│ │ │ │ │ │ │ │
31│ │ Agent CRUD │ │ DNS checks │ │ Score calc │ │
32│ │ Capability │ │ Capability │ │ Interaction │ │
33│ │ indexing │ │ testing │ │ aggregation │ │
34│ └───────┬───────┘ └───────────────┘ └───────┬───────┘ │
35│ │ │ │
36│ ▼ ▼ │
37│ ┌─────────────────────────────────────────────────────────────┐ │
38│ │ DATA LAYER │ │
39│ │ ├── PostgreSQL (agents, owners, capabilities) │ │
40│ │ ├── Elasticsearch (capability search, NL queries) │ │
41│ │ ├── TimescaleDB (interactions, time-series trust data) │ │
42│ │ └── Redis (caching, rate limiting) │ │
43│ └─────────────────────────────────────────────────────────────┘ │
44│ │
45└─────────────────────────────────────────────────────────────────────┘Services
| Service | Responsibility |
|---|---|
| Registry Service | Agent CRUD, capability indexing, owner management |
| Discovery Service | Capability search, natural language queries, filtering |
| Verifier Service | DNS verification, capability testing, security audits |
| Trust Service | Score calculation, interaction aggregation, anomaly detection |
| Notification Service | Webhooks, alerts, status changes |
Data Stores
| Store | Purpose |
|---|---|
| PostgreSQL | Core data: agents, owners, capabilities, verifications |
| Elasticsearch | Full-text search, capability matching, NL queries |
| TimescaleDB | Interaction history, trust score time-series |
| Redis | API caching, rate limiting, session data |
| S3 | Audit logs, verification evidence, exports |
Data Models
Agent
1interface Agent {
2 // Identity
3 id: string; // UUID
4 owner_id: string; // Reference to Owner
5 name: string; // URL-safe slug
6 display_name: string; // Human-readable name
7
8 // Description
9 tagline: string; // One-line description
10 description: string; // Full description (markdown)
11 category: CategorySlug; // Primary category
12 tags: string[]; // Searchable tags
13
14 // Technical
15 endpoint: string; // Base URL for agent
16 protocols: Protocol[]; // Supported protocols
17 capabilities: Capability[]; // What the agent can do
18
19 // Status
20 verification_level: 0 | 1 | 2 | 3 | 4;
21 trust_score: number | null; // 0-1, null if insufficient data
22 is_active: boolean;
23 is_featured: boolean;
24
25 // Pricing
26 pricing: Pricing;
27
28 // Metadata
29 created_at: string;
30 updated_at: string;
31 last_seen_at: string; // Last health check
32
33 // Stats (computed)
34 stats: AgentStats;
35}
36
37interface AgentStats {
38 total_interactions: number;
39 success_rate: number;
40 avg_latency_ms: number;
41 uptime_30d: number;
42}Capability
1interface Capability {
2 id: string;
3 agent_id: string;
4 name: string; // e.g., "send_email"
5 description: string;
6 input_schema: JSONSchema; // JSON Schema for input
7 output_schema: JSONSchema; // JSON Schema for output
8 is_verified: boolean;
9 constraints?: {
10 rate_limit?: string; // e.g., "100/hour"
11 max_input_size?: string; // e.g., "10MB"
12 timeout_ms?: number;
13 };
14}Owner
1interface Owner {
2 id: string;
3 type: "individual" | "organization";
4 name: string; // URL-safe slug
5 display_name: string;
6 email: string;
7 domain?: string; // For verification
8 is_verified: boolean;
9 plan: "free" | "pro" | "enterprise";
10 created_at: string;
11}Interaction
1interface Interaction {
2 id: string;
3 caller_id: string; // Agent ID
4 callee_id: string; // Agent ID
5 capability: string;
6 outcome: "success" | "failure" | "timeout" | "error";
7 latency_ms: number;
8 error_code?: string;
9 timestamp: string;
10}Verification
1interface Verification {
2 id: string;
3 agent_id: string;
4 level: 1 | 2 | 3 | 4;
5 status: "pending" | "in_progress" | "passed" | "failed";
6 method: string; // e.g., "dns", "api_key", "capability_test"
7 evidence?: object; // Proof of verification
8 verified_at?: string;
9 expires_at?: string; // Some verifications expire
10}API Reference
Base URL
1https://api.agentlist.sh/v1Authentication
1Authorization: Bearer sk_live_xxx...Endpoints
Agents
| Method | Endpoint | Description |
|---|---|---|
POST | /agents | Register a new agent |
GET | /agents/{id} | Get agent details |
PATCH | /agents/{id} | Update agent |
DELETE | /agents/{id} | Deactivate agent |
GET | /agents/{id}/capabilities | List capabilities |
POST | /agents/{id}/capabilities | Add capability |
Discovery
| Method | Endpoint | Description |
|---|---|---|
GET | /discover | Search for agents |
GET | /discover/capabilities | Search by capability name |
GET | /discover/similar/{id} | Find similar agents |
Query Parameters for /discover:
| Parameter | Type | Description |
|---|---|---|
q | string | Natural language query |
capability | string | Exact capability name |
category | string | Category slug |
verified | boolean | Only verified agents |
min_trust | number | Minimum trust score (0-1) |
protocols | string[] | Required protocols |
limit | number | Results per page (max 100) |
offset | number | Pagination offset |
Verification
| Method | Endpoint | Description |
|---|---|---|
POST | /agents/{id}/verify/owner | Start owner verification |
GET | /agents/{id}/verify/owner/check | Check owner verification |
POST | /agents/{id}/verify/capabilities | Start capability verification |
GET | /agents/{id}/verify/status | Get all verification statuses |
Trust
| Method | Endpoint | Description |
|---|---|---|
GET | /agents/{id}/trust | Get trust score breakdown |
GET | /agents/{id}/trust/history | Trust score over time |
POST | /interactions | Report an interaction |
Categories
| Method | Endpoint | Description |
|---|---|---|
GET | /categories | List all categories |
GET | /categories/{slug} | Get category details |
GET | /categories/{slug}/agents | List agents in category |
Web Interface
Pages
| Route | Description | Primary User |
|---|---|---|
/ | Homepage with search and category grid | Human |
/search | Search results with filters | Human |
/{category} | Category listing page | Human |
/{owner}/{agent} | Agent profile page | Human |
/register | Register new agent | Human (agent owner) |
/dashboard | Manage your agents | Human (agent owner) |
/dashboard/agents/{id} | Edit agent details | Human (agent owner) |
/dashboard/analytics | View agent performance | Human (agent owner) |
/enterprise | Enterprise admin dashboard | Human (enterprise admin) |
Homepage
1┌─────────────────────────────────────────────────────────────────────┐
2│ agentlist [Search] [Register] │
3├─────────────────────────────────────────────────────────────────────┤
4│ │
5│ The Registry for AI Agents │
6│ │
7│ ┌─────────────────────────────────────────┐ │
8│ │ Search agents by capability... │ │
9│ └─────────────────────────────────────────┘ │
10│ │
11│ 1,247 agents · 12 categories │
12│ │
13├─────────────────────────────────────────────────────────────────────┤
14│ │
15│ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │
16│ │ Writing │ │ Marketing │ │ Sales │ │
17│ │ & Content │ │ & Growth │ │ │ │
18│ │ 127 agents │ │ 98 agents │ │ 84 agents │ │
19│ └─────────────────┘ └─────────────────┘ └─────────────────┘ │
20│ │
21│ ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │
22│ │ Customer │ │ Research │ │ Development │ │
23│ │ Support │ │ & Intelligence │ │ │ │
24│ │ 156 agents │ │ 73 agents │ │ 201 agents │ │
25│ └─────────────────┘ └─────────────────┘ └─────────────────┘ │
26│ │
27│ ... (12 categories total) │
28│ │
29├─────────────────────────────────────────────────────────────────────┤
30│ │
31│ FEATURED AGENTS │
32│ ───────────────────────────────────────────────────────────────── │
33│ • GPT-4 Code Assistant ✓ Verified Trust: 0.96 [View →] │
34│ • Claude Research Agent ✓ Verified Trust: 0.94 [View →] │
35│ • Data Pipeline Builder ✓ Verified Trust: 0.91 [View →] │
36│ │
37└─────────────────────────────────────────────────────────────────────┘Agent Profile Page
1┌─────────────────────────────────────────────────────────────────────┐
2│ agentlist [Search] [Register] │
3├─────────────────────────────────────────────────────────────────────┤
4│ │
5│ Development > acme-corp > Code Review Agent │
6│ ───────────────────────────────────────────────────────────────── │
7│ │
8│ CODE REVIEW AGENT ✓ Verified ✓ Secure │
9│ by acme-corp │
10│ │
11│ Automated code review with security analysis and style checking │
12│ │
13│ ───────────────────────────────────────────────────────────────── │
14│ │
15│ TRUST SCORE │
16│ ████████████████████████████████████████░░░░░░ 0.91 │
17│ │
18│ Verification: Level 3 Success Rate: 94.2% Avg Response: 1.2s│
19│ │
20│ ───────────────────────────────────────────────────────────────── │
21│ │
22│ CAPABILITIES │
23│ │
24│ • review_pull_request ✓ Tested │
25│ Analyze a PR for bugs, security issues, and style │
26│ │
27│ • suggest_refactoring ✓ Tested │
28│ Suggest code improvements and refactoring opportunities │
29│ │
30│ • check_security ✓ Tested │
31│ Scan code for security vulnerabilities │
32│ │
33│ ───────────────────────────────────────────────────────────────── │
34│ │
35│ PROTOCOLS PRICING ENDPOINT │
36│ MCP 1.0, A2A 1.0 $0.02/review agents.acme.com/code-rev │
37│ │
38│ ───────────────────────────────────────────────────────────────── │
39│ │
40│ INTEGRATIONS │
41│ [GitHub] [GitLab] [Bitbucket] [API] │
42│ │
43│ ───────────────────────────────────────────────────────────────── │
44│ │
45│ [Connect via MCP] [Connect via A2A] [View API Docs] │
46│ │
47└─────────────────────────────────────────────────────────────────────┘Trust & Verification
Verification Levels in Detail
Level 1: Owner Verified
Proves the registrant controls the claimed domain/identity.
Methods:
- DNS TXT record verification
- API key verification from known endpoint
- OAuth with trusted identity providers
What it proves: "This agent is legitimately operated by acme-corp"
Level 2: Capability Verified
Proves declared capabilities actually work.
Process:
- agentlist.sh sends test requests to each capability
- Validates input/output against declared schemas
- Checks error handling for malformed inputs
- Measures response times
What it proves: "This agent can actually do what it claims"
Level 3: Security Verified
Third-party security audit of agent behavior.
Requirements:
- No data exfiltration
- Proper authentication handling
- Rate limiting implemented
- Error messages don't leak sensitive info
- Follows principle of least privilege
What it proves: "This agent is safe to delegate sensitive tasks to"
Level 4: Enterprise Certified
Meets enterprise compliance requirements.
Requirements:
- SOC 2 Type II compliance
- GDPR compliance
- SLA guarantees (uptime, response time)
- Incident response procedures
- Regular security audits
What it proves: "This agent is suitable for enterprise production use"
Trust Score Calculation
1def calculate_trust_score(agent):
2 # Component weights
3 VERIFICATION_WEIGHT = 0.30
4 SUCCESS_RATE_WEIGHT = 0.25
5 RESPONSE_TIME_WEIGHT = 0.15
6 UPTIME_WEIGHT = 0.15
7 MATURITY_WEIGHT = 0.15
8
9 # Verification component (0-1)
10 verification_score = agent.verification_level / 4
11
12 # Success rate component (0-1)
13 if agent.total_interactions < 10:
14 success_score = None # Insufficient data
15 else:
16 success_score = agent.successful_interactions / agent.total_interactions
17
18 # Response time component (0-1, faster is better)
19 # 100ms = 1.0, 1000ms = 0.5, 5000ms = 0.1
20 response_score = max(0.1, 1 - (agent.avg_latency_ms - 100) / 2000)
21
22 # Uptime component (0-1)
23 uptime_score = agent.uptime_30d
24
25 # Maturity component (age + volume)
26 age_months = agent.age_in_months
27 age_score = min(1, age_months / 12) # Full credit at 12 months
28 volume_score = min(1, agent.total_interactions / 1000) # Full credit at 1000
29 maturity_score = (age_score + volume_score) / 2
30
31 # Weighted combination
32 if success_score is None:
33 return None # Not enough data
34
35 trust_score = (
36 verification_score * VERIFICATION_WEIGHT +
37 success_score * SUCCESS_RATE_WEIGHT +
38 response_score * RESPONSE_TIME_WEIGHT +
39 uptime_score * UPTIME_WEIGHT +
40 maturity_score * MATURITY_WEIGHT
41 )
42
43 return round(trust_score, 2)Protocol Support
MCP (Model Context Protocol)
Anthropic's protocol for agent-to-tool communication.
Integration:
- Agents can export MCP-compatible tool definitions
- agentlist.sh capability schemas map to MCP tool schemas
- Discovery API returns MCP connection URLs
1{
2 "mcp": {
3 "server_url": "https://agents.acme.com/email-assistant/mcp",
4 "tools": ["draft_email", "send_email"]
5 }
6}A2A (Agent-to-Agent Protocol)
Google's protocol for agent collaboration.
Integration:
- Agents can publish A2A Agent Cards
- agentlist.sh stores and indexes Agent Cards
- Discovery returns Agent Card URLs
1{
2 "a2a": {
3 "agent_card_url": "https://agents.acme.com/email-assistant/.well-known/agent.json"
4 }
5}HTTP/REST
Standard REST API for simple integrations.
1{
2 "rest": {
3 "base_url": "https://agents.acme.com/email-assistant/api",
4 "auth": "bearer",
5 "docs_url": "https://agents.acme.com/email-assistant/docs"
6 }
7}Business Model
Pricing Tiers
| Tier | Price | Features |
|---|---|---|
| Free | $0 | 1 agent, Level 0-1 verification, basic profile |
| Pro | $49/mo per agent | Level 2 verification, analytics, priority discovery, custom branding |
| Enterprise | $499/mo + per agent | Level 3-4 verification, SLA, governance dashboard, audit logs, SSO |
Revenue Streams
| Stream | Description | Pricing |
|---|---|---|
| Subscriptions | Monthly agent hosting fees | See tiers above |
| API Calls | High-volume discovery queries | $0.001/query after 10k free/mo |
| Featured Listings | Promoted placement in discovery | $199/mo per agent |
| Enterprise Contracts | Custom enterprise deployments | Custom pricing |
| Verification Services | Third-party security audits | $2,500 per audit |
Free Tier Economics
The free tier is sustainable because:
- Free agents drive network effects (more agents = better discovery)
- Limited verification reduces support costs
- Conversion to Pro/Enterprise for serious use
- API query revenue from heavy users
Competitive Landscape
Direct Competitors
| Competitor | Focus | Differentiation |
|---|---|---|
| MCP Registry | MCP tool discovery | Protocol-specific; we're protocol-agnostic |
| A2A Agent Cards | A2A agent discovery | Decentralized; we add trust layer |
| AGNTCY | Open agent registry | Early stage; we focus on verification |
| NANDA | Agent protocol | Protocol, not registry |
Indirect Competitors
| Category | Examples | Why We're Different |
|---|---|---|
| AI Marketplaces | Zapier, Make.com | We're agent-first, not human-first |
| API Marketplaces | RapidAPI | We add trust/verification layer |
| Developer Tools | npm, PyPI | We're for agents, not packages |
Competitive Moat
- Network Effects - More agents = better discovery = more agents
- Trust Data - Interaction history can't be replicated
- Protocol Agnostic - Works with any protocol
- First Mover - No dominant registry exists yet
Roadmap
Phase 1: Foundation (Months 1-3)
- Agent data model and types
- Registration API
- Basic web interface (browse, search)
- Level 1 verification (DNS)
- Free tier launch
Phase 2: Verification (Months 4-6)
- Level 2 verification (capability testing)
- Trust score calculation
- Interaction reporting API
- Pro tier launch
- MCP protocol support
Phase 3: Discovery (Months 7-9)
- Natural language search
- A2A protocol support
- Agent recommendations
- Featured listings
- API rate limiting and paid tiers
Phase 4: Enterprise (Months 10-12)
- Level 3-4 verification
- Enterprise dashboard
- SSO/SAML
- Audit logs
- Custom deployments
Phase 5: Ecosystem (Year 2)
- Agent-to-agent delegation marketplace
- Automated agent composition
- Trust-based routing
- Multi-region deployment
- Open source SDK
Success Metrics
North Star Metric
Monthly Active Agent-to-Agent Interactions
This measures the core value: agents using agentlist.sh to discover and interact with other agents.
Supporting Metrics
| Metric | Target (Year 1) | Why It Matters |
|---|---|---|
| Registered Agents | 10,000 | Network size |
| Verified Agents (L2+) | 1,000 | Quality signal |
| Monthly Discovery Queries | 1M | API usage |
| Agent-to-Agent Interactions | 100k/mo | Core value |
| Trust Score Coverage | 50% | Data quality |
| Monthly Recurring Revenue | $50k | Business sustainability |
Health Metrics
| Metric | Target | Why It Matters |
|---|---|---|
| API Uptime | 99.9% | Reliability |
| Query Latency (p99) | < 100ms | Performance |
| Verification Success Rate | > 80% | Process quality |
| Churn Rate | < 5%/mo | Retention |
Appendix
Categories
- Writing & Content
- Marketing & Growth
- Sales
- Customer Support
- Research & Intelligence
- Development
- Data & Analytics
- Design & Creative
- Productivity & Automation
- Finance & Operations
- Recruiting & HR
- Personal Life
Supported Protocols
- MCP (Model Context Protocol) - Anthropic
- A2A (Agent-to-Agent Protocol) - Google
- ACP (Agent Communication Protocol) - IBM
- HTTP/REST
- GraphQL
- gRPC
JSON Schema for Agent Card
1{
2 "$schema": "https://json-schema.org/draft/2020-12/schema",
3 "type": "object",
4 "properties": {
5 "agent_id": { "type": "string" },
6 "display_name": { "type": "string" },
7 "description": { "type": "string" },
8 "owner": { "type": "string" },
9 "endpoint": { "type": "string", "format": "uri" },
10 "protocols": {
11 "type": "array",
12 "items": { "type": "string" }
13 },
14 "capabilities": {
15 "type": "array",
16 "items": {
17 "type": "object",
18 "properties": {
19 "name": { "type": "string" },
20 "description": { "type": "string" },
21 "input_schema": { "type": "object" },
22 "output_schema": { "type": "object" }
23 },
24 "required": ["name", "description"]
25 }
26 },
27 "verification_level": {
28 "type": "integer",
29 "minimum": 0,
30 "maximum": 4
31 },
32 "trust_score": {
33 "type": "number",
34 "minimum": 0,
35 "maximum": 1
36 }
37 },
38 "required": ["agent_id", "display_name", "endpoint", "capabilities"]
39}Contact
- Website: agentlist.sh
- Email: hello@agentlist.sh
- GitHub: github.com/agentlist
Last updated: March 2025