Gemini Developer API vs Hugging Face Inference Providers

Gemini Developer API 93

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling documented, and FunctionCallingConfig mode ANY with allowedFunctionNames forces a call to a named tool, with a VALIDATED mode that checks calls by constrained decoding (20 of 20). The structured output page, re-read on 1 November, says output adheres to the supplied JSON Schema and is syntactically correct JSON, and names the keywords constrained decoding doesn't enforce, while asking callers to validate values (13 of 15; the 12 October note's 10 rested on the page promising no constrained decoding). Context caching at 0.1x input, $0.075 per million on 3.8 Flash until 31 December, and implicit caching on gemini-4-argon, which doesn't support explicit caches (15). 1,048,576-token context on the default and flagship models (15). Batch half price (10). Official SDKs for Python and JavaScript (10). Documented error codes with backoff guidance (10 of 15, because 400, 402 and 403 are flagged as not retryable but recovery advice per code sits on a separate page we only skimmed).

Hugging Face Inference Providers 58

Router reading of the model checklist (tool use, structured output, caching, context, batch, SDKs, errors), as for openrouter. Tool calling through the OpenAI-compatible API with tool_choice, support flagged per provider in /v1/models (15 of 20). Structured output documented, support flagged per provider and false on some (10 of 15). No prompt caching guidance found, though the Enterprise usage API counts cached input tokens (3 of 15). Routes to models with up to 1,048,576 tokens of context per the model list, a judgement call since a router has no default model (15). No batch API (0 of 10). Official clients in Python and JavaScript, plus any OpenAI SDK (10). Errors not documented (5 of 15).

Gemini Developer API 50

Model reading. Keys live in a Cloud project. Since 28 May 2026 new keys are authorisation keys bound to a service account and restricted to the Gemini API, keys can be limited by IP or origin, unrestricted standard keys are rejected, and the docs give a leak checklist, per the API key page re-read on 1 November. No permission scopes, so 25 of 30, less 10 because the API reads a token from the URL. The Discovery document (revision 20261101) lists access_token, oauth_token and key as query parameters, and on 1 November a generateContent request with no credential answered 403 'Method doesn't allow unregistered callers' while one with a made-up ?access_token= answered 401 'Request had invalid authentication credentials' (ACCESS_TOKEN_TYPE_UNSUPPORTED), the deduction Google APIs took on 17 October and 1 November and Gemini Embedding and Gemini Live carry (15 of 30). Terms (effective 23 March 2026, re-read 1 November) say free-tier prompts and responses are used to improve Google products and human reviewers may read them, paid tier isn't used (10 of 20). Abuse monitoring on paid services is kept 'a limited period' with no number, grounding data 30 days, and since 26 October new paid projects store Generate Content requests by default unless store=false. No zero-retention route on this API was found (5 of 15). Request logs in AI Studio for billed projects (15). security.txt on google.com valid to 2030-04-01 with a vulnerability reward programme, re-read on 1 November. No certification naming the Developer API found, the reading Gemini Embedding takes (5 of 20).

Hugging Face Inference Providers 79

Model reading. Fine-grained user access tokens that can be limited to the Make calls to Inference Providers permission, rotated and revoked, plus a public revocation endpoint for leaked tokens, and organisation approval of fine-grained tokens on paid plans (30). Hugging Face says it doesn't store user data for training, but data handling past the router follows each provider's policy, with no per-request filter to exclude providers that train or retain (12 of 20). Request bodies and responses aren't stored when routed and debug logs are kept up to 30 days without user data or tokens, with provider retention outside that statement (10 of 15). Usage by model and provider in account settings, an Enterprise usage API, and Team and Enterprise admins can disable providers and set a spending limit (13 of 15). SOC 2 Type 2 for the Hub, of which the docs say Inference Providers is a feature, and security.txt valid to 2030 per the Inference Endpoints check; no bug bounty found (14 of 20).

Gemini Developer API 85

