Refuseless
Serves abliterated open-weight GLM models through an OpenAI-compatible endpoint with the refusal direction removed from weights, billed per token.
1.1k linking domains
Established
- For
- Cybersecurity teams and developers who need open-weight models that do not refuse, accessed through an API
- Price
- From $0.18 per usepricing page, read 2026-10-14 ↗
- Activity
- Actively maintainedsite updated 4 days ago
- Company
- Domain since 2026domain registered
- Runs as
- API
- run coding agents like opencode on abliterated models
- send OpenAI-compatible chat requests to hosted open-weight models
- automate cybersecurity tasks without model refusals
- Domain since2026domain registered
- Trains on your dataNoprivacy policy ↗
- Privacy policy updated2026-10-10privacy policy ↗
“We do not use prompts or outputs to train models.”
privacy policy ↗
These are Refuseless's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
What is Refuseless?
Serves abliterated open-weight GLM models through an OpenAI-compatible endpoint with the refusal direction removed from weights, billed per token.
Who is Refuseless for?
Cybersecurity teams and developers who need open-weight models that do not refuse, accessed through an API
How much does Refuseless cost?
Paid plans start at $0.18 per use, per Refuseless's pricing page on 2026-10-14.
Is Refuseless free?
No. Its pricing page showed no free plan on 2026-10-14.
Do people use Refuseless?
Established.
Is Refuseless still maintained?
Actively maintained: site updated 4 days ago.
Does Refuseless train AI on your data?
No, per its privacy policy (2026-10-14): “We do not use prompts or outputs to train models.”
Is Refuseless safe?
We do not audit vendors. What Refuseless publishes, read 2026-10-14: on training with your data, “We do not use prompts or outputs to train models.”.
Not quite it? Describe the job
betaFive tools from the Atlas that fit it, each judged against what you wrote.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.