slug: mastra
provider: Mastra
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
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: Agents
  spec_file: mastra-agents-api-openapi.yml
  capability_id: BC-610.60
  capability_id_l1: BC-610
  capability_name: Artificial Intelligence Management
  confidence: 0.75
  evidence: '"POST /api/agents/{agentId}/generate  generateAgent  Generate a response from an agent"'
  reason: Operations define, list and run LLM agents and execute tools on their behalf — the runtime surface
    of an AI agent framework, which falls under Artificial Intelligence Management (AI/ML lifecycle and
    operations). Some ambiguity because this is framework infrastructure rather than model governance.
- tag: Telemetry
  spec_file: mastra-telemetry-api-openapi.yml
  capability_id: BC-4220.20
  capability_id_l1: BC-4220
  capability_name: Observability Management
  confidence: 0.7
  evidence: '"GET /api/telemetry/traces  listTraces  List telemetry traces"'
  reason: Distributed traces exposed for understanding the running service, described in the spec as observability.
    Maps to Observability Management rather than product usage telemetry, since the artefacts are runtime
    traces, not product usage events.