Browse pricing billing units used across the UsagePricing blueprint corpus. 63 categories with editorial coverage and company examples.
A billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
A 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.
A billing unit common in LLM and AI products, where customers are charged per input and output token processed.
A billing unit where customers are charged per API request, regardless of payload size or processing time.
A billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
A billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
A billing unit where customers are charged per gigabyte of data stored on the platform per month.
A billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
A billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
A billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
A billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
A billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
A billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
A 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.
A billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
A billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
A billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
A billing unit where customers are charged per gigabyte of data transferred out of the platform.
A billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
A billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
A billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
A billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
A billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
A billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
A billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
A billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
A billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
A billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
A billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
A billing unit common in translation and localization platforms where the metered object is the word count of content processed.
A 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.
A billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
A billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
A billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
A billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
A 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.
A billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
A billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
A billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
A billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
A billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
A billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
A billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
A billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
A billing unit where each hardware device or endpoint connected to the AI platform is metered.
A billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
A billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
A billing unit where each AI-generated report or analysis document is metered as a discrete output.
Blueprint companies whose billing unit is "builds". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "emails-sent". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "algorithms". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "edge-requests". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "exams". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "exports". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "gb-ingested". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "investigations". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "lines-of-code". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "rides". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "scores". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "sites". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "slides". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "tests". Browse the full list in the corpus.
View companiesBlueprint companies whose billing unit is "trace-spans". Browse the full list in the corpus.
View companies