slug: databento
provider: Databento
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: Billing
  spec_file: databento-billing-api-openapi.yml
  capability_id: BC-4250.30
  capability_id_l1: BC-4250
  capability_name: Invoicing & Statement Management
  confidence: 0.8
  evidence: GET /v0/billing/invoices  List Invoice; GET /v0/billing/invoice/download/{invoice_id}  Download
    Invoice; schemas InvoiceListView, DataUsageByDatasetView, PlanSubscriptionItem
  reason: Operations list, detail, preview and download invoices, track credits and team budgets against
    metered data usage for a pay-as-you-go subscription service — subscription billing, centred on invoicing
    and statements.
- tag: Usage
  spec_file: databento-usage-api-openapi.yml
  capability_id: BC-4250.10
  capability_id_l1: BC-4250
  capability_name: Usage Metering
  confidence: 0.75
  evidence: 'GET /v0/usage/mtd_usage  Get Mtd Usage ... GET /v0/usage/report  Get Data Usage Report ...
    schemas: MonthToDateUsage, DataUsageRecord'
  reason: Aggregated data-usage records and month-to-date usage per user and per team, in a service the
    vendor describes as 'pay-as-you-go billing per byte streamed'. This is metering and aggregation of
    consumption that feeds rating and billing. Some overlap with API consumption analytics, hence not
    higher.