# Fix list: Bunny Storage From Anchor Terminal's listing at https://www.anchorterminal.com/tools/bunny-storage, the October 2026 research run, assessed 1 October 2026. Grade C, 58.7 out of 100. This is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public. For a coding agent working on Bunny Storage: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published. ## 1. Security & auth, 45 out of 100, up to 9.6 more on the total Why it scored 45: Each zone has a read-write and a read-only password, also used as the S3 secret, with a read-only S3 password since 30 July 2026. No expiry or prefix scope, and revoking means resetting. The account API key has full access (20). Read-only passwords, and deleting the zone root needs allowRootDelete=true, but nothing finer (12). Returns stored bytes, with no guidance on treating them as untrusted (8). No audit log of storage or API key use found (3). No security.txt, and the llms.txt names no disclosure policy, bounty or certification (2). The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10. - 0 to 15, audit logs or per-call visibility for the operator. - 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public. Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing. ## 2. Payments & pricing, 40 out of 100, up to 7.5 more on the total Why it scored 40: No x402, MPP or L402 (0). Per-GB storage and delivery prices public without a login (20). A 14-day trial without a card, per the 30 September check (20). A person signs up in a browser (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/). - 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which. - 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for "contact sales" or prices behind a login. - 20, a free tier or trial that doesn't need a card. - 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API). Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied. Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol. ## 3. Agent ergonomics, 57 out of 100, up to 7 more on the total Why it scored 57: No MCP server. An HTTP listing returns the whole folder as one JSON array; S3 ListObjectsV2 can page and filter by prefix (12). The docs give no pagination for HTTP listings; S3 has continuation tokens and prefixes, in preview (10). Thin error documentation, three codes on the HTTP API (8). A PUT by path is safe to repeat, the Checksum header rejects corrupt uploads, and S3 takes conditional requests (14). One PUT with one header, and official SDKs for TypeScript and .NET (13). The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 15, sensible defaults, few required parameters, and official SDKs in at least two languages. Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs. ## 4. Schema & documentation, 64 out of 100, up to 5.9 more on the total Why it scored 64: No OpenAPI for the storage data plane. The llms.txt lists specs for the core, compute, video, database, Shield and logging APIs, and the core spec covers zone management (12). llms.txt with 300-odd Markdown pages (10). The HTTP API page says what each call does in a line or two (12). Path-based calls with a few headers, little to type (9). curl examples for each call, but only 201, 400 and 401 documented, and one 401 covers a wrong key, a wrong region and an encoded body (9). A dated changelog, with S3 changes on 9 July, 30 July and 14 August; the storage API itself carries no version (12). The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 15, versioning and a public changelog. Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference. ## 5. Reliability, 75 out of 100, up to 5 more on the total Why it scored 75: Public status page at status.bunny.net with an RSS history (20). One storage incident in the window, a Storage API degradation in London with elevated error rates for about two hours on 18 August 2026, plus planned network maintenance in Sydney on 24 August that hit non-replicated zones (10). 500 requests a second and 1 Gbps per connection on S3, 250 concurrent HTTP connections per zone per server, 5 listings and 30 deletes at a time (15). A SlowDown 503 on the S3 endpoint carries Retry-After in seconds with advice to back off exponentially (15). SLA of 99.99 per cent with credits of 12 to 240 hours (10). The HTTP API is GA, but S3, the only route to expiring links, is still public preview (5). The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 10, the surface agents use is generally available, not beta or preview. Local packages, SDKs, frameworks and stdio MCP servers. - 20, installs from an official package with supported runtimes stated. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 15, version 1.0 or later, or declared stable. Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors. ## 6. Maintenance & community, 63 out of 100, up to 3.2 more on the total Why it scored 63: Last storage API change on 14 August 2026 (S3 compatibility improvements), with a dashboard change on 29 September (20). Storage entries on 9 July, 30 July, 14 August and 29 September (20). A dated public changelog; we didn't test support (10). Official storage SDKs for TypeScript and .NET, whose release dates we didn't check (8). Package health unchecked (5). The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older. - 20, at least three releases or dated changelog entries in the last 90 days. - 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## 7. Transparency & trust, 64 out of 100, up to 3.2 more on the total Made of editorial 52, provenance 75. Why it scored 64: Closed service, terms and privacy policy naming BunnyWay d.o.o. in Slovenia (15). Privacy policy updated 5 August 2026 and deletion after termination in the terms, per the 30 September check. No DPA read this run (18). No deprecation policy found; the changelog marks previews but sets no notice periods (5). Storage regions chosen per zone and an EEA routing filter for pull zones; we didn't read a sub-processor list (14). The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted). The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two. Provenance checks not met in full (half of this category, computed from checked facts): - Endpoint on the vendor's domain: storage.bunnycdn.com is not on bunny.net (0 of 15) - security.txt: not found (0 of 10) ## What we couldn't check What we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it. - unchecked: release dates of the official storage SDKs (@bunny.net/storage-sdk and the .NET library) - unchecked: whether bunny.net holds ISO 27001 or SOC 2, or runs a bug bounty; neither the llms.txt nor the docs we read name one - The S3 docs still say public preview while the 9 July changelog says S3 is available to all; we graded it as preview ## Weaknesses - Zone passwords are the only storage credential, read-write or read-only, with no expiry, prefix scope or usage log - S3 compatibility, and with it presigned links, is still public preview and can't be switched on for an existing zone - The HTTP API documents only 201, 400 and 401, and gives no pagination for folder listings - No OpenAPI for the storage data plane, no official MCP server and no security.txt - A two-hour Storage API degradation in London on 18 August 2026 ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Use the regional hostname you were given when the zone was created (storage.bunnycdn.com is Frankfurt). Other regions return a 401 - Send the body as raw bytes with --data-binary. Base64 or form encoding gets a 401 - Add the Checksum header (uppercase SHA-256 hex) on uploads so a corrupt transfer fails instead of landing - End a listing path with a slash, expect one JSON array for the whole folder, and keep to 5 listings in flight - On a SlowDown 503 from the S3 endpoint wait the Retry-After seconds, then back off exponentially ## What the review panel asked for - Publish all-in price - expiring, prefix-scoped keys - a storage access log ## When it's done Send what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `"kind": "dispute"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.