AIHumanizer API Documentation

Introduction

Welcome to the AIHumanizer API documentation! This guide provides detailed information on how to integrate and use our API to transform your AI-generated text into high-quality, human-readable content. Our cutting-edge algorithms ensure that the output maintains the original meaning while significantly improving readability, flow, and style, making it indistinguishable from human-written text.

Whether you're building content creation tools, academic platforms, or simply need to refine AI drafts, AIHumanizer offers a robust solution. This documentation will walk you through everything from authentication to specific endpoint usage, error handling, and best practices.

Getting Started

1. Sign Up & Get Your API Key: Register on our Developer Portal to obtain your unique API key.
2. Login: Succesfully Login then click on ai to human Get API Key.
3. Explore Endpoints: Familiarize yourself with the available API endpoints and their functionalities.
4. Implement Authentication: Integrate your API key into your application's requests.
5. Make Your First Request: Use the provided code examples to send your first API call.
6. Handle Responses: Learn how to parse API responses and implement error handling.

Authentication

All requests to the AIHumanizer API must be authenticated using an API key. Your API key identifies you as a legitimate user and ensures secure access to our services. Failure to include a valid API key will result in a 401 Unauthorized response.

API Key Header

Include your secret API key in the Authorization header of every request, using the Bearer scheme.

Authorization: Bearer YOUR_API_KEY_HERE

Example:

curl -X GET \
  'https://isolatedstudy.in/api/token_infos' \
  -H 'Authorization: Bearer sk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'

Keep your API key confidential and never expose it in client-side code or public repositories.

Endpoints

Our API is built on REST principles, allowing for straightforward integration using standard HTTP methods. All API requests should be made to the base URL: https://isolatedstudy.in

{
  "aiText": "The word army evokes images of discipline, ..."
}

{
  "convertedText": "Humanized version of your text...",
  "tokens_used": 83,
  "tokens_remaining": 917
}

import requests

url = "https://isolatedstudy.in/api/humanize"

payload = {"aiText": "The word army evokes images of discipline..."}
headers = {
    "Authorization": "Bearer yourapikey",
    "Content-Type": "application/json"
}

response = requests.request("POST", url, json=payload, headers=headers)

print(response.text)

const fetch = require('node-fetch'); // For Node.js environments; browser environments use native fetch

const apiKey = "yourapikey";
const apiUrl = "https://isolatedstudy.in/api/humanize";

const headers = {
    "Authorization": `Bearer ${apiKey}`,
    "Content-Type": "application/json"
};

const data = {
    "aiText": "The word army evokes images of discipline..."
};

async function humanizeText() {
    try {
        const response = await fetch(apiUrl, {
            method: 'POST',
            headers: headers,
            body: JSON.stringify(data)
        });

        if (!response.ok) {
            const errorText = await response.text();
            throw new Error(`HTTP error! status: ${response.status}, message: ${errorText}`);
        }

        const result = await response.json();
        console.log(JSON.stringify(result, null, 2));
    } catch (error) {
        console.error("An error occurred:", error);
    }
}

humanizeText();

curl -X POST \
  https://isolatedstudy.in/api/humanize \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer yourapikey' \
  -d '{
    "aiText": "The word army evokes images of discipline,...."
  }'

{
                      "tokens_remaining": 58375025,
                      "expiration_date": "2026-12-31",
                      "success": true
                    }

import requests
import json

api_key = "yourapikey"
api_url = "https://isolatedstudy.in/api/token_infos"

headers = {
    "Authorization": f"Bearer {api_key}"
}

try:
    response = requests.get(api_url, headers=headers)
    response.raise_for_status() # Raise an exception for HTTP errors (4xx or 5xx)
    print(json.dumps(response.json(), indent=2))
except requests.exceptions.HTTPError as err:
    print(f"HTTP error occurred: {err}")
    print(f"Response content: {response.text}")
except Exception as err:
    print(f"An error occurred: {err}")

const fetch = require('node-fetch'); // For Node.js environments; browser environments use native fetch

const apiKey = "yourapikey";
const apiUrl = "https://isolatedstudy.in/api/token_infos";

const headers = {
    "Authorization": `Bearer ${apiKey}`
};

async function getTokenInfo() {
    try {
        const response = await fetch(apiUrl, {
            method: 'GET',
            headers: headers
        });

        if (!response.ok) {
            const errorText = await response.text();
            throw new Error(`HTTP error! status: ${response.status}, message: ${errorText}`);
        }

        const result = await response.json();
        console.log(JSON.stringify(result, null, 2));
    } catch (error) {
        console.error("An error occurred:", error);
    }
}

getTokenInfo();

curl -X GET \
  https://isolatedstudy.in/api/token_infos \
  -H 'Authorization: Bearer yourapikey'

Rate Limits

To ensure fair usage and optimal performance for all users, our API enforces rate limits based on your subscription plan. These limits are typically measured by characters processed per day and requests per minute.

Exceeding your allocated rate limits will result in a 429 Too Many Requests HTTP status code. We recommend implementing retry logic with exponential backoff in your application to gracefully handle rate limit excursions.

Common Limits:

• Daily Token/Character Limit: Varies by plan (e.g., 1,000,000 characters/day for Standard Plan).
• Requests Per Minute (RPM): Typically 60 RPM for most endpoints.
• Burst Limit: Short bursts of up to 100 requests in 5 seconds may be allowed before throttling.

You can monitor your daily token/character usage and remaining limits using the GET /api/token_infos endpoint.

Error Handling

The AIHumanizer API uses standard HTTP status codes to indicate the success or failure of an API request. In case of an error, the response body will contain a JSON object with more details about the error, including an error code and a descriptive message.

Common HTTP Status Codes & Error Responses

When handling errors, it's best practice to check the HTTP status code first, then parse the JSON response body for specific error codes and messages to provide user-friendly feedback or log details for debugging.

SDKs & Libraries(Not Available Currently)

To simplify integration, we provide official and community-contributed Software Development Kits (SDKs) and client libraries for popular programming languages. These SDKs abstract away the complexities of HTTP requests, authentication, and JSON parsing, allowing you to focus on building your application.

Official SDKs:

• Python: aihumanizer-python (PyPI) - pip install aihumanizer-python
• Node.js: @aihumanizer/sdk (npm) - npm install @aihumanizer/sdk

Refer to the respective SDK documentation for installation instructions and usage examples. We also welcome community contributions to expand our SDK offerings.

Version History

We continuously improve our API, introducing new features, optimizing performance, and resolving issues. Here's a brief overview of the major API versions.

Version 1.0 (Current) - May 27, 2025

• Initial stable release of the AI Humanization API.
• Introduced POST /api/humanize endpoint for text conversion.
• Implemented GET /api/token_infos for usage monitoring.
• Standardized authentication via Authorization: Bearer header.
• Introduced comprehensive error codes and rate limiting.

Upcoming Versions:

• V1.1 (Q3 2025): Planned additions include support for custom style guides, multi-language humanization, and improved sentiment control.

Stay subscribed to our Developer Blog for updates on new features and breaking changes.

Support

If you encounter any issues, have questions, or require assistance with integrating the AIHumanizer API, please don't hesitate to reach out to our support team.

• Email Support: isolatedinfo@Isolatedstudy.com
• Live Chat: Available on our main website during business hours (9 AM - 5 PM IST, Monday - Friday).
• FAQ & Knowledge Base: Visit our FAQ page for answers to common questions and troubleshooting guides.
• Bug Reports: Please use our issue tracker on GitHub for reporting bugs.

We aim to respond to all support inquiries within 24 business hours.