slug: agentmail
provider: AgentMail
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Telecommunications
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 2
edges:
- tag: api-keys
  spec_file: agentmail-api-keys-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.75
  evidence: POST /v0/api-keys create Create API Key; type_api-keys_ApiKeyPermissions
  reason: Issuance, listing, revocation and permissioning of API keys for developers consuming the platform's
    public API maps to Developer Identity & Credential Management. Some risk this is better read as generic
    IAM plumbing, hence moderate confidence.
- tag: inboxes > api-keys
  spec_file: agentmail-inboxes-api-keys-api-openapi.yml
  capability_id: BC-4270.40
  capability_id_l1: BC-4270
  capability_name: Developer Identity & Credential Management
  confidence: 0.7
  evidence: POST /v0/inboxes/{inbox_id}/api-keys create Create API Key; type_api-keys_ApiKeyPermissions
  reason: Inbox-scoped API key issuance and revocation for developers integrating with the platform —
    credential stewardship for API consumers. Scoped-credential plumbing reading is possible, so confidence
    is held moderate.