What is it
Per-datapoint pricing is a billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
The unit sits across two pricing cultures that draw the line differently. In cloud FinOps platforms, a “datapoint” is a cost signal — a metered reading pulled from an AWS, GCP, or Azure billing API, or from an AI vendor like OpenAI or Anthropic. Finout ingests these signals into its MegaBill unified cost layer; Vantage turns them into cost reports, budgets, and anomaly alerts across 20+ providers. The value scales with how many signals get tracked, so “monitored cloud spend” — a buyer-legible proxy for datapoint volume — gates their pricing tiers.
In ML evaluation and training-data platforms, a datapoint is a stored, structured example. For Humanloop, it was one model completion enriched with inputs, human feedback, and evaluator judgments — the primary 2023 billing unit before it switched to the simpler “log” meter in 2024. Scale AI meters labeled records and annotation tasks — the same per-datapoint logic under a different name, applied to training data rather than observability.
The datapoint’s appeal is granularity: cost tracks the volume of data processed, not seat count or elapsed time. Its challenge is definitional — what counts as one datapoint is not self-evident, which makes the boundary a value-metric decision.
How it works
Per-datapoint billing typically operates in one of three modes: a quota-bundled subscription where each tier includes a fixed pool of datapoints per month, a committed contract that agrees an annual volume of data units, or a spend-gated proxy where the plan tier is set by the volume of cost signals tracked (expressed as monitored cloud spend).
| Mode | Mechanism | Example |
|---|---|---|
| Quota-bundled tier | Plan includes N datapoints/month; overage billed per 1,000 | Humanloop’s 2023 Starter: 1,000 datapoints/month included, then $10 per 1,000 |
| Committed contract | Annual deal priced per labeled task or data unit; no public rate card | Scale AI’s Data Engine: per-annotation rate quoted by sales as a committed annual volume |
| Spend-gated proxy | Plan tier gated by cost-signal volume, expressed as monitored cloud spend | Vantage: free Starter up to $2,500/month monitored spend; Pro up to $7,500; Business up to $20,000 |
Humanloop’s 2023 pricing shows the quota model most clearly. The Team plan bundled 100,000 datapoints/month at $1,000 (~$0.01 per datapoint at the included rate), overage at $4 per 1,000 — a 60% volume discount over the Starter overage of $10 per 1,000. Annual billing cut the platform fee 30%.
Unit math (Humanloop 2023): Monthly bill = plan fee + max(0, datapoints used − quota) × overage rate per 1,000 ÷ 1,000. A Team-tier customer processing 250,000 datapoints in a month would pay $1,000 + (150,000 × $4 / 1,000) = $1,600.
Scale AI applies the same per-unit logic at far larger volumes with no public rate card. Third parties cite indicative self-serve figures near 2 cents per image and 6 cents per annotation on the Data Engine, with the average enterprise contract reported near $93,000/year — implying large committed volumes negotiated per deal. Its free trial (first 1,000 labeling units, first 10,000 images) is the only publicly defined threshold. The introduction to usage-based pricing covers how committed-volume metering compares with pay-as-you-go.
Finout and Vantage abstract the datapoint meter behind spend tiers. Vantage’s free Starter covers up to $2,500 of monitored spend (3 users, 6-month retention); a team monitoring ~$6,000/month needs Pro (up to $7,500). The real variable is the count of cost signals ingested from AWS, Snowflake, OpenAI and others — spend is its proxy. Finout does the same: third parties report its Business tier near ~$1,000/month covering up to ~$500,000 of annual cloud spend, a scale-of-estate proxy for the datapoint volume its MegaBill layer processes.
Companies using this
Four corpus companies meter on datapoints across two categories: cloud cost intelligence (Finout, Vantage) and ML evaluation or training data (Humanloop, Scale AI). Each one’s value scales with the volume of structured data signals it processes, which makes the datapoint a natural meter even when the pricing page names it differently.
| Company | Product | Pricing model | Billing units | Free tier | Verified |
|---|---|---|---|---|---|
| Finout | Finout — enterprise cloud + AI cost observability (FinOps) platform | No | 2026-07-30 | ||
| Humanloop | LLM evals, prompt management & observability | Yes | 2026-06-09 | ||
| Scale AI | Data engine, GenAI platform & contributor marketplace | No | 2026-06-15 | ||
| Vantage | Vantage — cloud + AI cost monitoring and FinOps platform | Yes | 2026-06-10 |
Explore this theme in the knowledge graph
FAQ
What is per-datapoint pricing?
Per-datapoint pricing is a billing unit where each individual data measurement or signal ingested into a platform is metered and charged. It shows up in cloud cost intelligence tools like Finout and Vantage — which ingest cost signals from AWS, Azure, GCP and AI vendors — and in ML evaluation or training-data platforms like Humanloop and Scale AI that store labeled examples. What counts as one 'datapoint' varies by vendor: a cost-signal reading, a stored model completion, or one labeled annotation.
How is per-datapoint pricing different from per-event pricing?
Both meter discrete ingested units, but a 'datapoint' typically refers to a stored, structured measurement — a labeled example or a cost-signal snapshot — whereas an 'event' is more common in observability and streaming contexts with high volumes of ephemeral signals. Humanloop's 2023 pricing used 'datapoints' to mean stored model completions enriched with inputs, feedback, and evaluator judgments, distinct from the higher-frequency 'logs' meter it switched to in 2024.
Which companies price per datapoint?
Four companies in the UsagePricing corpus meter on datapoints: Finout and Vantage (cloud cost intelligence, where the datapoint is a cost signal, gated behind monitored-cloud-spend tiers) and Humanloop and Scale AI (ML evaluation and training data, where the datapoint is a stored labeled example). Each expresses the unit differently on its pricing page, but all scale cost with the volume of structured data signals processed.
How much does per-datapoint pricing cost?
Rates vary widely by context. Humanloop's 2023 datapoint tiers were Starter $100/month (1k datapoints, then $10 per 1k) and Team $1,000/month (100k datapoints, then $4 per 1k). Scale AI publishes no rate card, but third parties cite indicative self-serve figures near 2 cents per image and 6 cents per annotation. Vantage gates plans by monitored spend (free up to $2,500/month, Pro up to $7,500, Business up to $20,000), and Finout is quote-only with third-party reports around ~$1,000/month for its Business tier.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.