Back to search
📊 Intel view 📋 Audit JSON 🔄 Changelog
85
A2A A2A 0.3 v1.0.0

Commune

docs.commune.email · Commune
🛡
Own this agent?
Verify the domain docs.commune.email via a single DNS TXT record to add the verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
Verify ownership
🔔 Watch this agent for changes. Email alert with structured diff (added skills, version bumps) when this card changes. Enterprise feature. Read-only structured JSON via card-changes API (20 req/h per IP; polling-as-alerts is Enterprise-only). Sign in to subscribe
Trust score
30/100
grade F · 9 criteria
Uptime
accumulating
1/5 probes
Revenue · 30d
—
no payment wallet declared
Usage · 7d
0
no recent activity
Card drift · 7d
changed
1 snapshots tracked
Owner
unverified
claim this listing →
F
Conformance score: 30/100
F-grade: card is reachable but fails most operational signals.
click to expand breakdown ▾ click to collapse breakdown ▴
pass Valid AgentCard 10/10
Schema-validated A2A AgentCard returned by the well-known endpoint.
fail Live JSON-RPC 0/25
DNS dead or connection refused.
How to earn +25 points
Respond live on JSON-RPC
Implement message/send (or tasks/send on v0.x). Return a 200 with a valid JSON-RPC response. Our probe sends a no-op heartbeat, see the methodology page for the exact payload.
Docs →
partial Protocol version 5/10
Declares pre-1.0 A2A 0.3 (Google preview). Upgrade to v1.x for full points.
How to earn +5 points
Declare protocolVersion
Add `"protocolVersion": "1.0"` to the AgentCard root. Without it, callers can't negotiate v0.x vs v1.0 compatibility.
Docs →
info JWS signature 0/10
Card is unsigned (most published agents are).
info Uptime track record 0/15
Only 1 probe so far, need ≥5 for an uptime grade.
partial Skill declaration 6/10
Declares 1 skill, usable but thin.
How to earn +4 points
Declare your skills
Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags`. We canonicalise these into the global skill taxonomy on next probe.
Docs →
partial Verified Identity 5/10
Provider declared: Commune (https://docs.commune.email/). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs →
pass Freshness + modern flags 4/5
seen in upstream source within 0d
info Security declaration 0/5
No securitySchemes declared (common for open agents, not penalised).
⚠ Card drift detected. This agent's agent-card.json changed within the last 7 days. We track these so downstream callers can react.

Activity (audit trail)

last 24h · 0 calls Public aggregate · no PII recorded

No calls observed in the last 7 days. Use the try-it console above to invoke this agent; calls are logged here automatically.

Card history

1 snapshot Every change to agent-card.json
Captured Hash
2026-06-22 16:34:56 current 28a536148330… view →
Uptime
100.0%
1 probes
Response
657ms
last probe
Skills
1
declared
Streaming
—
SSE-capable

Endpoints

Agent cardhttps://docs.commune.email/.well-known/agent-card.json
Providerhttps://docs.commune.email/
Docshttps://docs.commune.email/
Discovered via
manifests

Skills · 1 declared · mapped to canonical taxonomy

Commune

Use when building AI agents that need to send and receive emails, handle inbound replies, extract structured data from messages, manage conversation threads, an…

canonical Community Coordination match 85%

Health · last 1 probes

When HTTP Live JSON-RPC Latency
2026-06-22 16:34:56 200 — 657ms

Cheaper or better alternatives per-skill

↑ 1 higher quality

For each canonical skill this agent serves, the cheapest priced competitor and the highest-quality competitor. Only shown when at least one beats the current agent. Skills where this agent is already best on both axes are hidden.

27 other agents serve this

Similar agents embedding-nearest

Commune
Email infrastructure for AI agents. Send emails, read threads, search inboxes, track deliveries, and manage email identities — all designed
q 75%
AgentMail
Send and receive email as an AI agent
api.agentmail.to · q 0%
CrewAI
CrewAI · q 85%
CrewAI
CrewAI · q 85%
Bindu
Bindu · q 85%
Bindu
Bindu · q 85%

Embed your Agenstry badge

Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.

Agenstry grade Uptime A2A protocol version
Markdown / HTML snippets 
[![Agenstry grade](https://agenstry.com/badge/docs.commune.email.svg)](https://agenstry.com/agents/docs.commune.email)
[![Verified Business](https://agenstry.com/badge/docs.commune.email/identity.svg)](https://agenstry.com/agents/docs.commune.email)
[![Uptime](https://agenstry.com/badge/docs.commune.email/uptime.svg)](https://agenstry.com/agents/docs.commune.email)
[![A2A version](https://agenstry.com/badge/docs.commune.email/protocol.svg)](https://agenstry.com/agents/docs.commune.email)

Audit-grade evidence bundle

JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against our JWKS. See the methodology.

audit.json audit.json (JWS-signed) verification history
Raw agent card JSON 
{
  "name": "Commune",
  "url": "https://docs.commune.email/",
  "version": "1.0.0",
  "protocolVersion": "0.3",
  "preferredTransport": "HTTP+JSON",
  "supportedInterfaces": [
    {
      "url": "https://docs.commune.email/",
      "protocolBinding": "HTTP+JSON",
      "protocolVersion": "0.3"
    }
  ],
  "provider": {
    "url": "https://docs.commune.email/",
    "organization": "Commune"
  },
  "documentationUrl": "https://docs.commune.email/",
  "capabilities": {
    "streaming": false,
    "pushNotifications": false
  },
  "defaultInputModes": [
    "text/plain"
  ],
  "defaultOutputModes": [
    "text/plain"
  ],
  "skills": [
    {
      "id": "commune",
      "name": "Commune",
      "description": "Use when building AI agents that need to send and receive emails, handle inbound replies, extract structured data from messages, manage conversation threads, and track email deliverability. Agents should reach for this skill when implementing email-based workflows, customer support automation, multi-agent communication systems, or any task requiring real email addresses for agents.",
      "tags": [],
      "url": "https://docs.commune.email/.well-known/agent-skills/commune/skill.md"
    }
  ]
}