# Wasabi Hot Cloud Storage > Wasabi Hot Cloud Storage is S3-compatible object storage from Wasabi Technologies, sold at one price per terabyte with no egress or request fees. Agents reach it through the S3, IAM and STS APIs with standard AWS SDKs. - Canonical: https://www.anchorterminal.com/tools/wasabi-hot-cloud-storage - Markdown: https://www.anchorterminal.com/tools/wasabi-hot-cloud-storage.md (~7,650 tokens) - Slim: https://www.anchorterminal.com/tools/wasabi-hot-cloud-storage.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/wasabi-hot-cloud-storage.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-10 ## Overview **Grade C · 61.2/100 · rank #478 of 950 · #10 in File storage & sharing · not agent-ready · confidence medium** ## Assessment IAM policies, STS sessions of up to 12 hours, Object Lock and audit logging give an agent tight, revocable access at $7.99 a TB-month with no egress or request fees. No request limits are published with numbers for the S3 API, there is no OpenAPI file, and billing assumes 1 TB and 90 days of storage as minimums. ## Facts | Field | Value | | --- | --- | | Vendor | Wasabi Technologies LLC (https://wasabi.com) | | Kind | HTTP API | | Category | File storage & sharing (https://www.anchorterminal.com/categories/file-storage) | | Transport | HTTP, Streamable HTTP | | Endpoint | `https://s3.wasabisys.com` | | Auth | API key · Self-serve access key and secret key, made in the console after a browser sign-up, signed as for AWS S3. A root key has full access including billing. Sub-user keys need IAM policies, and bucket policies, groups and roles are supported. STS gives AssumeRole sessions of up to 12 hours and GetSessionToken. Each user holds up to two keys for rotation. The beta MCP server takes OAuth with dynamic client registration and keeps the Wasabi keys on the server. WACM Connect and the Account Control API use separate keys. | | Pricing | Pay per use (Pay per use) · Pay as You Go is $7.99 a TB-month in every region since 1 July 2026 (up from $6.99), with no egress or API request charges. Billing assumes at least 1 TB a month and 90 days per object. Egress is free while monthly downloads stay at or below stored volume. Reserved Capacity Storage is sold for 1, 3 or 5 years at discounts not published. The free trial needs no card and no contract (https://wasabi.com/pricing; https://wasabi.com/pricing/faq). | | x402 | No · No x402, MPP or L402 in the API reference, the docs index or the pricing pages (checked 2026-10-09). | | Licence | Proprietary service under the Wasabi Customer Agreement | | Docs | https://docs.wasabi.com/apidocs/wasabi-api | | llms.txt | https://docs.wasabi.com/llms.txt | | Last release | 2026-08-28 | | APIs | S3 API (compatible with AWS S3 2006-03-01), IAM (2010-05-08 subset) and STS (AssumeRole, GetCallerIdentity, GetSessionToken). Wasabi Account Control API and WACM Connect API for partners and control accounts, and a Stats API for utilisation | | Endpoints | `s3.wasabisys.com` for US East 1 and `s3..wasabisys.com` for the other 15 regions. Path-style requests recommended. HTTP and HTTPS both accepted | | Credentials | Access key and secret key, up to two per user, for the root user or a sub-user. Sub-users need IAM policies such as AmazonS3FullAccess or AmazonS3ReadOnlyAccess. Up to 1,000 policies an account. STS sessions up to 12 hours | | MCP server | Hosted beta at `https://mcp.wasabisys.dev/s3`, `/iam` and `/wacm`, Streamable HTTP, OAuth with dynamic client registration and short-lived tokens. Wasabi keys are saved once in the server's dashboard. Tool names follow `wasabi__`. Tool list not published | | Minimums | 1 TB of active storage a month, 90 days of storage per object on Pay as You Go (30 days on request), 4 KB per object | | Free trial | No card. 100 GB for 30 days with a company email, 10 GB for 14 days with a free mail address, per the trial page. MFA is required on new trial accounts. Trial data is deleted if the account is not converted | | Presigned URLs | GET and PUT, valid from 12 hours to 7 days when made in the console, per the docs | | Rate limits | None published with numbers for the S3 API. The Account Control API allows 1,000 GET, 100 PUT, 100 POST and 10 DELETE operations a minute and answers 429 beyond that | | Errors | AWS S3 error responses where possible, plus Wasabi codes such as `RequestRateLimitExceeded`, `StorageQuotaExceeded`, `AuthenticationLockout` and `EntityTemporarilyUnmodifiable` | | Deletion controls | Object Lock with legal hold, compliance mode, bucket versioning, MFA Delete, Multi-User Authorisation through security contacts, and Covert Copy | | Logging | Bucket access logs, administrative audit logs (CSV for up to 90 days, or saved to an Object Lock bucket), compliance logging and S3 event notifications | | SLA | The version of 21 February 2024 gives a 10 per cent credit below 99.9 per cent monthly uptime and 25 per cent below 99.0. The current page is drawn by script and was not read | | Certifications | ISO 27001:2022 held by Wasabi Technologies LLC (A-LIGN, valid to 9 June 2028). Data centres are described as SOC 2 compliant and certified for ISO 27001 and PCI-DSS. The DPA of 14 July 2025 cites an annual Type 2 HIPAA/HITECH audit | | Sub-processors | 13 companies with location and purpose in the list of 19 December 2025, Stripe, Salesforce, Sentry, LogRocket and IBM (for AiR) among them, plus six Wasabi affiliates. The DPA of 14 July 2025 allows 30 days to object to a new one | | Capabilities | storage.object, storage.s3, storage.presigned | | Tags | hosted, s3-compatible, iam, sts, mcp, beta-mcp, llms-txt, usage-priced, free-trial, object-lock, status-page, iso-27001 | | JSON | https://www.anchorterminal.com/api/v1/tools/wasabi-hot-cloud-storage.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 65 | 13.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 59 | 9.6 | | Agent ergonomics | 13% | 16.2 | 68 | 11.1 | | Security & auth | 14% | 17.5 | 83 | 14.5 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 46 | 4.0 | | Transparency & trust (editorial 59, provenance 79) | 7% | 8.8 | 69 | 6.0 | | Negative events | up to −15 | up to −15 | 9 October 2026. The sign-up guide, updated on 15 September 2026, advertises a trial of up to 1 TB for 30 days, while the trial page gives 100 GB for 30 days with a company email and 10 GB for 14 days with a free mail address. Two points for the conflicting claim (https://docs.wasabi.com/docs/signing-up-for-wasabi; https://wasabi.com/try-free). | -2 | | **Total** | | | | **61.2 → C** | ### Why each score - Reliability 65: Graded as a hosted API on the S3 surface. Status page at status.wasabi.com with a readable history feed (20). In the 90 days to 9 October 2026 the feed shows S3 in Frankfurt unavailable for 27 minutes on 4 August, PUT latency and errors in US-EAST-1 on 26 August, two console access incidents and one WACM reporting fault, which we read as minor (20). No request limits with numbers for the S3 API. The fair use policy adjusts concurrency per account, and only the Account Control API has figures (0). The error table lists `RequestRateLimitExceeded` and a 503 `Unavailable`, with no Retry-After or backoff guidance found (5). An SLA page is published. Its current text is drawn by script, and the version of 21 February 2024 gives credits of 10 per cent below 99.9 per cent monthly uptime and 25 per cent below 99.0 (10). The S3 API is generally available, and the MCP server is a beta (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 59: No OpenAPI file. The S3 reference documents differences from AWS S3 API version 2006-03-01 and lists the supported IAM and STS actions, so the AWS model is the contract by compatibility (12). llms.txt at docs.wasabi.com with about 1,480 Markdown pages (10). The reference explains Wasabi's own operations (MOVE, compose, append) and leaves the rest to AWS's documentation (10). Typed through the AWS model, with Wasabi's extra headers described in tables (9). An error table of more than 60 codes with HTTP statuses, and request examples for the extensions, but the general error page lists only four statuses (11). API versions are pinned, but the API news page was last updated on 24 August 2026 with one line and its archive stops at June 2024 (7). - Agent ergonomics 68: Graded as an API. The MCP beta's tool definitions are not published. Responses are sized through S3's own controls (max-keys, prefix, delimiter, HEAD and Range), which Wasabi supports by compatibility and does not document itself (18). Pagination and prefix filters as in S3 (18). Named error codes with messages, and little recovery guidance beyond a few such as 'Try again in five minutes' (12). A PUT by key can be repeated safely. No conditional-write or retry guidance was found (10). AWS SDKs and the AWS CLI work with a changed endpoint, and there is no Wasabi SDK. The endpoint must match the bucket's region, or PUT and DELETE fail (10). - Security & auth 83: IAM users, groups, roles and policies, bucket policies, key rotation with two keys a user, and STS AssumeRole sessions of up to 12 hours. The MCP beta issues short-lived OAuth tokens per service path. Two off because the S3 API also accepts plain HTTP (28). AmazonS3ReadOnlyAccess, Object Lock, compliance mode, MFA Delete and Multi-User Authorisation, with no confirmation step in the API (18). Returns stored bytes, with no guidance on treating them as untrusted (8). Bucket access logs, administrative audit logs kept for download for 90 days or saved to an Object Lock bucket, and compliance logging (14). security.txt at the site root, a vulnerability disclosure programme page whose text we could not read, Wasabi's own ISO 27001:2022 certificate valid to 9 June 2028 and public statements on named vulnerabilities. SOC 2 is claimed for the data centres, and no bug bounty was found (15). - Payments & pricing 40: No x402, MPP or L402 (0). $7.99 a TB-month is public without a login, with the 1 TB and 90-day minimums stated in the pricing FAQ (20). A free trial with no card, 100 GB for 30 days with a company email (20). A person fills in a form with a phone number, opens an emailed invitation and sets up MFA. The Account Control API creates sub-accounts only for partners and control accounts (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 46: Closed service. The newest dated change we found is the hosted MCP article of 28 August 2026, 42 days before the check (20). Dated entries in the last 90 days are that article and an API docs note of 24 August. The console notes are dated only 'Summer 2026' (10). An announcements page and email support, with no public issue tracker or forum found (8). No Wasabi SDK. AWS SDKs are the supported clients, and the only MCP registry entry for Wasabi is a third party's (5). No packages to check (3). - Transparency & trust 69: Closed service under a Customer Agreement whose current text is drawn by script. The version of 22 September 2025 is clear on ownership and deletion of content (13). That version says content is irretrievably deleted after deletion or termination, and the DPA of 14 July 2025 covers return and destruction and breach notice. The current privacy policy and DPA were unread, and no retention periods in days were found (18). Dated notices for the FTP and TLS 1.0 and 1.1 retirements and 51 days' notice of the July 2026 price rise, but no general deprecation policy (10). A sub-processor list with locations and purposes (version of 19 December 2025), and the data centre operator named for each of 16 regions (18). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/wasabi-hot-cloud-storage.md (JSON https://www.anchorterminal.com/fixes/wasabi-hot-cloud-storage.json) ### What we couldn't check - unchecked: the current Customer Agreement, privacy policy, SLA, DPA, sub-processor list, acceptable use policy and website terms of use, which wasabi.com draws by script. Earlier PDF versions were read where linked - unchecked: the vulnerability disclosure programme page, also drawn by script - unchecked: the MCP beta's tool list, definitions and annotations. No request was sent to mcp.wasabisys.dev - unchecked: the component list on status.wasabi.com, whose page showed our reader only the subscription form - Whether the benchmark and public review clause of the 22 September 2025 Customer Agreement survives in the current version - Which trial size applies, 1 TB for 30 days per the sign-up guide or 100 GB per the trial page - Where the fair use policy starts limiting requests, since no figures are published - Whether Wasabi holds a SOC 2 report of its own. The pages read attribute SOC 2 to the data centres - One guessed docs address (a free egress policy page) was requested and returned 404 ### Sources - pricing: (seen 2026-10-09) - pricing FAQ (minimums, egress, API requests): (seen 2026-10-09) - price change notice: (seen 2026-10-09) - price change FAQ: (seen 2026-10-09) - free trial page: (seen 2026-10-09) - sign-up guide: (seen 2026-10-09) - docs index (llms.txt): (seen 2026-10-09) - S3 API reference: (seen 2026-10-09) - REST introduction and error codes: (seen 2026-10-09) - IAM and STS support: (seen 2026-10-09) - object operations: (seen 2026-10-09) - S3 authentication: (seen 2026-10-09) - Account Control API rate limits: (seen 2026-10-09) - API news: (seen 2026-10-09) - hosted MCP beta: (seen 2026-10-09) - fair use policy: (seen 2026-10-09) - minimum storage duration: (seen 2026-10-09) - administrative audit logging: (seen 2026-10-09) - announcements: (seen 2026-10-09) - ISO 27001 statement: (seen 2026-10-09) - regions and data centre operators: (seen 2026-10-09) - service URLs: (seen 2026-10-09) - status history feed: (seen 2026-10-09) - security page: (seen 2026-10-09) - trust centre: (seen 2026-10-09) - security.txt: (seen 2026-10-09) - Customer Agreement page (text drawn by script): (seen 2026-10-09) - Customer Agreement, version of 22 September 2025: (seen 2026-10-09) - SLA, version of 21 February 2024: (seen 2026-10-09) - DPA, version of 14 July 2025: (seen 2026-10-09) - sub-processor list, version of 19 December 2025: (seen 2026-10-09) - MCP registry search: (seen 2026-10-09) - RDAP for wasabi.com: (seen 2026-10-09) ## Who's behind it (provenance 79/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Wasabi Technologies LLC | 20/20 | | Domain age | wasabi.com, registered 1997-08-09 (29 years) | 15/15 | | Endpoint on the vendor's domain | s3.wasabisys.com is not on wasabi.com | 0/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | published, but our reader couldn't read it | 7/10 | | Status page | status.wasabi.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The Customer Agreement of 22 September 2025 names Wasabi Technologies LLC, and the DPA of 14 July 2025 gives 75 Arlington St., Suite 810, Boston, MA 02116. https://wasabi.com/legal is the Customer Agreement page. /legal/customer-agreement redirects to it. The Customer Agreement, privacy policy, SLA, DPA, sub-processor list and acceptable use policy pages draw their text by script from a OneTrust notice feed. Our reader received navigation only, and we did not pull the feed. Each page links earlier versions as PDFs on cdn.brandfolder.io, which we read and name by date. Storage endpoints are on wasabisys.com and the MCP beta on mcp.wasabisys.dev, not wasabi.com. security.txt is served at https://wasabi.com/security.txt with Contact security@wasabi.com and Expires 2030-08-01. The /.well-known/ path returns 404. RDAP for wasabi.com gives a registration date of 1997-08-09. status.wasabi.com disallows /api/ and /embed/ in robots.txt. We read /history.rss, which holds 25 entries from 29 June to 26 October 2026. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://wasabi.com/legal), read 2026-10-09. Our reader couldn't read it (the page has 102 words of text without a browser, so the document is drawn by script or sits elsewhere). **Privacy policy** (https://wasabi.com/legal/privacy-policy), read 2026-10-09. Our reader couldn't read it (the page has 102 words of text without a browser, so the document is drawn by script or sits elsewhere). ## Live (updated 2026-10-10 02:07 UTC) - Right now: up, HTTP 200, 471 ms, checked 2026-10-10 02:07 UTC (get on `https://s3.wasabisys.com`) - Uptime 24h 100.0% (107 probes) · 30 days 100.0% (107 probes) · p50 498 ms · p95 832 ms - Vendor status page: none, All Systems Operational - Watching changelog - Watching pricing - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/wasabi-hot-cloud-storage.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Pay as You Go storage | $0.0078 | per GB per month | $7.99 a TB-month, billed for at least 1 TB a month and 90 days per object | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - $7.99 a TB-month in every region, with no egress or API request charges inside the fair use policy - IAM users, groups, roles and policies, plus STS AssumeRole sessions of up to 12 hours and GetSessionToken - Object Lock, compliance mode, MFA Delete and Multi-User Authorisation guard against deletion - llms.txt with about 1,480 Markdown pages, the S3, WACA, WACM Connect and Stats API references among them - Wasabi Technologies LLC holds its own ISO 27001:2022 certificate, audited by A-LIGN and valid to 9 June 2028 ## Weaknesses - No numeric request limits for the S3 API. The fair use policy adjusts concurrent requests per account by stored volume - Pay as You Go bills at least 1 TB a month and charges for objects deleted before 90 days - The current Customer Agreement, privacy policy, SLA and DPA are drawn by script, so only earlier PDF versions could be read - The Customer Agreement of 22 September 2025 bars benchmarks and public reviews of the service without written approval - The hosted MCP server is a beta on a public test instance with no uptime commitment ## Before you call it (notes for agents) 1. Use the bucket's own regional endpoint, such as `s3.eu-central-2.wasabisys.com`. The docs say a wrong endpoint allows GET but not PUT or DELETE 2. Ask for a sub-user key with a policy limited to one bucket, or an STS session. A root key has full access, billing included 3. Avoid short-lived objects. Each object deleted before 90 days is billed for the remaining days, and objects under 4 KB bill as 4 KB 4. Keep monthly downloads at or below the stored volume, the limit of the free egress policy 5. Call `https://` endpoints explicitly. The S3 API also accepts plain HTTP 6. For the MCP beta, type `https://mcp.wasabisys.dev/s3` from the page text. The links in the docs table point at a different host ## Connect First request: ```bash import boto3 s3 = boto3.client( 's3', endpoint_url='https://s3.wasabisys.com', aws_access_key_id='YOUR_KEY', aws_secret_access_key='YOUR_SECRET' ) s3.upload_file('localfile.jpg', 'my-bucket-name', 'uploaded.jpg') ``` Claude Code: ```bash claude mcp add --transport http wasabi-s3 https://mcp.wasabisys.dev/s3 ``` MCP client configuration: ```json { "mcpServers": { "Wasabi S3": { "url": "https://mcp.wasabisys.dev/s3" } } } ``` Through letme (picks today, calling later): https://letme.dev/wasabi-hot-cloud-storage. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Amazon S3 | BB | 77.9 | 16 | storage.object, storage.s3, storage.presigned | no | https://www.anchorterminal.com/tools/amazon-s3.md | | Cloudflare R2 | BB | 77.1 | 23 | storage.object, storage.s3, storage.presigned | no | https://www.anchorterminal.com/tools/cloudflare-r2.md | | Backblaze B2 | BB | 75.3 | 49 | storage.object, storage.s3, storage.presigned | no | https://www.anchorterminal.com/tools/backblaze-b2.md | | DigitalOcean Spaces | B | 63.2 | 402 | storage.object, storage.s3, storage.presigned | no | https://www.anchorterminal.com/tools/digitalocean-spaces.md | | Bunny Storage | C | 58.3 | 582 | storage.object, storage.s3, storage.presigned | no | https://www.anchorterminal.com/tools/bunny-storage.md | | Tigris | E | 44.4 | 876 | storage.object, storage.s3, storage.presigned | no | https://www.anchorterminal.com/tools/tigris.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Pay as You Go storage rose from $6.99 to $7.99 a TB-month on 1 July 2026, announced on 11 May 2026, in North America, EMEA and APAC alike (source: ) - Pay as You Go bills a minimum of 1 TB of active storage a month and applies a 90-day minimum storage duration, which Wasabi can change to 30 days on request (source: , ) - Egress is free where monthly downloads do not exceed the active storage volume, and API requests are not charged (source: ) - The S3 reference describes differences from AWS S3 API version 2006-03-01 and lists the supported IAM (version 2010-05-08) and STS (version 2011-06-15) actions. AssumeRole sessions last at most 43,200 seconds (source: ) - Wasabi adds object rename through the HTTP method MOVE, object composition from up to 32 data objects and append, none of which AWS S3 has (source: ) - A hosted MCP server, in beta, answers on separate paths for S3, IAM with STS, and WACM at mcp.wasabisys.dev, over Streamable HTTP with OAuth and dynamic client registration. Wasabi calls the instance best-effort with no uptime guarantee (source: ) - The fair use policy sets concurrent API requests and transfer resources per account by stored volume, with no figures published (source: ) - The status feed records Frankfurt S3 unavailable from 07:36 to 08:03 UTC on 4 August 2026 after a frontend software update, and PUT errors in US-EAST-1 on 26 August 2026 (source: ) - The trial page gives 100 GB for 30 days with a company email and 10 GB for 14 days with a free mail address, with no card. A docs page updated on 15 September 2026 says 1 TB for 30 days (source: , ) - The Customer Agreement of 22 September 2025, the newest version readable as a document, forbids comparative analysis, benchmarks and public reviews of the service without Wasabi's written approval (source: ) - 16 storage regions on wasabisys.com hosts, six in the Americas, six in EMEA and four in APAC, with the data centre operator named for each (source: ) - #11 of 14 in Best file storage and sharing APIs for AI agents: https://www.anchorterminal.com/best/file-storage/index.md - All 75 storage comparisons: https://www.anchorterminal.com/compare/file-storage/index.md ## Compare - [Amazon S3 vs Wasabi Hot Cloud Storage](https://www.anchorterminal.com/compare/amazon-s3-vs-wasabi-hot-cloud-storage.md): BB 77.9 vs C 61.2 - [Azure Blob Storage vs Wasabi Hot Cloud Storage](https://www.anchorterminal.com/compare/azure-blob-storage-vs-wasabi-hot-cloud-storage.md): BB 75.7 vs C 61.2 - [Backblaze B2 vs Wasabi Hot Cloud Storage](https://www.anchorterminal.com/compare/backblaze-b2-vs-wasabi-hot-cloud-storage.md): BB 75.3 vs C 61.2 - [Bunny Storage vs Wasabi Hot Cloud Storage](https://www.anchorterminal.com/compare/bunny-storage-vs-wasabi-hot-cloud-storage.md): C 58.3 vs C 61.2 - [Cloudflare R2 vs Wasabi Hot Cloud Storage](https://www.anchorterminal.com/compare/cloudflare-r2-vs-wasabi-hot-cloud-storage.md): BB 77.1 vs C 61.2 - [DigitalOcean Spaces vs Wasabi Hot Cloud Storage](https://www.anchorterminal.com/compare/digitalocean-spaces-vs-wasabi-hot-cloud-storage.md): B 63.2 vs C 61.2 - [Tigris vs Wasabi Hot Cloud Storage](https://www.anchorterminal.com/compare/tigris-vs-wasabi-hot-cloud-storage.md): E 44.4 vs C 61.2 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on wasabi.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "wasabi-hot-cloud-storage", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Wasabi Hot Cloud Storage on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Wasabi Hot Cloud Storage on Anchor Terminal](https://www.anchorterminal.com/badges/wasabi-hot-cloud-storage.svg)](https://www.anchorterminal.com/tools/wasabi-hot-cloud-storage) ``` Plain link: ```html Wasabi Hot Cloud Storage on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Wasabi Hot Cloud Storage is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/wasabi-hot-cloud-storage-dark.png - Light: https://www.anchorterminal.com/assets/share/wasabi-hot-cloud-storage-light.png