www.studio-x.cc
https://www.studio-x.cc/api/generate/imageShares a payout wallet with 3 other endpoints — its adoption is attributed from that shared wallet's traffic, not earned exclusively.
Studio X uncensored NSFW image generation with Flux Dev
Reliability & health
Uptime and response time from our own unpaid probes, plus the reliability score built from them.
Uptime
100.0% avgResponse time
p50 78ms · p95 142msData table
| Bucket | Uptime | Probes | Response time |
|---|---|---|---|
| 7/22/2026, 12:00:00 AM | 100% | 1 | 100ms |
| 7/23/2026, 12:00:00 AM | 100% | 1 | 65ms |
| 7/24/2026, 12:00:00 AM | 100% | 1 | 73ms |
| 7/25/2026, 12:00:00 AM | 100% | 1 | 76ms |
| 7/26/2026, 12:00:00 AM | 100% | 1 | 92ms |
| 7/27/2026, 12:00:00 AM | 100% | 1 | 82ms |
| 7/28/2026, 12:00:00 AM | 100% | 1 | 74ms |
| 7/29/2026, 12:00:00 AM | 100% | 1 | 97ms |
| 7/30/2026, 12:00:00 AM | 100% | 1 | 107ms |
| 7/31/2026, 12:00:00 AM | 100% | 1 | 76ms |
| 8/1/2026, 12:00:00 AM | 100% | 1 | 111ms |
| 8/2/2026, 12:00:00 AM | 100% | 1 | 165ms |
| 8/3/2026, 12:00:00 AM | 100% | 1 | 94ms |
| 8/4/2026, 12:00:00 AM | 100% | 1 | 70ms |
| 8/5/2026, 12:00:00 AM | 100% | 1 | 90ms |
| 8/6/2026, 12:00:00 AM | 100% | 1 | 77ms |
| 8/7/2026, 12:00:00 AM | 100% | 1 | 113ms |
| 8/8/2026, 12:00:00 AM | 100% | 1 | 82ms |
| 8/9/2026, 12:00:00 AM | 100% | 1 | 83ms |
| 8/10/2026, 12:00:00 AM | 100% | 1 | 60ms |
| 8/11/2026, 12:00:00 AM | 100% | 1 | 83ms |
| 8/12/2026, 12:00:00 AM | 100% | 1 | 72ms |
| 8/13/2026, 12:00:00 AM | 100% | 1 | 72ms |
| 8/14/2026, 12:00:00 AM | 100% | 1 | 70ms |
| 8/15/2026, 12:00:00 AM | 100% | 1 | 60ms |
| 8/16/2026, 12:00:00 AM | 100% | 1 | 68ms |
| 8/17/2026, 12:00:00 AM | 100% | 1 | 74ms |
| 8/18/2026, 12:00:00 AM | 100% | 1 | 70ms |
| 8/19/2026, 12:00:00 AM | 100% | 20 | 80ms |
| 8/20/2026, 12:00:00 AM | 100% | 20 | 81ms |
- Availability
- 100
- Latency
- 100
- Security
- 100
- Transparency
- 61
- Activity
- 11
How often it was reachable when we probed it (weight 35%).
How quickly it answers when it is up — fast scores high (weight 20%).
Whether it serves over working TLS / https (weight 15%).
Whether the operator disclosed what it does — description, schema, identity (weight 15%).
Observed on-chain payments to this endpoint's wallet — transactions, volume, and distinct paying wallets over the last month (weight 15%; not yet measured when we have not seen its wallet settle).
Confidence 100% — how much probe evidence backs this score. A thin history is flagged, not hidden.
See the scoring methodology for exactly how each number is computed.
Payment
- Currencies
- USDC
- Networks
- base
- Facilitator
- unknown
- SDK
- unknown
Operator
- Company
- inferred — unknown
- Jurisdiction
- —
- Registrar
- —
- Domain registered
- —
- Hosting network
- VERCEL-09
- Hosting country
- —
Operator context is derived from public RDAP/TLS records and unverified. Company and country are only available for endpoints that publish them (an OV/EV TLS certificate or a non-redacted domain record); most endpoints are CDN-fronted and disclose neither.
On-chain activity (base)
Payments per day
last payment 8/17/2026Data table
| Day | Payments | Volume (USD) | Paying wallets |
|---|---|---|---|
| 8/5/2026 | 21 | 8.8 | 1 |
| 8/11/2026 | 6 | 2.59 | 1 |
| 8/15/2026 | 7 | 0.12 | 2 |
| 8/17/2026 | 2 | 0.05 | 1 |
Payout address changed 2 times, last on 7/14/2026
- 0x5a9A…9311 → 0x1919…679c (base) · 7/14/2026
- 0x1919…679c → 0x5a9A…9311 (base) · 7/14/2026
A changed payout address is worth a second look — it can be routine, but it is also how a hijacked listing redirects funds.
This payout wallet is shared: figures cover all 4 endpoints paid at it, since payments cannot be attributed to one of them. Only payments settled on chains and facilitators we index.
Linked by wallet — likely same operator
On-chain agent identity and the x402 endpoint that shares its settlement wallet.
Response schema
{
"$ref": "#/components/schemas/GenerationSubmitted"
}