# Amazon Bedrock vs BlockRun.AI (slim)

> Amazon Bedrock scores 81.7 (A) to BlockRun.AI's 78.9 (A) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/amazon-bedrock-vs-blockrun-ai.md (~6,300 tokens) · this version ~2,880 tokens · JSON https://www.anchorterminal.com/compare/amazon-bedrock-vs-blockrun-ai.json · canonical https://www.anchorterminal.com/compare/amazon-bedrock-vs-blockrun-ai
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Amazon Bedrock scores 81.7 (A) on agent readiness against BlockRun.AI's 78.9 (A), and leads in 5 of 7 scored categories. BlockRun.AI leads on payments & pricing. Both do llm inference. BlockRun.AI accepts x402. Amazon Bedrock doesn't.

- Amazon Bedrock: A 81.7, rank #8 of 1486 · https://www.anchorterminal.com/tools/amazon-bedrock.min.md
- BlockRun.AI: A 78.9, rank #20 of 1486 · https://www.anchorterminal.com/tools/blockrun-ai.min.md
- Amazon Bedrock, good 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 65; Security & auth, 98 against 61; Transparency & trust, 85 against 73. Also A hosted endpoint, with nothing to install.
- BlockRun.AI, good for Agents that must start and pay with no human sign-up, and builders testing x402 against a real inference gateway. Ahead on Payments & pricing, 100 against 30. Also An agent can pay per call over x402, with no account; Runs on your own machine.

| Category | Amazon Bedrock | BlockRun.AI |
| --- | --- | --- |
| Reliability (16%) | 80 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 94 | 90 |
| Agent ergonomics (13%) | 92 | 88 |
| Security & auth (14%) | 98 | 61 |
| Payments & pricing (10%) | 30 | 100 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 81 | 85 |
| Transparency & trust (7%) | 85 | 73 |

| Fact (where they differ) | Amazon Bedrock | BlockRun.AI |
| --- | --- | --- |
| Kind | Model API | MCP server |
| Vendor | Amazon Web Services | BlockRun, Inc. |
| Hosted endpoint | `https://bedrock-runtime.us-east-1.amazonaws.com` | no (local only) |
| Transports | HTTP | stdio |
| x402 | no | yes |
| Licence | Proprietary 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.0 | MIT |
| Tools exposed | none | 19 |
| Read-only variant documented | no | yes |
| MCP registry | not listed | `io.github.BlockRunAI/blockrun-mcp` |
| Last release | 2026-10-30 | 2026-10-28 |
| Terms last updated | 2026-10-01 | 2026-09-02 |
| Privacy policy last updated | 2026-05-18 | 2026-09-02 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Popularity | 21.8M npm/wk | 5 stars, 679 PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Payments & pricing, BlockRun.AI +70: 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).); BlockRun.AI 100 (x402 v2 on its own gateway, USDC on Base and Solana, and since MCP 0.55.0 (28 October) on Circle's Arc through arc.blockrun.ai (40). Per-token prices per model published without a login, plus a flat $0.001 fee per wallet call on Base (20). Seven free models per the status page's menu, no card or sign-up, and a wallet costs nothing to create (20). An agent can create its own wallet and pay per request with no human sign-up (20). 40 + 20 + 20 + 20 = 100.)
- Security & auth, Amazon Bedrock +37: 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.); BlockRun.AI 61 (MCP and API reading. The credential is a wallet private key, auto-created at `~/.blockrun/.session` or passed in an environment variable and optionally mirrored to the OS keychain, and it controls the whole balance. `blockrun_wallet` can delegate a capped budget to a child agent, and an API-key route backed by account credit exists (20 of 30, as on 1 October). `blockrun_polymarket_read` gives read-only positions and previews apart from the trading tool, trades need `confirm:true` with a $25 default order cap, `--profile` drops whole groups of tools, and `BLOCKRUN_CONFIRM_SPEND=on` pauses every paid call for approval, though it's off by default (16 of 20). Search, Exa, market and RPC tools return third-party content, and no prompt-injection guidance was found in the README or docs read (5, as knock and suprsend). Every payment settles on-chain and the wallet tool reports balances and spending (10 of 15). security.txt is valid on 1 November, with an email contact, a policy link and an Expires date of 1 November 2027, and SECURITY.md takes private GitHub reports with a 72-hour acknowledgement and a 7-day plan for fund-affecting issues. No bounty or certification found (10). 20 + 16 + 5 + 10 + 10 = 61.)
- Reliability, Amazon Bedrock +15: 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).); BlockRun.AI 65 (Read with the local-software lines, as the listing's kind is `mcp` and the owner runs the server over stdio, though every paid call lands on BlockRun's gateway (the reading assymetrix-mcp and copilot-studio-mcp get). The 1 October check read it as a router. Installs from the official npm package `@blockrun/mcp` with Node 20.19 or later stated in `engines` (20). The CI workflow runs typecheck, build and tests on Node 20.19 and 22 on every push and pull request, with a required gate job. Run results weren't readable, as GitHub's pages answered 403 (20 of 25). Open issues couldn't be read. The changelog names numbered reports fixed in releases, such as #176 and #177 in 0.54.3 and 0.54.4 (10 of 25). Semver numbering with breaking changes marked BREAKING in CHANGELOG.md and shipped as minor bumps, as its own entries say (15). Version 0.55.0, pre-1.0 (0). 20 + 20 + 10 + 15 + 0 = 65. For the gateway behind it, blockrun.ai/status still shows live checks of the Base and Solana gateways and says "None recorded on this page yet" under incident history, the terms still say "We do not commit to any particular uptime", and free models are limited to 30 requests a minute and 300 an hour per IP with 429s carrying Retry-After.)
- Transparency & trust, Amazon Bedrock +12: 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).); BlockRun.AI 73 (The editorial half. The MCP server and SDKs are MIT and the gateway is closed. The listing is graded as the MCP server, so 30 as assymetrix-mcp got for an MIT server in front of a closed API (was 15 under the router reading). The terms and privacy policy, both last updated 21 October 2026, now name the same entity, BlockRun, Inc., as contracting party and data controller. The privacy policy now says prompts, completions and tool calls to blockrun.ai, arc.blockrun.ai, nano.blockrun.ai and api.blockrun.ai are stored with the paying wallet or account and kept "until we delete it; it has no fixed expiry", usage records and connection metadata for 13 months, while the Solana gateway keeps no request content. The 1 October policy said prompts weren't stored past the request and metadata was kept 30 days. The documents agree with each other, but content has no retention period and no subprocessors are named (18 of 30, was 20). No deprecation policy, and the terms say a provider may withdraw a model at any time. Removals are dated in the changelog, such as Gemma 4 31B delisted on 2 October, the same day (5 of 20). Upstream providers are named and Google Analytics is disclosed with its cookies and retention. Data locations aren't stated, and whether the MCP server sends telemetry wasn't read (10 of 20). 30 + 18 + 5 + 10 = 63.)