build1 publisherOne report agentgateway v1.6.0 priced a Claude Sonnet 5 request at $0.000156 from its built-in catalog, with no hand-kept modelCatalog in the config. The test covered one Anthropic model, so retiring rate tables is safe only for models the catalog provably knows.
Reality
- Evidence55
- Adoption
- Insufficient
- Hype gap+10
- Incentives
- Insufficient
- Confidence50
build1 publisherOne report Solo's agentgateway runs Coraza as a shared extension, and the write-up's own warning is that a WAFPolicy without HeadersAndBody mode and a JSON body processor will pass every payload while looking healthy.
Reality
- Evidence62
- Adoption12
- Hype gap+15
- Incentives45
- Confidence58
build1 publisherOne report Written as separate entries, a country check and a model allowlist become alternatives, so a caller from a restricted jurisdiction gets through by naming an approved model, and the policy still reports Accepted and Attached.
Reality
- Evidence62
- Adoption20
- Hype gap+12
- Incentives38
- Confidence64
build1 publisherOne report Admission control and RBAC decide who may fetch a Secret object. Neither is in the path once the kubelet has copied the value into a container, and an agent runtime is where that gap gets expensive.
Reality
- Evidence68
- Adoption15
- Hype gap+12
- Incentives45
- Confidence62
build1 publisherOne report A dev.to walkthrough on agentgateway makes a narrow point worth taking seriously: an agent that retries on failure will keep hitting an unrated MCP server until something gives.
Reality
- Evidence38
- Adoption
- Insufficient
- Hype gap+34
- Incentives
- Insufficient
- Confidence36