DeepSeek API vs Vertex AI (Gemini Enterprise Agent Platform)

DeepSeek API 35

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Model reading. One Bearer key per balance, no scoping found (20 of 30). The privacy policy, last updated 10 February 2026, says personal data is used to train models, with an opt-out by email to privacy@deepseek.com (0 of 20). Data kept for as long as needed to provide the services, with no period stated and no zero-retention route (5 of 15). Per-call logs or audit logs not found (5 of 15). Security programme 5 of 20 (was 0). The www.deepseek.com footer carries a Report Security Issue address, security@deepseek.com, per the 21 October reading used for DeepSeek's open-weight listings and its Search and Fetch API listing. No security.txt (404 on 17 October), disclosure policy, certification or bug bounty found. 20 + 0 + 5 + 5 + 5 = 35.

Vertex AI (Gemini Enterprise Agent Platform) 97

Model reading. OAuth 2.0 with IAM roles and service accounts, which the docs recommend for production, with API keys for testing. No key in a query string found in the docs we read (30). The training restriction in the Service Specific Terms says Google won't use customer data to train or fine-tune any model without permission, GA and pre-GA alike (20). Default in-memory caching for 24 hours that can be disabled, flagged prompts logged up to 90 days unless an abuse-monitoring exception is granted or the customer has a Cloud Master Agreement, the Interactions API storing by default, and Claude Fable 5 and Mythos 5 requiring 30-day retention shared with Anthropic (12 of 15, a judgement call matching the Fable exception on the Anthropic and Bedrock listings). Cloud Audit Logs, with Data Access logs off until enabled, and optional request-response logging to BigQuery (15). google.com security.txt valid to 2030-04-01, the Google VRP, and Generative AI on the platform in ISO 27001, 27017 and 27018 and SOC 1, 2 and 3 scope per the 1 October services-in-scope check for vertex-ai-tuning, not re-read on 6 October (20).

DeepSeek API 49

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). No OpenAPI document and no llms.txt found (0 and 0). API reference covers both the OpenAI and Anthropic formats. The chat completion reference, read on 2 October, describes each parameter with its range and default, such as max_tokens from 1 to 393,216 with 8K by default without thinking, but says little on when not to use one (14 of 20). Strict tool calls are documented, in beta at the /beta base URL, with a JSON Schema subset (object, string, number, integer, boolean, array, enum, anyOf, $ref) where every property must be required. JSON output mode carries no schema guarantee (10 of 15). The error codes page lists seven codes, each with a cause and a fix, but no example bodies (10 of 15). Dated updates page that names model changes (15). 0 + 0 + 14 + 10 + 10 + 15 = 49.

Vertex AI (Gemini Enterprise Agent Platform) 94

Model reading. Keyless discovery document for the Agent Platform API v1, revision 20260930, with 1,128 methods and 1,493 schemas (25). No llms.txt, but every docs page answers as Markdown at .md.txt, counted as for vertex-ai-tuning (10). Model cards give limits, capabilities and retirement dates, and the 3.8 Flash card says when to use 3.7 Flash instead, but the docs mix the Vertex AI and Agent Platform names, and the OpenAI page tells new users to call the Gemini Developer API instead (16 of 20). Structured output with response_schema and response_mime_type: application/json always follows the schema per the docs, and complex schemas fail with a 400 (15). Examples on every page and a 429 guide, but we found no full error code list for generateContent (13 of 15). Versioned v1 and v1beta1 APIs and release notes with entries on most working days, newest 5 November 2026 (15).

DeepSeek API 46

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Model reading. V4.1 Flash was upgraded to DeepSeek-V4.1-Flash-1017 on 17 October under the same deepseek-flash name and price, posted on the updates page the same day, 19 days before this check (30). Later updates entries are unread. No stated notice policy. deepseek-chat and deepseek-reasoner got three months, announced on 24 April for 24 July. One dated notice with no stated period partly meets the line, and the earlier partial award is held (4 of 12). Model churn covers the V4 Flash retirement on 10 September and the V4 Pro shutdown set for 14 September, announced on 13 August and withdrawn on 10 September. The 24 July shutdown has left the 90-day window. A retirement and a withdrawn shutdown inside it keep churn at the bottom of its range (0 of 8). Dated updates page, and the docs list api-service@deepseek.com and a Discord server for support. We didn't test whether either answers (12 of 15). No official SDKs or SDK repository (0 of 15, 0 of 10). 30 + 4 + 0 + 12 + 0 + 0 = 46.

Vertex AI (Gemini Enterprise Agent Platform) 91

Model reading. Gemini Omni 1.2 Flash GA on 5 November, Grok 4.7 GA on 27 October, Gemini 4 Argon GA on 13 October and Claude Haiku 5.5 on 7 October 2026 (30). Stable models stay at least 12 months, and since 6 October Gemini 4 Argon and Gemini 3.8 Flash are in that tier, while 3.7 and 3.6 Flash remain short-term with at least 45 days' notice once a date is set (10 of 12, up from 8). Gemini 2.5 Pro, Flash and Flash-Lite were due to retire on 20 October, three models on one date after more than 12 months, with replacements named. We didn't check partner model retirements (6 of 8, down from 8). Dated release notes on most working days, newest 5 November, and Cloud Customer Care (15). python-genai replies not sampled this run (5 of 10). Current SDKs, google-genai 3.0.0 on 6 November and @google/genai 3.0.0, and google-cloud-aiplatform 2.7.0 on 28 October 2026 (15). Supported runtimes stated, Python 3.10 or later and Node 20 or later, per the 6 October check (10). Unchanged at 91.

