Repository navigation
Remove Transcribe pricing - #737
Merged
Merged
Conversation
Contributor
|
🌿 Preview your docs: https://cohere-preview-97a9bf1c-8b4a-435d-b1fd-62b6b80a7720.docs.buildwithfern.com |
manoj-cohere
approved these changes
Apr 9, 2026
Contributor
|
🌿 Preview your docs: https://cohere-preview-f6cd4dc1-623d-4043-b5e6-3d5edd30e250.docs.buildwithfern.com |
emanic-cohere
approved these changes
Apr 9, 2026
alhassankhedr-cohere
added a commit
that referenced
this pull request
Jun 26, 2026
Transcribe pricing was intentionally removed from public docs in #737; drop the row re-added to the new Standard Vault pricing table. Transcribe remains listed as a supported model.
alhassankhedr-cohere
added a commit
that referenced
this pull request
Aug 7, 2026
* Add Model Vault as a top-level docs tab Surface Model Vault (Encrypted AI) as its own top-level tab in both v1 and v2 navigation, with a starter Overview page, instead of leaving it buried under Guides and concepts > Deployment options. * Restructure Model Vault docs into product-first sections Reorganize the Model Vault docs around a shared core plus two product subsections (Standard Vault, Encrypted Vault). The nav now reads Overview -> Quickstart -> Standard Vault -> Encrypted Vault -> shared sections (Deploy & manage, Inference & APIs, Operate & observe) -> Model Vault with North -> Resources, so readers self-select their vault type before the shared how-to flow. Adds skeleton pages closing the Baseten gap analysis (scaling, versioning, rate limits, async/batch, logs & tracing, errors, SLA, embeddings & reranking, shared-API migration), Standard Vault security & multi-region pages, and type-specific API usage pages. Wires everything into v1.yml and v2.yml. * Add visual hero and image cards to Model Vault overview Frame the dashboard screenshot in a browser-window mockup and present the "Why Model Vault" and "Two types of vault" sections as homepage-style image cards with custom illustrations, rather than Fern's compact default cards. * Broaden Guides and concepts description to cover products Update the home page card copy from API/training-focused wording to "In-depth guides on how to use our APIs and products" so it reflects product documentation, not just the platform API. * Add product-first Get Started intro and reposition platform/products Introduce a new "Welcome to Cohere" page that frames the Cohere Platform, Model Vault, and North as peer products, each suited to a different need. Move the platform-specific pages into a renamed "Cohere Platform" section below Model Vault, and make the platform overview product-aware. * Reorder nav: Cohere Platform above Model Vault Move the Cohere Platform section above Model Vault in v1/v2 nav to mirror the Welcome page's product order (Platform first, then Model Vault). Also reword the Guides and concepts description to lead with products. * Refine Model Vault overview/quickstart and reorder vault nav Update the Model Vault overview with researched, accurate positioning (no rate limits, no noisy neighbors, real monitored metrics), name the two vault types as bullets, and swap in a new dashboard hero. Reorder the Standard/Encrypted sub-pages and move both type sections below the shared Deploy/Inference/Operate sections in v1/v2. Add Choose Vault Type and Attestation screenshots to the quickstart, creating-a-vault, and verifying-deployment pages, and tighten the quickstart steps and next steps. * Fix relative image path in verifying-deployment The attestation screenshot used ../../ but the page lives one level deeper (encrypted/), so the path resolved outside pages/. Use ../../../ so fern check passes and the image resolves. * Build out Model Vault Encrypted pages and update supported models Ground the encrypted vault docs (security model, attestation, verifying deployment, encryption/key management, API usage, supported models, compliance) in Cohere's confidential-computing stack, add the Passport architecture diagram, and add per-response attestation certificate / verifiable-via-API and positioning language. Refresh standard and encrypted supported-models with the current model lists and keep GPU references generic. * Address review feedback on welcome, Model Vault overview, and quickstart Broaden welcome lead-in beyond LLMs, rephrase the two-vault-types intro and drop the duplicated explanation, fix the misleading shared-compute and SLO card copy, soften the compliance comparison row, replace ambiguous "model card" wording, and strengthen the quickstart attestation-verification step. * Refresh Model Vault overview card images to brand palette Regenerate the six "Why Model Vault" and two vault-type card illustrations using Cohere's brand colors, and serve them as downscaled JPEGs (about 96% smaller) for faster page loads. * Fix CI: trim frontmatter descriptions to 50-160 chars and format Python snippet Shorten over-length meta descriptions on the welcome, Model Vault overview, standard security, and encrypted overview/api-usage/supported-models pages, and apply Black formatting to the encrypted api-usage code sample. * Trim Model Vault docs to published pages Remove the 16 still-skeleton pages from the nav and delete their files, convert encrypted/pricing into a short real page, trim api-access skeleton sections, and scrub inbound links so fern check passes with 0 errors. * Update attestation diagram to JPG and expand passport flow Replace the passport architecture PNG with a JPG that renders correctly and uses generic GPU labels, and enrich the end-to-end flow with mutual-attestation key sharing, transitive client trust, and OHTTP routing-metadata details. * Group encrypted vault security pages under a Security subsection Move the confidential-computing, security model, attestation, verification, key management, and compliance pages into a nested Security subsection under Encrypted Vault, leaving overview, supported models, API usage, and pricing at the top level. * Use vector SVG for attestation flow diagram Replace the rasterized JPG with a pure-vector SVG (~88 KB) that stays sharp at any zoom, and force a white background so it renders correctly in dark mode. * Rename Vaults Dashboard to Home Page and drop "dashboard" wording Rename the Vaults Dashboard page to Home Page (new slug docs/model-vault/home) and replace Model Vault "dashboard" references with "the Model Vault app" to avoid confusion with dashboard.cohere.com. Also refine welcome wording (models are not identical across products; verifiably private inference). * Replace "fails closed" with "refuses the connection" wording Use clearer connection-refused phrasing across the Model Vault attestation docs instead of the "fails closed" jargon. * Rename home page slug to vault-home and title to Model Vault Home Page Use the docs/model-vault/vault-home slug and the clearer "Model Vault Home Page" title, updating internal links accordingly. * Remove redundant vault-type bullet in Creating a Vault The vault type is already chosen in the first step, so drop the duplicate bullet in the configuration-panel list. * docs(model-vault): refine encrypted vault docs and TNG framing - Define TNG (Trusted Network Gateway) on first use and present both the in-SDK client and standalone proxy forms across encrypted pages - Remove claims that model weights are encrypted/protected (not yet supported) - Clarify end-to-end encryption terminates inside the TEE - Correct attestation timing (per-response certificate, not per-connection) - Point the encrypted "call your vault" step to the encrypted API page - Remove single-GPU references and reframe encrypted model support as beta * docs(model-vault): refine confidential computing and attestation accuracy - Ground confidential computing protections in memory encryption, isolation, and integrity, not isolation alone - Name the attestation service (verifier) and Intel Trust Authority in the primer - Correct attestation flow: hardware produces signed evidence; the attestation service issues the attestation result - Distinguish side-channel vs physical attacks and fix physical-attack examples - Consolidate residual risks into the Security Model and remove the duplicate section from the primer - Trim compliance page sections * docs(model-vault): add Encrypted Vault FAQ and refine trust wording Add a curated Encrypted Vault FAQ (data privacy, attestation, trust boundary, keys, models/performance, compliance) under the Encrypted Vault nav after Pricing. Reword "enforced by hardware, not by policy" to contrast against operational trust (since Kata and ITA policies are part of enforcement) across the FAQ, compliance, and security-model pages. * docs(model-vault): split API docs per vault type, add generative pricing - Replace the shared "Calling a Vault over the API" page with symmetric per-vault pages: Standard (SDK, raw HTTP, OpenAI-compatible direct) and Encrypted (same methods via the TNG client or proxy). - Add generative and speech hourly pricing to Standard Vault pricing. - Refine attestation trust framing and remove em-dashes across the docs. * docs(model-vault): remove Cohere Transcribe pricing Transcribe pricing was intentionally removed from public docs in #737; drop the row re-added to the new Standard Vault pricing table. Transcribe remains listed as a supported model. * docs(model-vault): format python snippets in standard api page Apply check_python_code_snippets.py formatting to satisfy CI. * docs(model-vault): reorder Encrypted Vault FAQ sections Lead with Getting started and Compliance, then Data and privacy, trust boundary, encryption and keys, verification, and models. * docs(model-vault): simplify encrypted vault attestation docs (#765) Co-authored-by: Cursor <cursoragent@cursor.com> * docs(model-vault): update Model Vault Encrypted usage (#766) * docs(model-vault): update Model Vault Encrypted usage * docs(model-vault): expand API usage section for Cohere OHTTP proxy * fix(docs): update OHTTP proxy details * docs(model-vault): reorder OHTTP proxy options (#767) * docs(model-vault): update Model Vault Encrypted usage * docs(model-vault): expand API usage section for Cohere OHTTP proxy * fix(docs): update OHTTP proxy details * docs(model-vault): reorder OHTTP proxy options Lead with the standalone Cohere OHTTP proxy as Option 1 and move the coming-soon embedded client to Option 3, so the currently usable path is presented first. --------- Co-authored-by: Shariq Khalil Ahmed <shariq.ahmed@cohere.com> * docs(model-vault): format encrypted API usage python snippets Apply check_python_code_snippets.py (Black, line length 70) to the OHTTP proxy examples so the "Fail if changes are detected" CI check passes. * docs(model-vault): remove model header from encrypted API usage examples (#784) * docs(model-vault): remove model header from encrypted API usage examples * docs(model-vault): update docker image version in encrypted API usage * docs(model-vault): update Docker image version to latest in encrypted API usage (#786) * docs: describe North Mini Code as a model, not the North platform The models list linked North Mini Code but described North, our agentic platform, which misrepresented both. Also drop an unused httpx import from the OHTTP proxy example. * docs(model-vault): fix dead data-residency anchor on compliance page The GDPR bullet linked to a #data-residency section that was removed when skeleton pages were trimmed. CI's link checker ignores same-page anchors, so it went unnoticed. * docs(model-vault): address review feedback on vault pages Trim content that would go stale as models ship and clarify wording flagged in review: - Collapse the nested model examples on Creating a Vault into a single bullet, keeping the performance tier detail the tier suffixes implied - Reduce both Supported Models tables to model families and point to the creation dropdown and models overview for specific versions - Link Standard and Encrypted inline from the Model Vault overview - Replace the ambiguous "turn down" pause warning, which also read as applying to resume - Move "Calling a Vault over the API" into the Standard-specific list, since it links to a Standard-only page - Drop the redundant "Etc." bullet from Monitoring * docs(model-vault): use path-relative links and de-duplicate FAQ answers Convert the 206 root-relative /docs and /reference links across the Model Vault and Get Started pages to URL-relative form, per review feedback. These links resolve against the page's published URL, and every page is served under both /docs/... and /v2/docs/..., so a root-relative target hard-codes the v1 route and silently drops v2 readers into v1. The number of "../" segments is derived per page from its slug depth: overshooting clamps at the site root and strips the version prefix, which fails silently rather than 404ing. Also stop the FAQ from restating beta pricing and the Encrypted model list. Both answers now defer to their canonical page; the model list had already drifted out of sync with the trimmed table. Remaining beta-scoped content is tracked in SIP-702. * docs(model-vault): satisfy the new markdownlint CI gate Main added markdownlint to CI while this branch was in review, and these pages had never been linted against it. Auto-fixable: blank lines around code fences and one heading in encrypted/api-usage.mdx and quickstart.mdx, and a list indent in creating-a-vault.mdx. No wording or code changed. The quickstart step headings become h2. They were h3, which tripped MD001 because the implied baseline from the frontmatter title is h1. Whether the rule fires at all depends on where a blank line falls relative to the <Steps> tag, which is why some existing quickstarts get away with h3. The v2 quickstarts already use h2 inside <Steps>, so this follows the convention that lints clean. Nothing links to these anchors and anchor slugs derive from the text, so no links break. * docs(model-vault): drop the unreleased embedded OHTTP client Per review, document the embedded client when it ships rather than carrying a "coming soon" section. Removes Option 3 and its pip install cohere[mve] snippet from encrypted/api-usage.mdx. Also updates the surrounding copy that assumed three options existed: the connect table row, the "three ways"/"three forms" framing, and two other pages that described the proxy as embedded in the SDK. Those now describe the two shipping forms, the standalone proxy and the conseel Python package. * docs(model-vault): bind the local OHTTP proxy to loopback The documented docker run used --network host with IN_HOST=0.0.0.0, which publishes the proxy on every host interface. Verified against a live encrypted vault: with that form the vault answered a chat request sent to the host's LAN address, so anything on the network could reach the trusted side of the tunnel. With -p 127.0.0.1:8080:8080 the same request is refused and the documented client flows still work end to end. IN_HOST stays 0.0.0.0 because it applies inside the container; the note says so to stop readers "hardening" it and breaking the container. Also renames "Verify before send" to "Verifying before send" for consistency with the other section headings. Nothing links to the old anchor. * docs: fix six links that 404 on the versioned copies of the-cohere-platform This page is served at /docs/, /v1/docs/ and /v2/docs/. Converting these links to ../docs/X made them resolve inside whichever prefix the reader is on, and these six targets only exist unversioned, so /v1/docs/foundation-models and friends 404. This is what the muffet link crawl caught. ../../docs/X resolves to /docs/X from all three prefixes, since the extra .. is clamped at root. That keeps the links path-relative as requested while restoring the behaviour the root-relative form had. The other 16 links on the page stay at ../docs/X on purpose: their targets do exist under every prefix, so staying in the reader's version is correct. Checked all 450 resolved link/prefix combinations across the 25 converted files against the preview; these 8 failures were the only ones. * docs(model-vault): tell readers to pin the proxy image in production The example uses :latest so the docs don't go stale on every proxy release, which the security review flagged as a mutable-tag risk. Keeping :latest but saying that production should pin puts that reasoning on the page instead of leaving it in a review thread. Worded as controlling when updates land rather than preventing change, since a version tag can still be moved; only a digest is immutable. * docs(model-vault): stop the FAQ restating pricing and the model list Both answers duplicated their canonical page, so each fact needed updating in two places. The cost answer repeated the beta pricing from pricing.mdx almost verbatim; the model answer repeated the six families from the supported-models table. Both now defer. The cost answer keeps only that Encrypted is priced separately, since that is the durable part of the answer. It deliberately does not describe what is on the pricing page: that page currently has no rates, just beta status and a sales contact. * docs(model-vault): recapture the two low-resolution screenshots Both were 1024x559, captured at 1x, so they pixelated when readers zoomed in, which is what the review flagged. Recaptured at 1905x920. Fixes four placements: the attestation panel on verifying-deployment and quickstart, and the vault type modal on creating-a-vault and quickstart. Both show the same UI and copy as before, so no surrounding prose changes. model-vault-dashboard-overview.png on the overview page is still 1000x1024 and is intentionally left as is. --------- Co-authored-by: yousef-cohere <yousef.sadr@cohere.com> Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Shariq Khalil Ahmed <shariq.ahmed@cohere.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR removes the Cohere Transcribe model from the pricing table, which previously included both Medium and Large performance tiers.
Note
Low Risk
Low risk documentation-only change that removes two
Cohere Transcribeentries from the Model Vault pricing table; no functional or behavioral code changes.Overview
Removes
Cohere Transcribepricing from theModel Vault Pricingtable inmodel-vault.mdx, leaving pricing listed only forEmbed 4andReranktiers.Reviewed by Cursor Bugbot for commit 264afbc. Bugbot is set up for automated code reviews on this repo. Configure here.