Skip to main content

Welcome to the GPTHuman API

The GPTHuman API enables you to transform AI-generated text into natural, human-sounding prose. This documentation covers everything you need to integrate GPTHuman into your application, including authentication, credit usage, and the POST /v1/humanize response fields returned by the live API.
Looking for a quick start? Jump straight to the POST /v1/humanize endpoint or experiment in the interactive playground on the right.

Usage

Credits & pricing

1 word = 1 credit. The number of credits consumed equals the word count of the text field in your request. Credit packages. Credits are purchased as packages from the API dashboard: API Dashboard. The API Dashboard displays your remaining credits and the available credit packages.

Versions

Current stable version: 1.0.0 (see the Changelog). Future releases will follow semantic versioning.

Authentication

All requests require an API key passed as a Bearer token in the Authorization header:
Authorization: Bearer YOUR_API_KEY
You can create and manage keys from your GPTHuman API dashboard.

Request defaults

If you omit optional request settings, the API applies the following defaults:
  • tone: College
  • mode: Balanced

Response metadata

Successful POST /v1/humanize responses include the rewritten output together with usage and analysis metadata such as:
  • detected language
  • similarity and readability
  • humanScore when available
  • input and output counts
  • creditUsage and remaining creditBalance