AI Humanizer API,built for production.
Ship human-sounding text built to bypass the detectors, straight from your own app. Two endpoints, webhooks, idempotent retries — the same engine that powers Wibble, behind a clean async REST API.
# Submit your textcurl -X POST https://www.wibbleai.com/api/v1/humanize \-H "Authorization: Bearer $WIBBLE_API_KEY" \-H "Content-Type: application/json" \-d '{ "text": "The mitochondria is the powerhouse of the cell." }'# → { "id": "5c2f...", "status": "queued" }# Fetch the result when it's readycurl https://www.wibbleai.com/api/v1/humanize/5c2f... \-H "Authorization: Bearer $WIBBLE_API_KEY"# → { "status": "succeeded",# "output": "Mitochondria are the cell's powerhouses." }
How it works
Two endpoints. That's the whole API.
No SDKs to learn, no session juggling. If you can send an HTTP request, you can ship text built to get past the detectors today.
[ 1 ]
Request access
Email support@wibbleai.com and we'll enable the API for your account, then create a key from your dashboard.
[ 2 ]
Submit your text
POST to /humanize. You get a job id back instantly while the rewrite runs.
[ 3 ]
Ship the humanized text
Poll GET /humanize/{id} or register a webhook — then drop the humanized text straight into your product.
See it in action
Try the quality behind the API
This demo shows the output quality your integration can deliver. Paste something robotic and watch it come back reading like a person.
Boring infrastructure, in the best way
Everything you'd build around a text API — retries, signatures, refunds — is already handled.
[ A ]
The same quality as the app
API jobs deliver the same production-quality humanization as Wibble's dashboard — tuned to bypass detectors while keeping writing sharp. No reduced-quality API tier.
[ B ]
Async by design
Every job returns an id immediately, so there's no long-hanging HTTP request to time out. Poll when convenient or let webhooks come to you.
[ C ]
Webhooks you can trust
Completion callbacks are signed so you can verify every payload came from Wibble, and deliveries retry automatically if your endpoint blips.
[ D ]
Idempotent retries
Send an Idempotency-Key and network retries return the original job instead of charging you twice. Safe to retry blindly.
[ E ]
Word-exact billing
Words are reserved when a job is accepted and only charged on success. Failed jobs refund every reserved word automatically.
[ F ]
Scoped, expiring keys
Up to 10 keys with configurable expiry, revocable instantly and independently. Clear rate limits with honest error codes.
Pricing
By request
We enable the API account by account. Tell us what you're building and your expected volume, and we'll set you up. Failed jobs are always refunded in full.
Comparing options? See how the humanizer APIs stack up on pricing, limits, and reliability.
Questions, answered straight.
Full reference, guides, and webhook docs live at docs.wibbleai.com. Here are the ones people ask first.
How much does the API cost?+
API access is set up account by account, and pricing is agreed when we enable it. Email support@wibbleai.com with your expected volume and we'll get back to you.
Do I need a Wibble subscription to use the API?+
No. API access is set up separately from web subscriptions, so you can integrate Wibble without one. Subscriptions cover the web dashboard.
Is the output as good as the app?+
Yes. API jobs deliver the same production-quality humanization as the dashboard, tuned to bypass detectors while keeping the writing sharp — there is no reduced-quality API tier.
Does it preserve citations and quotations?+
The engine is designed to carry citations and direct quotations through the rewrite, so reference lists and quoted passages stay intact while the surrounding prose is humanized. If your content is academic or research-adjacent, diff a reference list before and after on your own documents to confirm it holds for your sources.
What happens if a job fails?+
Words are reserved when a job is accepted and only charged when it succeeds. If a job fails, every reserved word is refunded to your balance automatically.
What are the limits?+
Up to 2,000 words per request, 5 concurrent jobs per account, and 20 submissions per minute per key. Need more headroom? Reach out — we're happy to talk.
Ship text built to bypass detectors from your product.
Full reference and webhook docs at docs.wibbleai.com.