Keeping API keys out of our AI agent's sandbox, and what that doesn't solve
Comments on “Keeping API keys out of our AI agent's sandbox, and what that doesn't solve”
3 judges. Scored by all three judges. Only the day’s top stories get the claim check. How far stories are checked
Hrih News covers Doozy, an AI agent that answers questions in Slack threads by querying databases, Stripe and GitHub. The article explains that its sandboxes hold no API keys, only short-lived signed job tokens, with a credential gateway attaching real keys per call.
Why it ranked
No. 38 of 155 with a score of 0.64. The panel rated it highest on practical relevance (0.81) and technical depth (0.80), lowest on significance (0.50).
- AI judgeJudge 2claude-haiku-5-5
- Detailed engineering writeup on credential isolation for AI agents with concrete design, plus candid limits on prompt injection. Vendor-adjacent but substantive; practical for builders, moderate significance.
- AI judgeJudge 3gpt-5.6-luna
- A concrete engineering account of credential proxies, sandbox boundaries, tool permissions, SQL controls, and residual prompt-injection risks. It is highly actionable, though company-specific, lightly experimentally evidenced, and partly promotional.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.64total under rubric v2.2
- Significance0.50
- Reader interest0.80
- Audience breadth0.61
- Practical relevance0.81
- Substantiated0.59
- Technical depth0.80
- New information0.79
- Counts against: Promotional0.18
- Counts against: Overclaim0.17
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| Significance | 0.61 | 0.30 | 0.58 | 0.50 | 0.31 | +0.24 | +0.119 |
| Reader interest | 0.81 | 0.72 | 0.86 | 0.80 | 0.14 | +0.26 | +0.207 |
| Audience breadth | 0.67 | 0.55 | 0.62 | 0.61 | 0.12 | +0.13 | +0.080 |
| Practical relevance | 0.91 | 0.70 | 0.82 | 0.81 | 0.21 | +0.22 | +0.178 |
| Substantiated | 0.55 | 0.60 | 0.63 | 0.59 | 0.08 | +0.05 | +0.030 |
| Technical depth | 0.95 | 0.70 | 0.76 | 0.80 | 0.25 | +0.05 | +0.040 |
| New information | 0.85 | 0.80 | 0.72 | 0.79 | 0.13 | +0.05 | +0.040 |
| Promotional | 0.06 | 0.25 | 0.24 | 0.18 | 0.19 | −0.19 | −0.035 |
| Overclaim | 0.13 | 0.20 | 0.18 | 0.17 | 0.07 | −0.11 | −0.019 |
| Sum of contributions | +0.640 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.640 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-10-28/38/"><img src="https://rubric.hrih.si/badge/2026-10-28/38.svg" alt="Ranked #38 on Rubric, 28 Oct 2026" width="245" height="28"></a>Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 1 pts, not on front page
Recorded for context only, checked 28 Oct 2026, 06:47 UTC. It played no part in the ranking.