specification: FinOps Framework
specificationVersion: '1.0'
schema: https://www.finops.org/framework/
provider: Abstract API
providerId: abstract-api
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: true
tags:
  - Data Validation
  - Geolocation
  - Email Verification
  - FinOps
  - FOCUS
description: FOCUS-aligned FinOps for Abstract API — tiered subscription with selectable monthly request
  volume per product. Each product (email, phone, IP, company) is a separate billable line and meter.
sources:
  - https://www.abstractapi.com/api/email-verification-validation-api
  - https://docs.abstractapi.com/
  - https://focus.finops.org/focus-specification/v1-3/
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: Abstract API, Inc.
serviceCategory: Data Validation / Enrichment
billingModel:
  pricingCategory: Tiered Subscription
  billingFrequency: Monthly
  billingCurrency: USD
  chargeCategories:
    - Purchase
    - Usage
    - Adjustment
    - Refund
    - Credit
focusColumns:
  ServiceName: Abstract API
  ServiceCategory: Data Validation / Enrichment
  ProviderName: Abstract API
  PublisherName: Abstract API, Inc.
  InvoiceIssuerName: Abstract API, Inc.
  BillingCurrency: USD
  ChargeCategory: Purchase
  PricingCategory: Tiered Subscription
  PricingUnit: request
meters:
  - name: monthly_request_quota
    description: Selected monthly request volume for the active plan/product (e.g., 5k, 25k, 150k).
    unit: request
    aggregation: max
    dimensions:
      - product
      - plan
      - tier
  - name: requests_consumed
    description: Actual request count made against the API key, drawn from the monthly quota.
    unit: request
    aggregation: sum
    dimensions:
      - product
      - api_key
      - status_code
  - name: rate_throttle_events
    description: Count of 429 throttled responses (signals that the 3 req/sec ceiling is being hit).
    unit: event
    aggregation: sum
    dimensions:
      - product
      - api_key
  - name: plan_month
    description: Monthly subscription line item for the active plan tier.
    unit: month
    aggregation: count
    dimensions:
      - product
      - plan
principles:
  - name: Visibility
    description: Use the Abstract API dashboard's request-counter and the per-product usage page to track
      consumption against the selected monthly volume tier.
  - name: Allocation
    description: Issue separate API keys per product / service / environment so requests can be attributed
      to consuming applications when reconciling the monthly invoice.
  - name: Optimization
    description: Cache validation results client-side (especially email and IP enrichment) to stay inside
      the tier; right-size the monthly volume sub-tier each renewal cycle and switch to annual for the
      10% discount when usage is steady.
  - name: Accountability
    description: Engineering owns API key issuance and caching; the consuming product team owns the monthly
      request budget; finance owns the renewal decision and annual-vs-monthly billing trade-off.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com