Meta Model API vs Vertex AI (Gemini Enterprise Agent Platform)

Meta Model API 40

No status page with readable component history. The error guide's dev.meta.ai/status link now opens a Model API Status page, which showed "Status information is unavailable" to our reader on 4 November, its content drawn by script that we don't request, and the documented GET /v1/status reports only the current state (0). No readable incident history (5). Rate limits published per team and per model, 3,000 RPM and 4,000,000 TPM for muse-wonder-1.0, 150 RPM and 3,000,000 TPM for the contributor variants, 600 background submissions a minute (15). 429 and 503 carry Retry-After (60 seconds for service_overloaded and backend_unavailable), with backoff-with-jitter guidance, rate-limit headers on every token response and a documented mid-stream server_shutting_down event to retry, a generation call read as stateless as gemini-api's (15). No SLA found, and the terms let Meta throttle or suspend access without notice (0). Muse Wonder is labelled a preview. Muse Spark 1.3 carries no preview label, but the API opened on 8 July 2026 as a public preview and we found no general-availability notice, so half (5 of 10, the 12 October partial, kept). 0 + 5 + 15 + 15 + 0 + 5 = 40.

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.

Meta Model API 46

Model reading. Muse Wonder launched on 12 October 2026 (30). No deprecation policy or notice period found. All three Muse Spark versions are still served, so no retirement has tested one (0 of 12). Dated launches on the API since 6 August that we read, Muse Image on 25 August, Muse Voice Transcribe on 3 September and Muse Wonder on 12 October (8 of 8). Muse Code leaving beta on 31 August is a separate product and isn't counted. No Model API changelog. A help centre with support tickets, answered 'typically within two business days' by Meta's own account, which we didn't test (8 of 15). No SDK of Meta's own for the API (0 of 15, 0 of 10). 30 + 0 + 8 + 8 + 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.

Meta Model API 53

Closed service with clear terms, under California law with AAA arbitration for Meta Platforms, Inc. and Irish law and courts for Meta Platforms Ireland Limited, with liability capped at the greater of 12 months of fees or $1,000. Muse Glimmer's open weights don't change the hosted service (15). The terms, the models page, the pricing page and the zero-retention help page agree that Standard content isn't used for training and Contributor content may be, but retention periods are not stated outside zero retention, and the privacy policy is Meta's general one (18 of 30). No deprecation policy or dated notices found, and the terms let Meta remove functionality without notice (0). A subprocessor list is linked from the terms but wasn't read, and no data locations were found (8 of 20). 15 + 18 + 0 + 8 = 41.

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).

Meta Model API 60

No OpenAPI or similar machine-readable contract found. The reference is Markdown pages with schema sections, and /openapi.json paths on dev.meta.ai return 404 (0). llms.txt at dev.meta.ai/llms.txt, and every docs page has a Markdown copy (10). The models page says when to choose Muse Wonder and when Muse Spark, and the tool-calling and structured-output guides state their limits, such as tool_choice only accepting auto and which schema keywords strict allows (16 of 20). JSON Schema tools and output, reasoning_effort an enum from minimal to max, a strict subset that returns 400 when violated, though tool_choice has one value (12 of 15). Curl, Python and TypeScript examples on each page and an error guide covering 400 to 504 with the error envelope, codes and a fix for each (15). Versioned model IDs (muse-spark-1.1 to 1.3, muse-wonder-1.0) and dated launch posts on the developer blog, but no API changelog (7 of 15). 0 + 10 + 16 + 12 + 15 + 7 = 60.

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).

Meta Model API 64

Model reading. Bearer keys per team, named, shown once and revoked by deletion, with rotation advice. No scopes, read-only keys or per-key limits found (20 of 30). The terms say Meta will not use Content submitted to the Standard Services to train Meta Models, and training applies only to the -contributor model IDs a caller picks. Content may still be used to develop and improve safety and security systems (17 of 20). Retention is 'as needed' for the service, the law, flagged violations and safety review, with no period stated. Zero data retention for qualified accounts through sales, with flagged content kept up to 2 years (10 of 15). The usage dashboard shows tokens and requests per day by model, with no per-key or per-call log found (5 of 15). No security.txt on dev.meta.ai. Meta's bug bounty at bugbounty.meta.com is named in the Muse Code SDK's security policy, and a security commitments page describes TLS 1.2 or later, PCI-DSS card handling and an ISMS, with no named certification for the API (12 of 20). 20 + 17 + 10 + 5 + 12 = 64.

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).

Meta Model API 75

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool calls on all three endpoints, parallel calls, tool search with deferred loading, built-in web search and a computer-use tool, but tool_choice accepts only auto, so a call can't be forced or forbidden (15 of 20). Output constrained to the JSON Schema on every surface (15). Automatic prompt caching with no setup, and cached input at 5 per cent of the input price on Muse Wonder (15). 1,048,576-token context on Muse Wonder and every Muse Spark version, with no long-context premium (15). No batch endpoint or discount found. Background responses run asynchronously at the normal price (0). No SDK of Meta's own. The docs use the OpenAI and Anthropic SDKs against compatible endpoints, the same reading as StepFun (0). OpenAI-style error envelope with type and code, per-status fixes and named retryable codes (15). 15 + 15 + 15 + 15 + 0 + 0 + 15 = 75.

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).