DeepSeek API 60

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Status page at status.deepseek.com, run on Flashduty, with per-API components and a readable feed (20). The recorded feed lists 36 incidents from 22 July to 15 October. Four touch only web search, 27 are degraded performance, and five are partial unavailability, one of them (12 October) the web chat only. Of the four that hit the API, 28 July (7 minutes) has left the 90-day window and 2 September lasted 31 minutes. 14 September (18:30 to 21:30 UTC) left the V4.1 Flash API and chat partly unavailable for three hours, and 15 October (00:11 to 05:04 UTC) left the V4 Pro and V4.1 Flash APIs and chat partly unavailable for 4 hours 52 minutes. Two majors in 90 days sit between one (10) and several (0), so 5. 16 October to 5 November is unread and earns nothing beyond the recorded award (5). Concurrency caps published per account, 2,500 on Flash and 500 on V4 Pro, and requests that haven't started inference after 10 minutes are closed (15). The rate-limit and error pages document 429, and advise a brief wait and retry on 500 and 503, with no Retry-After header, backoff schedule or statement that a retried call is safe (10 of 15). No SLA found (0). V4 Pro and V4.1 Flash are GA (10). 20 + 5 + 15 + 10 + 0 + 10 = 60.

Vertex AI (Gemini Enterprise Agent Platform) 99

Google Cloud status dashboard with per-product history (20). Its incident feed, read on 6 November, has no incident naming Vertex Gemini API, Gemini or the Agent Platform in the 90 days. The regional incidents of 20 August, 1 September and 20 October (europe-west2) and the Cloud Storage incident of 8 and 9 October didn't list it among affected products (30). Standard PayGo publishes usage tiers by 30-day spend with baseline throughput, 2,000,000 to 50,000,000 tokens a minute for Flash models and 500,000 to 10,000,000 for Pro, plus quota tables for other methods (15). A 429 page says to use the global endpoint and truncated exponential backoff, and a retry-strategy page (15). SLA of 99.5 per cent a month on generateContent and streamGenerateContent, 95 per cent for short-term availability models, and a latency SLO on Provisioned Throughput. The 429 page says pay-as-you-go 429s don't count toward the SLA error rate (10). Gemini 4 Argon reached GA on 13 October and Gemini 3.8 Flash moved to the 12-month tier, and the v1 API, 3.5 Flash-Lite and Claude Opus 5.5 are GA, but express mode was Preview at the 6 October check (9 of 10, up from 8). Up from 98 on 6 October.

DeepSeek API 70

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool calls through both request formats, and the API reference documents tool_choice as none, auto, required or a named function (20 of 20). Strict schema-enforced tool calls in beta, JSON output without a schema guarantee (10 of 15). Disk cache on by default with cheaper hits, per the listing (15). 1M-token context and up to 384K output (15). No batch API documented (0). No official SDKs, you use the OpenAI or Anthropic client (0). Seven error codes with a fix for each, 402 for an empty balance (10 of 15). 20 + 10 + 15 + 15 + 0 + 0 + 10 = 70.

Vertex AI (Gemini Enterprise Agent Platform) 97

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with FunctionCallingConfig mode ANY and allowedFunctionNames to force a named tool (20). Schema-guaranteed JSON output (15). Implicit and explicit context caching, cached input at 0.1x, $0.075 per million on 3.8 Flash through 31 December (15). 1,048,576-token context on 3.8 Flash, a unified 1,048,576-token input and output limit on Gemini 4 Argon, and 1,000,000 on Claude Opus 5.5 (15). Flex/Batch at half price on Gemini (10). Gen AI SDKs for Python and JavaScript among others, and the OpenAI libraries work with Google Cloud auth (10). 429 handling documented per quota framework, with standard Google status codes elsewhere (12 of 15).

DeepSeek API 65

Per the 17 October check, not re-read on 5 November (DeepSeek's terms bar automated access, so nothing on DeepSeek's hosts was requested). Closed service with clear terms under PRC law. The model weights are published, which doesn't change the hosted service (15). The privacy policy of 10 February 2026 is consistent on training by default and storage in the PRC, but publishes no retention period and no DPA (10 of 30). Dated notices on the updates page, undercut by a shutdown announced and withdrawn within a month and a reroute with no prior entry (10 of 20). Data location disclosed as the PRC, third parties named only by category (10 of 20). 15 + 10 + 10 + 10 = 45.

Vertex AI (Gemini Enterprise Agent Platform) 90

Closed service under the Google Cloud terms, with the Gen AI SDKs under Apache-2.0 and a public discovery document (18, as for Bedrock's open service models). The zero data retention and abuse monitoring pages agree with the Cloud terms and give periods for each case, 24 hours in memory, up to 90 days for flagged prompts, 30 days for Advanced AI models, 3 days for Search grounding logs and 30 days for Maps grounding, and say which can't be switched off (27 of 30). A dated model versions table with release and retirement dates and a stated 12-month or 45-day policy, but on 6 November it still listed Gemini 2.5 Pro, Flash and Flash-Lite as available with a 20 October 2026 retirement date and left them out of the retired table (18 of 20, down from 20). The Cloud subprocessor list with locations, per the 1 October vertex-ai-tuning check, regional and multi-region endpoints, and per-model ML processing locations on the partner model cards (20).