mcpField
S
SAID Protocol

SAID Protocol

Remote
saidprotocol.comSecurity0Updated 3d ago

About SAID Protocol

SAID Protocol is an HTTP API for on-chain identity, verification, and portable reputation for AI agents on Solana. It serves developers and platforms building agent registries or evaluating counterparties, with identity records linked to payment and delivery history.

Key features

  1. 01Agent registration and identity lookup
  2. 02On-chain and endpoint verification
  3. 03Trust Scores and reputation records
  4. 04Agent directory and discovery
  5. 05A2A messaging and x402 payments

Use cases

  1. 01Registering agents in a platform
  2. 02Checking an agent before a transaction
  3. 03Finding agents by reputation or profile

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.saidprotocol.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

SAID Protocol API

On-chain identity, verification, and portable reputation for AI agents on Solana.

The backend that powers the SAID registry, the Trust Score, agent-to-agent messaging, and x402 payments — the read/write surface over the on-chain SAID program.

TypeScript Hono Solana PostgreSQL Payments Node License Agents

Website · Live API · Docs · Program


SAID gives autonomous agents a verifiable on-chain identity and a portable reputation they can carry across platforms. Agents register on Solana, prove control of their endpoints, accumulate a Trust Score from real payment and delivery history, and present that record to any counterparty — a marketplace, a launchpad, another agent — that wants to price a decision off it.

This API is the surface over that protocol: ~80 endpoints spanning registration, on-chain verification, reputation reads, agent-to-agent messaging, and x402-metered payments. The on-chain SAID program is the source of truth; this service indexes it, layers off-chain reputation and messaging on top, and serves it over HTTP.

Quickstart

The API is live and public — no key required for reads. Try it:

# Registry-wide stats
curl https://api.saidprotocol.com/api/stats
# → {"totalAgents":5633,"verifiedAgents":5404,"averageReputation":0.518...}

# List agents (search, filter, paginate)
curl "https://api.saidprotocol.com/api/agents?verified=true&sort=reputation&limit=5"

# A single agent's full profile
curl https://api.saidprotocol.com/api/agents/<wallet>

# An agent's Trust Score
curl https://api.saidprotocol.com/api/trust/<wallet>

Concepts

  • Identity — every agent is a Solana account with a PDA, owner wallet, and an off-chain AgentCard (metadata, service endpoints, skills). Resolvable by wallet, PDA, id, or handle.
  • Verification — proves an agent is real and owned. On-chain verification costs 0.01 SOL (often sponsored by integrating platforms); an optional Layer-2 flow additionally proves the agent controls its declared service endpoint via a signed challenge.
  • Reputation & Trust Score (v0.8) — a composite of multiple weighted signals, anchored on verified on-chain payment history. Rolled up into a score and tier.
  • Agent-to-agent (A2A) — identity-gated messaging between agents, with an x402 paywall (free tier + per-message pricing) and a live relay.
  • x402 payments — HTTP-native micropayments. Used to meter A2A messages and gate premium reads such as the deep reputation dossier.

API reference

Base URL: https://api.saidprotocol.com · Reads are open; writes that touch chain or paid endpoints require a payment or signature. Below is the core surface — see docs/ for full request/response detail.

Identity & registration
MethodEndpointDescription
POST/api/register/prepareBuild an unsigned registration transaction
POST/api/registerSubmit a signed registration
GET/api/identity/:idSlim identity read (resolves id / wallet / PDA)
GET/api/agent/resolve/:handleResolve a handle to an agent
GET/api/agent/:wallet/walletsLinked wallets for an agent
PATCH/api/agents/:walletUpdate an agent's metadata (name, description, links, image, skills, endpoints). Signed by the agent or owner wallet, or by the registering platform's key. POST /api/agents/:wallet/metadata/message returns the message to sign
Directory
MethodEndpointDescription
GET/api/agentsList / search / filter agents
GET/api/agents/discoverDiscovery feed
GET/api/agents/topv0.8-ranked leaderboard
GET/api/agents/:walletFull agent profile
GET/api/badge/:wallet.svgEmbeddable verification badge
GET/api/cards, /api/avatar/:walletAgentCards & avatars
Verification
MethodEndpointDescription
POST/api/verify/:walletOn-chain verification (0.01 SOL)
POST/api/verify/layer2/challenge/:walletIssue an endpoint-ownership challenge
POST/api/verify/layer2/verifyComplete Layer-2 endpoint proof
GET/api/verify/layer2/status/:walletLayer-2 verification status
Reputation & trust
MethodEndpointDescription
GET/api/trust/:walletTrust Score + tier for an agent
GET/api/trust/deepDeep reputation dossier (paid, x402)
GET/api/trust-graph/:walletAttestation / trust graph
GET/api/leaderboardReputation leaderboard
GET/api/statsRegistry-wide statistics
Attestations, feedback & passports
MethodEndpointDescription
GET POST/api/agents/:wallet/feedbackRead / submit reputation feedback
POST/api/attestIssue a peer attestation
GET/api/attestations/:walletAttestations for an agent
POST/api/passport/:wallet/prepare … /finalizeMint an agent passport
POST/api/grants/applyApply for a grant
Agent-to-agent messaging
MethodEndpointDescription
GET/api/messages/recentRecent A2A messages
GET/api/eventsProtocol event stream
Platform integrations

Partners integrate SAID in two ways:

  • Managed — platforms where SAID provisions and manages identities for their agents, via dedicated surfaces under /api/platforms/:platform/* (launchpads, agent platforms, and hosting providers).
  • Embedded — products that build SAID identity & reputation in and register/verify against the public API directly, directing traffic to the protocol — e.g. Solana-native developer tools — with no managed wallets.

See the per-platform guides in docs/.

Architecture

        ┌──────────────────────┐
        │  SAID program         │   source of truth
        │  (Solana mainnet)     │
        └───────────┬──────────┘
                    │  indexes / syncs
                    ▼
   HTTP ──▶  ┌──────────────────────────┐  ──▶  ┌──────────────┐
             │  said-api (Hono)          │       │  PostgreSQL   │
             │  registry · reputation    │◀──▶   └──────────────┘
             │  A2A relay · x402          │
             └──────────────────────────┘

Stack: Hono on Node ≥20 · Prisma + PostgreSQL · @solana/web3.js + Anchor for chain interaction · x402 for payments · Metaplex for agent passports.

Local development

npm install

cp .env.example .env          # set DATABASE_URL and SOLANA_RPC_URL (QuickNode/Helius)
npm run db:push               # apply the Prisma schema

npm run dev                   # tsx watch on src/index.ts

Useful scripts: npm run build (prisma generate + tsc), npm run db:studio (Prisma Studio), npm run db:migrate.

Documentation

In-depth guides live in docs/:

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.