Amazon Bedrock vs DeepInfra

Amazon Bedrock 98

Model reading. IAM with SigV4, roles and STS session credentials, policies down to a model or inference-profile ARN, short-term API keys that expire within 12 hours, long-term keys with expiry and reset, and condition keys that can deny bearer tokens altogether (30). The security page says customer data isn't shared with model providers or used to improve the base models (20). The abuse detection page says Bedrock stores no inputs or outputs by default, and a per-Region none mode blocks models that require retention, but Claude Fable 5 and 5.1 keep all traffic up to 30 days and GPT-6 and GPT-5.x keep flagged traffic up to 30 days (13 of 15, a judgement call; Anthropic's own API got 12 for the same Fable exception without an account-level block). CloudTrail logs API calls, and model invocation logging can send prompts and responses to S3 or CloudWatch Logs (15). Bedrock is in ISO, SOC and CSA STAR Level 2 scope, HIPAA eligible and FedRAMP High in GovCloud (US-West) per its security page, with a vulnerability disclosure programme on HackerOne, and the aws.amazon.com security.txt, expired on 6 October, was renewed with Expires 2027-10-16 when read on 6 November (20). Up from 96 on 6 October for that reason.

DeepInfra 64

Model reading. Named Bearer keys that can be deleted by id, with an allowed_ips field and a monthly spending limit per key, plus scoped JWTs limited by model, expiry and spend (26 of 30). Less 10 because GET /v1/scoped-jwt?jwtoken= is still the documented way to inspect a JWT and puts a live token in the query string. The two deprecated routes that carried the API token in the URL path are no longer in the OpenAPI document (16 of 30). The terms say Customer Data is not used to train, fine-tune or improve any model. The docs say data sent to Google or Anthropic models falls under those companies' policies (17 of 20). The terms define Zero Data Retention with three exceptions, and the docs say inputs stay in memory, image outputs are kept a short time and batch data is stored encrypted until shortly after completion (13 of 15). Usage per key, request costs and deployment logs are in the API. No account audit log was found (8 of 15). The trust centre at trust.deepinfra.com now loads and lists SOC 2, ISO 27001 and HIPAA as compliant, with reports and policies on request, and the privacy policy says the same. No security.txt, disclosure policy or bug bounty was found (10 of 20, as other listings with certification claims and no disclosure route).

Amazon Bedrock 94

Model reading. No OpenAPI, but the bedrock-runtime and bedrock Smithy models are public in aws/api-models-aws with types, required members and enums, counted as for S3 (25). llms.txt for the user guide with about 2,000 lines, each page with a Markdown twin (10). Model cards state context, output limits, endpoints and supported functions per model, and the guide now recommends bedrock-runtime for new work, but support for each API, endpoint and feature changes model by model (16 of 20). Structured outputs compile JSON Schema to a grammar, with minimum, maximum and string lengths supported, though some inference profiles don't support it, such as Haiku 4.5 through the India profile (13 of 15). Every operation lists typed errors with HTTP codes and links to a troubleshooting page with causes and fixes, and examples run through the guide (15). API version 2023-09-30 and a dated document history with an RSS feed, newest entry 30 October 2026, with structured outputs for Claude on both endpoints added on 18 October (15).

DeepInfra 69

Model reading. Public OpenAPI 3.1.0 document at api.deepinfra.com/openapi.json with 131 paths, 157 operations and 257 schemas on 2 November 2026. llms.txt now links that document, though the docs host's own copy still returns Mintlify's sample plant store document, and the spec lists chat at /v1/chat/completions while every docs example uses /v1/openai/chat/completions (22 of 25). llms.txt with 224 links and a Markdown copy of every docs page (10). Guide pages for tool calling, structured output, caching, batch and service tiers say when to use each. Many reference operations have a name and no description (14 of 20). Typed parameters with 49 enums, 31 chat properties and two required (11 of 15). Curl, Python and JavaScript examples on each page. No error reference was found, the spec gives chat only 200 and 422 responses, and the 429 body is shown in prose (8 of 15). No changelog was found. The spec version reads 1.0.0, and the docs repository on GitHub has a public commit history (4 of 15).

Amazon Bedrock 81

Model reading. The last model or API change is 30 October 2026 (OpenAI model API support and cross-Region inference in GovCloud), after structured outputs for Claude on both endpoints on 18 October (30). Models launched since 7 September 2026 get a 6-month or 45-day Legacy period, but the legacy page, which promises at least 6 months in Legacy, lists Claude 3 Haiku, 3 Sonnet, 3.5 Sonnet, 3.5 Sonnet v2 and 3.7 Sonnet as Legacy from 10 or 13 October with end of life on 13 November in several Regions, about 34 days (6 of 12, down from 10). Six models reached end of life in the 90 days to 6 November on five dates, Command R and R+ on 19 August, Claude 3 Haiku on 10 September, Nova Sonic on 14 September, Nova Canvas and Nova Reel on 30 September and Claude Sonnet 4 on 14 October (3 of 8, down from 4). Dated document history several times a month, What's New and re:Post, with direct support on a paid plan (12 of 15). SDK issue replies not sampled (5 of 10). Current official SDKs, boto3 1.43.125 on 5 November and @aws-sdk/client-bedrock-runtime 3.1163.0 (15). Supported runtimes stated, Python 3.10 or later and Node 20 or later (10). Down from 86 on 6 October.

