A1 ratingsAWSAmazon Bedrock

Amazon Bedrock

AWS · platform · Any industry
B
BGrade
67Score
±1495% range
≈#120Rank of 1136
0%From fleets
FR-CAT-01106Catalog no.

The six pillars

Each bar is the score; the bracket is its 95% range.

Can you see what it costs?

Cloud billing export (AWS Cost Explorer API (GetCostAndUsage) / Cost and Usage Reports) · prices published
63±38
Desk research 76 · counts for 25% · A cost API you can call scores highest; an admin console or cloud billing export next; a card statement or emailed invoice is all some products leave you. Published prices add to it.

Can you see how much it's used?

No usage API found
64±27
Desk research 70 · counts for 15% · A usage API (tokens, seats, credits, conversations) a buyer can read.

Can you tie cost to one agent?

By project
64±27
Desk research 70 · counts for 15% · Exact (one key or project per agent) beats by-project, by-workspace or by-user.

Can an agent on it report out?

SDK · Agent can call AWS SDK (boto3) for Cost Explorer and CloudWatch with an IAM role.
64±27
Desk research 70 · counts for 15% · A remote MCP connector scores highest, then a local MCP server, an SDK, an API or a workflow step; copy-and-paste lowest. Any open standard counts, not just FleetRegistry.

Can you control spend and access?

Spend cap: Alerts only · Per-agent keys: Scoped · Audit log: By API · Revoke: By API · SSO: SSO + SCIM
69±38
Desk research 88 · counts for 20% · Hard spend caps (30%), scoped per-agent keys (25%), an audit log you can read by API (20%), revoking by API (15%), SSO with SCIM (10%).

Does it work on small plans?

Small plans get the data
86±27
Desk research 100 · counts for 10% · Whether the plan a person or small business buys gets the cost and usage data at all.

Where the evidence comes from

Independent fleets0%Desk research62%Neutral starting point38%

Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.

Controls on record

Spend capAlerts only
Per-agent keysScoped
Audit logBy API
RevokeBy API
SSOSSO + SCIM
PricesPublished

Price changes: AWS Customer Agreement s.3.1: at least 30 days' prior notice for fee increases on services in use

Bedrock has no native hard spend cap. AWS Budgets actions can apply a Deny IAM policy or SCP at a threshold but don't guarantee charges stop. Bedrock API keys are tied to IAM principals and can be scoped by IAM (including denying CallWithBearerToken), and long-term keys can be deactivated, reset or deleted through the console or API. CloudTrail and IAM Identity Center ratings carry over from the prior check.

History

11-12 B 6711-13 B 6711-14 B 6711-15 B 6711-16 B 6711-17 B 6711-18 B 6711-19 B 67
First rated 2026-10-02 at 66 (B). Now 67. Published grades are sealed daily into the transparency log (N4.4). Grade held since 2026-10-02.

Every fact, with its rung and source

Each fact stands on its own source and its own rung of the evidence ladder (Rule N2.1). Verified Observed Declared Inferred. The weakest fact in a pillar sets its weight.

FactValueRungCheckedSources
How a buyer sees cost
Cost
Cloud billing export Declared
medium confidence
2026-11-15
3 earlier
[1][2] Correct
Prices published
Cost
Yes Inferred 2026-11-15
3 earlier
[1][2] Correct
Usage API
Usage
None found Declared
medium confidence
2026-11-15
2 earlier
[1][2] Correct
Cost per agent
Per agent
By project Declared
medium confidence
2026-11-15
2 earlier
[1][2] Correct
How an agent reports out
Reports out
SDK Declared
medium confidence
2026-11-15
2 earlier
[1][2] Correct
Per-agent keys
Controls
Scoped Inferred 2026-11-15
3 earlier
[1][2] Correct
Audit log
Controls
By API Inferred 2026-11-15
4 earlier
[1][2] Correct
Revoke access
Controls
By API Inferred 2026-11-15
3 earlier
[1][2] Correct
Spend cap
Controls
Alerts only Inferred 2026-11-15
4 earlier
[1][2] Correct
SSO
Controls
SSO + SCIM Inferred 2026-11-15
3 earlier
[1][2] Correct
Small plans get the data
Small plans
Yes Declared
medium confidence
2026-11-15
2 earlier
[1][2] Correct

Prices · Per-token on-demand by model; Flex and Batch 50% below Standard, Priority +75%; Provisioned Throughput hourly per model unit (no/1-mo/6-mo commit)

Notes · AWS-billed. CUR 2.0 gives line items per model, token type (input, output, cache read, cache write), service tier and cross-region routing, and cost can be attributed by IAM principal, session, Bedrock Project or application-inference-profile tags (after activating them as cost allocation tags; up to 24h to populate). Totals are aggregated hourly or daily, not per request; per-request cost needs model invocation logs.

Scored with the rubric for Platforms and APIs (Rule N7.1). Each pillar blends a neutral 50, desk facts weighted by rung, and independent fleets. A1 is 85+ with fleet proof, A 70, B 55, C 40, D 25, E below. Part N of the Rules

Corrections

1 awaiting review. Accepted corrections are published in the corrections register with an FR-C number.

Run agents on Amazon Bedrock?

Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.