A keyless Discovery document at generativelanguage.googleapis.com/$discovery/rest?version=v1beta (revision 20261101, re-read on 1 November) types 86 methods and 225 schemas for GenerateContent, files, batches, caching and models, but not the Interactions API the guides now lead with (20 of 25). llms.txt at ai.google.dev/gemini-api/docs/llms.txt, with Markdown twins of each page (10). Reference not read in full, and the changelog and latest-model guide name the recommended models (15 of 20). Structured output accepts JSON Schema with enums, minimum, maximum, prefixItems and $ref, but the server ignores minLength, maxLength, minProperties, maxProperties and uniqueItems, per the structured output page re-read on 1 November (10 of 15). Examples on every guide and an API errors page with HTTP, blocked and content codes (15). Dated changelog and model versions (15).

Hugging Face Inference Providers 62

No OpenAPI document for the router (openapi.json paths answer 404). The task reference pages are generated from typed JSON Schema specs in huggingface.js, and the router's /v1/models gives a machine-readable catalogue, so 12 of 25. llms.txt for the Inference Providers docs and a Markdown twin of every page via .md (10). Guides say what each task and policy is for, with a quick setup page for coding agents (14 of 20). Parameter tables with types for chat completion, though response_format and tool_choice show as unknown types (9 of 15). Examples in Python, JavaScript and curl on every task page, but no documented error responses for the router (9 of 15). No changelog of its own; the Hub changelog doesn't cover it and dated changes are only in the hub-docs history (8 of 15).

Gemini Developer API 45

Status page at aistudio.google.com/status (robots.txt allows it), but on 1 November it still returned a script shell titled Google AI Studio with no components or history, so 10 of 20, and 5 of 30 for the incident line with no readable record, as the Gemini Live and Gemini Embedding listings read the same page. Google Cloud's status dashboard covers Vertex AI products, not this endpoint. Per-model RPM and TPM live in AI Studio. The public rate-limits page, re-read on 1 November, publishes tier rules, spend-based limits of $10, $50 and $200 per 10 minutes for Tiers 1 to 3, and batch queue limits (5 of 15). The troubleshooting page, re-read on 1 November, gives exponential backoff with jitter for 429 RESOURCE_EXHAUSTED and 503 UNAVAILABLE, says to retry 429, 408 and 5xx and not 400, 402 or 403, and says the Python SDK retries transient errors up to four times (15). No SLA found for the Developer API (0). The flagship gemini-4-argon went GA on 13 October 2026 and the default 3.8 Flash is GA, and the Interactions API the guides lead with has been Generally Available since June 2026. The listing's example and the SDKs default to the v1beta path, which Google labels beta, but the API versions page, read on 1 November, says the stable v1 path carries the Interactions API, generateContent, function calling and structured output and supports every model, so the surface is available as GA, the reading Gemini Embedding takes on the same endpoint. Gemini Live keeps a deduction because the Live API runs on v1beta only (10). Before 13 October the only Pro model was gemini-3.1-pro-preview (5 of 10).

Hugging Face Inference Providers 25

Hosted lines. status.huggingface.co is a Better Stack page with 90-day component history for the Hub, Inference Endpoints, Spaces, the CDNs and Jobs, but no component for Inference Providers or the router (10 of 20). With no component, there is no readable incident history for the surface agents call, and the feed's 23 items from 10 June to 7 October 2026 don't name it (5). No rate limits for the router were found; the Hub rate-limits page gives numbers for Hub APIs, resolvers and pages only (0). No 429 or overload guidance for the router was found (0). No SLA found (0). Chat completions on the router is generally available; the Responses API is labelled beta (10). Routing between providers with :fastest or :cheapest softens a single provider's outage, which this checklist doesn't score.

Gemini Developer API 40

No machine payment protocol (0). Per-token prices published without a login, re-read on 1 November (20). Free tier on 3.8 Flash, 3.6 Flash, 3.5 Flash-Lite and 3.1 Flash-Lite, not on gemini-4-argon or 3.1 Pro preview, and the rate-limits page needs only an active project for the free tier and a linked billing account from Tier 1, so the free tier needs no card (20). A Google account and AI Studio are needed for a key (0).

Hugging Face Inference Providers 20

No x402, MPP or L402 (0). Per-token prices for every model and provider published without a login in the router's /v1/models and on model pages (20). No free tier since 7 October 2026, when free users lost their included monthly credits; PRO's $2.00 of credits needs a subscription (0). Sign-up, token creation and credit purchase are browser steps (0).