DeepInfra 61

Model reading. The docs repository changed on 26 October 2026, and on 22 October documented Nemotron 3.5 image embeddings and reranker scores (30). Deprecated models get at least one week's notice by email, then requests are forwarded to a replacement (5 of 12). Churn. In the 90 days to 2 November four redirect dates passed (8, 9, 12 and 25 October, five models), Kimi-K2.7-Code was deprecated before 28 September, and three more are scheduled for 2 and 3 November. Three or more removal dates in 90 days give 0, as groq and fireworks-inference were read (0 of 8, was 4 when the five were only scheduled). No changelog. Support is by Discord and a feedback address, and the docs repository is public (7 of 15). Replies on the SDK repositories were not examined (3 of 10). Python deepinfra 0.3.0 from 12 August 2026 with a changelog. The Node repository tagged 2.1.0 on 1 September 2026, and npm couldn't be read on 2 November, so its 8 October reading of 2.0.2 from 8 May 2024 stands (9 of 15). CI workflows in both SDK repositories (7 of 10). 30 + 5 + 0 + 7 + 3 + 9 + 7 = 61.

Amazon Bedrock 85

Closed service under the AWS Customer Agreement and Service Terms, with the SDKs and Smithy models under Apache-2.0 (18, as for S3). The data retention, abuse detection and security pages agree that Bedrock stores nothing by default, name the models that retain traffic and for how long, and say retained data isn't shared with providers. The retention page's default mode says AWS 'may retain the data for safety and abuse-prevention purposes' without a period, and a legacy provider_data_share mode is kept though sharing isn't supported (25 of 30). A written lifecycle policy with Legacy and EOL dates per model, but the legacy table's 34-day Legacy periods for five Claude models in some Regions contradict its own 6-month floor (15 of 20, down from 18). AWS's sub-processor list, per the 4 October S3 check, and per-Region, geographic and global inference options, with global routing able to process data in any commercial Region (18 of 20).

DeepInfra 68

Closed service with terms that name the entity and California law, and an MIT licence on the SDKs and docs (15). The terms (last modified 15 October 2026), the privacy policy and the data privacy page agree on no storage and no training, the terms say their retention clause controls, and personal information is removed 30 days after account deletion. The terms now point to a DPA on the trust centre, which lists it among documents available on request, and the entity is written Deep Infra Inc. in the terms and DeepInfra, Inc. in the privacy policy (21 of 30). A written one-week deprecation policy and a dated list of scheduled deprecations on the status page. No record of past removals was found (14 of 20). The sub-processor list names Stripe, Amazon Web Services and Google Cloud Platform, as does the trust centre. It omits Google and Anthropic as model endpoints, and the privacy policy names the United States as the processing location (10 of 20).

Amazon Bedrock 92

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Converse takes tools with toolChoice auto, any or a named tool and strict: true, but forced choice depends on the model behind it (17 of 20). Structured outputs on supported models only (13 of 15). Explicit and implicit prompt caching, cache reads at $0.20 per million on Opus 5.5, 0.05x input, with 5-minute and 1-hour TTLs (15). 1M-token context on Opus 5.5, Sonnet 5.5 and Nova 2 Lite, a judgement call since Bedrock has no default model (15). Batch at half price on supported models, but the pricing page shows none for Opus 5.5 or Sonnet 5.5, while Flex is half price on Nova (7 of 10). AWS SDKs in every major language plus token generators for Python, JavaScript and Java (10). Typed errors with recovery advice per code (15).

DeepInfra 77

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with tool_choice of none, auto, required or a named function, and streaming. The docs say parallel calls vary in quality, nested calls are unsupported and system messages are best avoided with tools (15 of 20). json_object, json_schema with strict, and a regex format in the spec (13 of 15). Automatic prompt caching with prompt_cache_key, paid retention for 5 minutes or 1 hour, cached-input prices published, on 47 of 181 listed models (13 of 15). Context of 1,048,576 tokens on DeepSeek V4, Kimi K3 and GLM 5.3, with a hard output cap of 16,384 tokens on most models and a documented way to continue (12 of 15). Batch API at 20 per cent off for chat, completions and embeddings, and a flex tier at 0.8x (10). The OpenAI and Anthropic clients work with a changed base URL. The Python package deepinfra 0.3.0 dates from 12 August 2026, and npm listed 2.0.2 from May 2024 on 8 October (7 of 10). 429 carries an engine_overloaded code. Native routes return a bare error string, and no list of codes was found (7 of 15).

Amazon Bedrock 30

No x402, MPP or L402 (0). Per-token prices per model, tier and Region on the public pricing page, filled from AWS's public price feed (20). New accounts get up to $200 in Free Tier credits and the Free Tier page lists Bedrock among eligible services, and the Free Tier FAQ says most new customers don't need a payment method, but AWS may still ask for one, so half, as for S3 (10). A person signs up for AWS in a browser and sets up IAM before any key exists (0).

DeepInfra 20

No machine payment protocol (0). Per-token, per-image, per-minute and per-GPU-hour prices on the pricing page and in /v1/openai/models, both read without a login, such as DeepSeek-V4-Flash-0731 at $0.06 in and $0.18 out per 1M tokens (20). No free tier. The pricing page says an account must add a card or prepay (0). A person signs up in a browser, and the key API needs an existing key (0).