Head to head · LLM inference · October 2026 research run

Amazon Bedrock vs xAI API (Grok)

Amazon Bedrock scores 81.7 (A) on agent readiness against xAI API (Grok)'s 71.7 (BB), and leads in every scored category. Both do llm inference.

Best model APIs and inference for AI agents · All 830 models comparisons

Which one, for what

Amazon Bedrock A

Best for Teams already on AWS who want Claude, GPT-6, Nova, Llama and other models under one IAM, billing and VPC boundary, with regional data controls and an SLA.

Ahead on

  • Reliability, 80 against 55
  • Schema & documentation, 94 against 88
  • Payments & pricing, 30 against 20
  • Transparency & trust, 85 against 63

Watch for

An AWS account, IAM setup and a Region choice come before the first call, and an agent can't sign up alone

xAI API (Grok) BB

Best for Agents that want a capable model at a low per-token price with built-in web and X search, remote MCP and voice, and teams that need self-serve ZDR or US-only processing.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

API models outage of about 3 hours 40 minutes on 3 September 2026, and high error rates on grok-4.6 and grok-4.5 on 17 August

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Amazon Bedrock +25

Amazon Bedrock 80

AWS Health Dashboard with per-service, per-Region feeds and a public history file (20). The history lists Amazon Bedrock as disrupted in ME-CENTRAL-1 (UAE) and ME-SOUTH-1 (Bahrain) since March 2026, where AWS said on 15 September 2026 (still inside the 90-day window on 6 November) that it can't restore resources held only there. No other Bedrock event appears in the history in the 90 days to 6 November; an EU-SOUTH-2 packet-loss event on 4 October named Bedrock AgentCore, not Bedrock. This counts as one major event (10). StatusGator's third-party mirror shows 'Increased Error Rates' warnings on 24, 26 and 27 August and 10 September that we couldn't find in AWS's own history, so we didn't score them. Per-model token quotas with default values in the AWS General Reference, such as 30,000,000 tokens a minute for Opus 5.5 global inference (15). The error guide gives exponential backoff with jitter for 429, 503 and 529 and says to honour Retry-After, and the SDKs retry ModelNotReadyException up to five times (15). SLA of 99.9 per cent a month per Region for the model APIs, last updated 4 October 2023 (10). Converse and the current Claude, GPT-6 and Nova 2 Lite models are GA (10).

xAI API (Grok) 55

Status page at status.x.ai with components for the global and US API endpoints, voice, the consumer apps and, since the Cursor merger, Cursor's services, with an RSS feed (20). The feed, read on 6 November, now holds 267 incidents back to 11 August, so the whole 90-day window is readable. On the API components there were high error rates on grok-4.6 and grok-4.5 from 21:57 to 23:28 UTC on 17 August (about 90 minutes) and a models outage on the global and US endpoints from 13:30 to 17:09 UTC on 3 September (about 3 hours 40 minutes), so several majors. A 26-minute datacenter outage across the API on 22 September, voice disruptions of 12 and 28 minutes on 10 September and 6 October, a 63-minute voice and Imagine degradation on 30 October and a 37-second model degradation on 24 October add to the record (0). Rate limits published per model and tier, grok-4.7 at Tier 0 is 150 requests a second and 50M TPM, with the per-second cap derived as RPM divided by 48 (15). The rate-limits page shows exponential backoff on 429, but no Retry-After header or overload guidance was found (10 of 15). No SLA found in the docs or llms.txt (0). The Responses API has been GA since September 2025 and grok-4.7 carries no preview label (10).

Transparency & trust Amazon Bedrock +22

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

xAI API (Grok) 63

Closed service under xAI's enterprise terms, with the Python SDK under Apache-2.0 (15). The docs agree with each other on no training, 30-day abuse retention, 30-day storage of stateful responses and the ZDR route, but the privacy policy, enterprise terms and DPA at x.ai/legal answered a Cloudflare block page on 6 October and again on 6 November, so they couldn't be compared (15 of 30). Dated migration guides and redirect tables for each retirement, but no written deprecation policy, and Chat Completions, Anthropic compatibility and grok-voice-2.0 are labelled deprecated with no date (12 of 20). The US regional endpoint states what stays in the US, the global endpoint guarantees no region, and no subprocessor list was readable (10 of 20).

Payments & pricing Amazon Bedrock +10

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

xAI API (Grok) 20

No x402, MPP or L402 (0). Per-token and per-call prices published without a login on docs.x.ai/developers/pricing (20). No free tier found for the text API, and the quickstart says to load the account with credits (0). Sign-up is in the browser at console.x.ai. The Management API can create keys and top up prepaid credit, but only with a management key made by a person in the console, so no line credit (0).

Schema & documentation Amazon Bedrock +6

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

xAI API (Grok) 88

