specification: FinOps Framework
specificationVersion: '1.0'
alignedWith:
  framework: FinOps Foundation Framework
  frameworkUrl: https://www.finops.org/framework/
  dataSpec: FOCUS
  dataSpecVersion: '1.3'
  dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/
provider: Browserbase
providerId: browserbase
publisherName: Browserbase
serviceCategory: API
created: '2026-05-22'
modified: '2026-05-22'
tags:
- Headless Browser
- Browser Infrastructure
- Web Automation
- AI Agents
- Web Scraping
- Stagehand
- Playwright
- Puppeteer
- Web Search
- Web Fetch
- Model Gateway
- MCP
- Session Recording
- Agent Identity
- FinOps
- Cost Management
- FOCUS
description: FinOps framework alignment for the Browserbase API surface. Provides a FOCUS-shaped mapping for cost allocation,
  usage measurement, and unit-economics reporting.
principles:
- name: Visibility
  description: Make API consumption costs visible to engineering, product, and finance teams in near real-time.
- name: Allocation
  description: Tag every chargeable API call with the consuming team, environment, application, and feature so cost can be
    allocated.
- name: Optimization
  description: Continuously evaluate request patterns, caching, batching, and tier selection to reduce cost per useful unit
    of work.
- name: Accountability
  description: Establish budget owners and chargeback / showback flows for each consuming team.
domains:
- name: API Consumption
  description: Per-call and per-quota usage charges across the Browserbase API surface.
  costDrivers:
  - request_volume
  - tier_selection
  - feature_use
  focusMapping:
    ChargeCategory: Usage
    ChargeClass: Consumption
    ServiceCategory: API
    ServiceSubcategory: Provider API
focusFields:
  required:
  - BillingPeriodStart
  - BillingPeriodEnd
  - ChargeCategory
  - ChargePeriodStart
  - ChargePeriodEnd
  - ProviderName
  - PublisherName
  - InvoiceIssuerName
  - ServiceName
  - ServiceCategory
  - BilledCost
  - EffectiveCost
  - ListCost
  - ContractedCost
  - PricingCategory
  - PricingUnit
  - PricingQuantity
  recommended:
  - SubAccountId
  - SubAccountName
  - ResourceId
  - ResourceName
  - ResourceType
  - Region
  - Tags
notes:
- Reconcile the scaffolded mapping above against Browserbase's actual invoice / billing model.