slug: avalanche
provider: Avalanche
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: Data API Usage Metrics
  spec_file: avalanche-data-api-usage-metrics-api-openapi.yml
  capability_id: BC-4270.50
  capability_id_l1: BC-4270
  capability_name: API Consumption Governance
  confidence: 0.85
  evidence: GET /v1/apiUsageMetrics  getApiUsageMetrics  Get usage metrics for the Data API; GET /v1/apiLogs  Get
    logs for requests made by client
  reason: Operations expose API consumption usage metrics and request logs for the vendor's public developer
    API, which matches API Consumption Governance (quotas, rate limits, usage analytics).
- tag: Webhooks
  spec_file: avalanche-webhooks-api-openapi.yml
  capability_id: BC-4270.80
  capability_id_l1: BC-4270
  capability_name: Webhook & Event Subscription Management
  confidence: 0.75
  evidence: POST /v1/webhooks createWebhook 'Create a webhook'; 'Generate or rotate a shared secret';
    'Add addresses to EVM activity webhook'
  reason: Operations are the full lifecycle of outbound event subscriptions exposed to external developers
    — create/list/update/deactivate webhooks, rotate signing secret, manage subscribed addresses. This
    matches Webhook & Event Subscription Management within the developer platform/API ecosystem, rather
    than being internal plumbing of another business process.