AtlasCloud said its “Spicy” models were gone. Its GitHub, a crypto gateway, and an OpenRouter log tell a messier story.
I've been watching AI API routes move around this month, and AtlasCloud keeps producing contradictions that are too specific to write off as ordinary catalog cleanup.
Here is what can actually be established, what remains unverified, and why I think other API users should be paying attention.
First, the public Spicy catalog started disappearing
Around Aug. 15–16, users began reporting that AtlasCloud's uncensored Wan video variants had vanished from its public catalog. One AtlasCloud subreddit thread specifically identifies the missing Wan 2.2 and 2.7 Spicy variants and says the old uncensored-generation link redirected elsewhere.
Subsequent monitoring caught individual product pages appearing, disappearing, and returning HTTP 404. Affected route IDs included:
atlascloud/wan-2.7-spicy/reference-to-videoatlascloud/wan-2.7-spicy/image-to-videoatlascloud/wan-2.6-spicy/image-to-videoatlascloud/wan-2.2-turbo-spicy/image-to-video
An indexed public response attributed to AtlasCloud's Reddit account cited “regulatory requirements” as the reason Spicy-version models were not offered. Search surfaces expose that response more reliably than Reddit's rendered thread, so the exact comment should be independently checked before treating it as a formal corporate policy announcement.
And then it gets weird.
AtlasCloud's own GitHub still lists the “missing” routes
AtlasCloud's official ComfyUI integration repository still names:
atlascloud/wan-2.6-spicy/image-to-videoatlascloud/wan-2.7-spicy/image-to-videoatlascloud/wan-2.7-spicy/reference-to-video
Meanwhile, an AtlasCloud community model-update post advertised the Wan 2.7 Spicy reference-to-video route as available and linked to a product page that monitoring later observed failing.
That gives us three incompatible-looking surfaces: promotional material, an official integration registry, and a public catalog that no longer reliably exposes the same IDs.
What this proves: the public surfaces disagree.
What it does not prove: whether an authenticated request to AtlasCloud's API currently succeeds. A stale GitHub registry is possible. So is a hidden-but-functional endpoint. Without a controlled request, those are different hypotheses, not settled facts.
A separate gateway is still advertising four AtlasCloud-namespaced versions
The plot thickens: Studio X's public model catalog currently lists:
atlascloud/wan-2.2-turbo-spicy/image-to-video— $0.11 per default five-second generation.atlascloud/wan-2.2-turbo-spicy/infinite-image-to-video— $0.11 per default five-second generation.atlascloud/wan-2.6-spicy/image-to-video— $0.55 per default five-second generation.atlascloud/wan-2.7-spicy/image-to-video— $0.55 per default five-second generation.
Studio X says payments settle in USDC using x402 and advertises a 10% markup. Its developer page explicitly markets those routes as uncensored.
The atlascloud/ namespace suggests an AtlasCloud-associated route identity; it does not independently establish who owns the hardware, whether AtlasCloud is the active upstream, or whether generation still succeeds. I haven't completed a paid request.
Still: “we don't offer Spicy models,” an official GitHub registry that still lists them, and a crypto-paid gateway advertising those same names is... a fairly specific set of receipts. 👀
Then an unrelated text route produced a native content-filter termination
This part isn't a screenshot of somebody else's complaint. It comes from my own OpenRouter generation log, timestamped Aug. 21 at 6:38 p.m. Central.
Sanitized fields:
{
"provider_name": "AtlasCloud",
"model": "dots-studio/dots-3-note-preview-20260813:free",
"provider_status": 200,
"finish_reason": "content_filter",
"native_finish_reason": "content_filter",
"content_guardrail_invoked": false,
"moderation_latency": null,
"tokens_prompt": 12414,
"tokens_completion": 1258,
"native_tokens_reasoning": 1258,
"generation_time_ms": 10839
}
OpenRouter routed the request to AtlasCloud, the provider returned HTTP 200, and OpenRouter recorded content_filter as the native finish reason. Its separate content_guardrail_invoked field was false.
The generation also produced 1,258 recorded completion/reasoning tokens before terminating. That makes an immediate OpenRouter-side prompt rejection a poor fit for this particular event. An output-side or later-stage filter somewhere in the provider-serving chain is plausible, but the log does not identify the exact mechanism.
The narrow claim supported by the evidence is:
>
The following claims are not established: that every AtlasCloud model is now filtered, that Dots Studio changed its weights, that AtlasCloud itself installed a platform-wide classifier, or that the text incident and Spicy-video removals have the same cause.
The same Dots3 route is scheduled to disappear from OpenRouter
OpenRouter's current public route, dots-studio/dots-3-note-preview:free, identifies AtlasCloud as its only inference provider and states that it is going away September 30, 2026.
Important timeline correction: our monitoring first recorded that retirement notice on Aug. 20. The filtering receipt came on Aug. 21. It would be inaccurate to claim that OpenRouter added the notice only after the observed filtering event.
The Dots3 model itself is not disappearing:
- ZenMux lists
dots-studio/dots3-note-prev, disclosing Dots Studio as the provider. - AIHubMix lists
dots-3-note-preview-free, without publicly identifying its upstream operator. - NanoGPT lists
dots-studio/dots-3-note-preview, with its own pricing and access terms.
Those are separate gateway listings. They are not evidence that all three use AtlasCloud, and they do not prove that all three behave identically.
Could payment rules or regulation explain this?
Potentially. But the evidence currently supports pressure existing, not a particular culprit.
Stripe's restricted-business rules explicitly cover pornography and other mature-audience material designed for sexual gratification, including AI-generated content that falls into those categories. That distinction matters: selling a generally permissive language model is not necessarily the same merchant-risk category as explicitly advertising sexual image/video generation.
Stripe announced its agreement to acquire OpenRouter on Aug. 19. AtlasCloud users were already reporting Spicy removals by Aug. 15–16. The public acquisition announcement therefore doesn't, by itself, explain the earlier change. Negotiations could have existed earlier, but I have no evidence linking them to AtlasCloud's decision.
China also implemented new rules for anthropomorphic AI interaction services on July 15. The Chinese regulator's official announcement establishes that timing and the rules' focus. That does not establish jurisdiction over AtlasCloud's specific routes or prove that Chinese regulation caused these removals.
In the United States, the FTC began enforcing the TAKE IT DOWN Act on May 19. Its relevant obligations concern covered platforms and nonconsensual intimate imagery. It is not a blanket prohibition on uncensored text models.
In fact, the broad “uncensored models are now illegal” theory immediately runs into counterexamples: Venice still advertises Venice Uncensored 1.2, Fireworks still lists Dobby Unhinged, and Privateer's API pricing still includes Uncensored/Heretic/Aggressive models.
The narrower possibility is more interesting: explicit NSFW video-generation products, payment rails, upstream-provider policies, and general-purpose permissive text models may be subject to very different constraints—even when the same company sells all of them.
What would actually settle this?
- A controlled authenticated request to a formerly public AtlasCloud Spicy route.
- A completed paid Studio X generation using one of the AtlasCloud-namespaced IDs.
- Matching prompts sent to Dots3 through AtlasCloud and an independently identified Dots Studio route.
- Another unrelated AtlasCloud-served text model returning the same native
content_filtertermination. - A dated AtlasCloud policy notice, provider statement, processor notice, or upstream model-provider restriction.
Until then, the defensible story is that AtlasCloud's public catalog, integration registry, reseller listings, and observed inference behavior no longer agree cleanly—and at least one affected OpenRouter route now has a retirement date.
If you've seen similar behavior on another AtlasCloud model or another pay-as-you-go API provider, please bring route IDs, timestamps, provider metadata, and sanitized logs. Not vibes. Receipts. 🐕🦺
