This public pricing snapshot is organized by provider so teams can review model catalogs without scrolling through one oversized table. The current snapshot date is April 22, 2026.
Apostic uses this view to help clients narrow down model families for Voxvey Cortex, internal chat, enterprise search, coding, reasoning, multimodal tasks, and provider consolidation.
Pricing on these pages is presented as a published snapshot, not a promise that vendor pricing will never change afterward.
OpenAI, Anthropic, Gemini, Perplexity, Mistral, xAI, Cloudflare, and OpenRouter each get their own page to keep long catalogs easier to scan.
Apostic can bill and consolidate usage across providers instead of pushing clients into a separate commercial conversation for every model family.
Counts below include wildcard summary rows, provider catalog rows, and any priority rows where they apply.
General-purpose chat, reasoning, search, coding, realtime, audio, image, video, moderation, and embedding endpoints available through Apostic billing and Voxvey Cortex workflows.
Claude models for chat, reasoning, and multimodal enterprise workflows where long context and strong writing quality are a fit.
Gemini chat, search-aware, vision, audio, image, video, and embedding endpoints for enterprise copilots and search experiences.
Perplexity models and presets for grounded search, online answers, and research-style enterprise workflows.
Mistral chat, vision, reasoning, coding, OCR, and embedding endpoints suited to European-model preference and cost-sensitive deployments.
Grok chat, coding, reasoning, search, and multimodal models for organizations that want xAI access under centralized Apostic billing.
Cloudflare-hosted models and Workers AI routes for teams building inference close to edge or app workloads.
Aggregated access routes across many upstream providers for teams that want optional routing and additional model breadth.
Pricing matters, but model selection usually depends on whether the task is search-heavy, reasoning-heavy, code-heavy, multimodal, realtime, or subject to stricter deployment and governance requirements.
The “Details” marker from the source export is treated as source metadata only and is intentionally not rendered as a dead customer-facing link.
Bring the workflow, data boundaries, and deployment constraints. Apostic can help map them to Voxvey Cortex and the right provider mix.