Skip to main content

How pricing works

Your price is the answer to three questions, in this order:
  1. What kind of files? Video, image, audio, PDF/document, text, or web pages — the modality.
  2. How much content? Each file type counts in its honest natural unit: images per file, video and audio per minute, PDFs per page, text per token, web per crawled page.
  3. What do you want to search by? Visual similarity, faces, on-screen text, document layout, transcripts, … — these plain-language capabilities are features.
For each file type: price = amount × (base rate + the search-by features you enable). Each tier is a flat monthly fee that includes a usage pool; anything beyond the pool bills at the same rate card. Worked example — 100 videos averaging 2 minutes each, searchable by what’s on screen (base video search) plus who appears (faces):
  1. What kind of files: video → bills per minute
  2. How much: 100 videos × 2 min = 200 minutes
  3. Search by: video search (base, 0.05/min)+faces(+0.05/min) + faces (+0.10/min)
200 min × (0.05+0.05 + 0.10) = **30.OnScale,the30**. On Scale, the 100 monthly pool covers it entirely; on Build, 10comesoutofthepooland10 comes out of the pool and 20 bills as overage. Everything is in dollars — rates, usage, invoices, and quotes are dollar-denominated end to end. Quote any planned ingestion before you run it with the estimate endpoint; it uses the same rating engine that bills you. For current numbers, see the pricing page. Manage your plan and payment method in Studio Billing.
Under the hood, each feature maps to a feature extractor — that deeper layer (which extractor implements a feature, extractor options, bring-your-own extractors) is documented in Features. You never need it to understand your bill.

Plans

Each tier is a flat monthly fee that includes a usage pool — a dollar allowance you can spend on any mix of modalities and features. Only usage beyond the pool bills as overage, at the same rate card.
BuildScaleEnterprise
Monthly price$25$250Custom
Included usage pool$10$100Custom
Pool buys, e.g.~6,600 images or 200 video minutes or ~6,600 pages~66,000 images or 2,000 video minutes or ~66,000 pages
OverageRate cardRate cardContract
Custom extractorsIncludedIncludedIncluded
SupportEmailPriority + private SlackDedicated
The pool is fungible — it isn’t a per-modality cap. The natural-unit equivalents above are just the pool divided by each base rate, so you can compare tiers at a glance. Spend it on whatever mix you actually ingest.
Enterprise runs on dedicated single-tenant infrastructure with custom contracts — see Single Tenant or contact sales.

The rate card

The API is the source of truth for rates. GET /v1/billing/pricing is public (no auth) and returns the live rate card — the same payload that studio, the homepage, and the billing engine read, so displayed numbers can never disagree with billed numbers:
Response abbreviated — the live payload covers all six modalities and every tier. How to read it:
  • modalities[].base — the per-unit rate for making that modality searchable. Creating any collection for a modality gets you its base feature.
  • modalities[].addons — features you opt into, priced per the same unit. kind: "external" rows are backed by external LLM inference and priced as usage-based passthrough (never flat-rated). kind: "included" rows (clustering, taxonomy enrichment) cost nothing extra.
  • usage_pools — each tier’s flat fee and included dollar pool, with derived natural-unit equivalents.
  • placeholder_ratesfalse means the rates are live and billable. (The nested v2 object in the payload is a deprecated alias of these same top-level keys and will be removed.)
Don’t hardcode rates into your own tooling — read them from GET /v1/billing/pricing, or quote concrete workloads with the estimate endpoint.

How a batch is priced

When you submit a batch, each object bills as: modality units x (base rate + enabled add-on rates). Example at the rates shown above: a 10-minute video in a collection with faces and onscreen_text enabled bills 10 min x (0.05+0.05 + 0.10 + 0.10)=0.10) = **2.50**.
  • Measured units — video/audio minutes come from measured duration (not file size), pages from actual page counts. Anything estimated at submit is trued up at batch completion, in both directions.
  • Batch minimum — batches bill at least $0.01.
  • Normalization included — content is normalized once at ingest (video to 720p mezzanine, images capped, audio to 16kHz mono). Originals stay untouched in your bucket. Collections that opt out with full_res: true bill at a 2x multiplier. See full resolution opt-out.
  • Deduplication — re-ingesting content Mixpeek has already processed (same content hash) skips extraction rather than re-billing full processing.

Storage

Vector and index storage bills at a single all-in rate: $0.33 per GB-month (storage.vector_storage_usd_per_gb_month). No separate per-vector charges.

Reads (queries)

Tiers include a generous query allowance; beyond it, reads bill at $2 per 1M queries (reads.overage_usd_per_1m_queries).

Estimate before you run

POST /v1/organizations/billing/estimate quotes planned ingestion — same rating engine, same rate card, so the quote matches the eventual charge:
The response itemizes dollars per (modality, feature), reports how much falls inside your remaining usage pool, and what would bill as overage. Full request/response details in Features → Estimate.

Tracking usage

Current-period usage is available in Studio Billing and via the usage API. Usage reports break down dollars by modality and feature:
  • units consumed per modality (minutes, images, pages, tokens) and per feature
  • storage GB-month and reads
  • pool consumption, overage, and the period’s total in dollars
You can set spending caps to limit overage through Studio Billing or the spending caps API.

How billing works

1

Sign up and choose a plan

Create an account at studio.mixpeek.com. Upgrade to Build or Scale from the billing page.
2

Add a payment method

Paid plans require a card on file via Stripe. Add or update your card in Studio Billing or through the payment method API.
3

Use Mixpeek

Your usage pool is available immediately and resets each cycle. Usage is metered continuously in dollars and visible in the dashboard.
4

Receive your invoice

Stripe generates a monthly invoice: your flat plan fee plus any overage, itemized by modality and feature. Invoices are in Studio Billing and via the invoices API.

MVS Standalone

Using Mixpeek’s vector store with your own embeddings (no extraction)? MVS bills separately: storage at $0.33/GB-month all-in, with per-tier query and write allowances. See the live mvs_plans and mvs_usage_rates in GET /v1/billing/pricing and the MVS overview.

FAQ

Credits are gone as a customer-facing concept — every surface (rates, usage, invoices, quotes) is dollar-denominated. If you see a legacy credits field in an older API response, it’s an internal ledger unit worth $0.001 (a milli-dollar); the dollar fields alongside it are canonical.
No. The estimate endpoint and the metering pipeline call the same rating engine against the same rate card. Estimated units (e.g. duration unknown at submit) are trued up from measured values at batch completion — in both directions.
No. It’s a fungible dollar pool — the natural-unit equivalents shown on tier cards are illustrations (pool ÷ base rate), not limits. Spend it on any mix of modalities and features.
No. The usage pool resets at the start of each billing cycle.
Yes. Upgrades take effect immediately and are prorated. Downgrades take effect at the start of the next billing cycle.
Features marked kind: "external" (e.g. multimodal_understanding) are backed by external LLM inference and priced as usage-based passthrough — their upstream cost is unbounded, so they’re never flat-rated. The pricing payload flags them with a pricing_note.
A custom:<plugin> feature derives its per-unit rate from the compute profile the plugin declares — the same machinery that prices native features. Quote it like anything else via the estimate endpoint.
Requests that exceed hard resource caps return 403 with type QuotaExceededError and an upgrade_plan hint. Overage within your plan simply bills at the rate card — no interruption.
All major credit and debit cards via Stripe. Enterprise customers can pay by invoice with net-30 terms.
Annual billing is available for Scale and Enterprise. Contact sales for details.