OpenAPI 3.1 document at docs.x.ai/openapi.json, 39 paths and 205 schemas on 6 November, covering Responses, Chat Completions, files, images, videos and models. The batch endpoints documented in the REST reference still aren't in it (20 of 25, applied as for gemini-api's missing Interactions API). llms.txt and a Markdown twin of every page, plus a docs MCP server (10). The models page says which model to use for code, chat, images, video and voice, and reference pages list each parameter. Reference not read in full (18 of 20). Structured outputs are guaranteed to match the schema for supported keywords, and tool arguments always conform with strict implicitly true (15). Examples in Python, JavaScript and curl on every guide. The debugging page lists status codes with fixes, but the cause cells for 400, 403, 404 and 415 are still empty (13 of 15). Release notes are grouped by month without day dates, and model slugs come as aliases and dated versions (12 of 15).

Score by category

CategoryWeight this runAmazon BedrockxAI API (Grok)Edge
Reliability16%208055Amazon Bedrock +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29488Amazon Bedrock +6
Agent ergonomics13%16.29290Amazon Bedrock +2
Security & auth14%17.59897Amazon Bedrock +1
Payments & pricing10%12.53020Amazon Bedrock +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88177Amazon Bedrock +4
Transparency & trust7%8.88563Amazon Bedrock +22
Negative events≤1500
TotalA 81.7/100BB 71.7/100

Facts side by side

FactAmazon BedrockxAI API (Grok)
KindModel APIModel API
VendorAmazon Web ServicesSpaceXSI (xAI)
Hosted endpointhttps://bedrock-runtime.us-east-1.amazonaws.comhttps://api.x.ai/v1
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under the AWS Customer Agreement and Service Terms. Third-party models carry their providers' licence terms. The AWS SDKs and the Smithy service models are Apache-2.0Proprietary service under xAI's enterprise terms of service. The Python SDK is Apache-2.0
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-302026-11-02
Terms last updated2026-10-012026-10-27
Privacy policy last updated2026-05-182026-10-27
Customer content may train modelsyes, with an opt-outyes
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textyes
Popularity21.8M npm/wk597 stars, 912k PyPI/wk

What the same task costs

TaskAmazon BedrockxAI API (Grok)
Research a product and write a sourced reportanthropic.claude-opus-5-5 on Amazon Bedrock, grok-4.7 on xAI API (Grok)$43.88$21.76
Build a small four-page websiteanthropic.claude-opus-5-5 on Amazon Bedrock, grok-4.7 on xAI API (Grok)$10.03$4.85
Find and fix a bug in a large codebaseanthropic.claude-opus-5-5 on Amazon Bedrock, grok-4.7 on xAI API (Grok)$2.16$1.07

Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.

Verdicts

Amazon Bedrock

Bedrock reaches Claude, GPT-6, Nova, Llama and other families through one IAM-controlled API, with a 99.9 per cent SLA and a per-Region zero-retention switch. Setup needs an AWS account, IAM permissions and a Region, capabilities vary by model, and some Regions gave five older Claude models about 34 days of notice.

xAI API (Grok)

Grok 4.7 at $2/$6 per million tokens, now 20% off in batch, with a public OpenAPI spec, llms.txt, API keys limited by endpoint and model, and self-serve zero data retention. The API endpoints had a 3 hour 40 minute models outage on 3 September 2026, no SLA was found, and there's no free tier or first-party SDK beyond Python.

Before you call either

Amazon Bedrock

  1. Use the geographic or global inference ID from the model card, such as global.anthropic.claude-opus-5-5. Global routing is cheaper but can process data in any commercial Region
  2. Set data_retention_mode to none in each Region before sending sensitive data. Models that need retention then return ValidationException
  3. Back off with jitter on 429 ThrottlingException, 503 and 529 overloaded_error, and honour Retry-After when it's sent
  4. Generate short-term API keys from an IAM role for production. Long-term keys create an IAM user and AWS marks them exploration only
  5. Call ListFoundationModels in your Region and read modelLifecycle before pinning a model ID. Claude 3.x IDs in several Regions stop working on 13 November 2026 and requests don't redirect

xAI API (Grok)

  1. Build on the Responses API at https://api.x.ai/v1. Chat Completions is labelled deprecated and the Anthropic-compatible endpoint fully deprecated
  2. Pin a dated model slug. A retired slug keeps answering from a replacement model, billed at the replacement's price
  3. Back off exponentially on 429. The per-second cap is the per-minute budget divided by 48, with a minimum of 2
  4. Set allowed_tools on remote MCP servers. There's no approval step, and every exposed tool enters the context
  5. Use https://us.api.x.ai/v1 when processing must stay in the US. It costs 1.1x and serves only grok-4.7 and grok-4.6

Questions

Which is better for AI agents, Amazon Bedrock or xAI API (Grok)?

Amazon Bedrock scores 81.7 (A) on agent readiness against xAI API (Grok)'s 71.7 (BB), and leads in every scored category.

Do Amazon Bedrock and xAI API (Grok) need an API key?

Amazon Bedrock takes an API key or an OAuth sign-in. xAI API (Grok) needs an API key.

Can an agent call Amazon Bedrock and xAI API (Grok) without installing anything?

Yes. Amazon Bedrock has a hosted endpoint at https://bedrock-runtime.us-east-1.amazonaws.com and xAI API (Grok) at https://api.x.ai/v1.

Other comparisons with Amazon Bedrock or xAI API (Grok)

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.