specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Shell
providerId: shell
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Energy
  - Mobility
  - Fleet
  - Fuel Cards
  - FinOps
  - FOCUS
description: FinOps shape for Shell B2B APIs — gated to existing partners with no public per-call pricing.
  The dominant cost line is the underlying B2B contract (fuel-card transactions, mobility services, loyalty
  programme); the API itself is typically a free service layer on top of that contract. Reconciliation
  to FOCUS columns is best-effort because Shell does not publish a meter-level rate sheet.
sources:
  - https://developer.shell.com/api-catalog
notes: No public per-meter pricing. Cost flows through the underlying Shell B2B agreement (fuel-card
  fees, transaction commissions, etc.) rather than per-API metering.
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/
publisherName: Shell plc
serviceCategory: Energy / Mobility B2B
billingModel:
  pricingCategory: Embedded in B2B Contract
  billingFrequency: Per-Invoice
  billingCurrency: USD
  chargeCategories:
    - Purchase
    - Usage
focusColumns:
  ServiceName: Shell B2B APIs
  ServiceCategory: Energy / Mobility B2B
  ProviderName: Shell
  PublisherName: Shell plc
  InvoiceIssuerName: Shell plc
  BillingCurrency: USD
meters:
  - name: card_transactions
    description: Fuel-card transactions processed under the partner's Shell agreement
    unit: transaction
    aggregation: sum
    dimensions:
      - card_program
      - country
  - name: cards_managed
    description: Active cards under management for a B2B partner
    unit: card
    aggregation: max
    dimensions:
      - card_program
  - name: api_requests
    description: API requests against Shell developer endpoints (operational meter; not billed at the
      API layer)
    unit: request
    aggregation: sum
    dimensions:
      - api
principles:
  - name: Visibility
    description: Visibility comes from the partner's Shell B2B portal and invoice (transaction reports,
      card-level statements). API call volume should be instrumented client-side because Shell does not
      publish a usage API.
  - name: Allocation
    description: Allocate fuel-card and transaction cost by cost center / fleet / driver via card metadata;
      align with the partner's existing fuel-card cost-allocation process rather than re-deriving it
      from API logs.
  - name: Optimization
    description: Optimization happens at the Shell B2B contract level (volume rebates, network preference)
      rather than via API tuning. On the integration side, batch transaction queries and respect partner
      rate limits to avoid disruption.
  - name: Accountability
    description: Procurement / Fleet management owns the Shell partner relationship. Integration-platform
      engineering owns API hygiene and is the contact for partner-side rate-limit issues escalated through
      the Shell account team.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com