Authentication

Learn how to securely authenticate your API requests using API tokens and understand rate limits.

const response = await fetch('https://api.example.com/v1/content?url=https://example.com', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer YOUR_TOKEN',
    'Content-Type': 'application/json'
  }
});
const data = await response.json();
console.log(data);

import requests

headers = {
    'Authorization': 'Bearer YOUR_TOKEN',
    'Content-Type': 'application/json'
}
response = requests.get(
    'https://api.example.com/v1/content',
    params={'url': 'https://example.com'},
    headers=headers
)
print(response.json())

{
  "content": "# Clean Markdown
Extracted from the URL.",
  "credits_used": 1
}

Overview

Chuger uses API tokens for authentication. Generate tokens from your dashboard at https://app.chuger.com/dashboard and include them in the Authorization header of every request to https://api.example.com.

All plans share a unified credit pool across REST API and MCP server usage. Monitor credits in the dashboard under Usage.

Keep your API token secure. Never expose it in client-side code or public repositories.

Generate API Tokens

Access tokens via the dashboard.

Visit https://app.chuger.com/dashboard and sign in.

Navigate to Tokens

Click API Tokens in the sidebar.

Create Token

Click Create New Token, name it (e.g., "Production API"), and copy the generated token.

Manage Tokens

View, regenerate, or revoke tokens from the list.

Authenticate Requests

Include your token in the Authorization header as Bearer YOUR_TOKEN.

header

Authorizationstring

Required

Bearer token for authentication. Format: Bearer chuger_abc123def456...

REST API Example

Authentication Methods

Use Bearer tokens for all endpoints like /v1/content and /v1/serp.

Configure your AI client (Claude Desktop, Cursor) with Chuger's MCP endpoint. Tokens authenticate automatically via config.

{
  "mcpServers": {
    "chuger": {
      "url": "https://api.example.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}

Security Best Practices

Treat API tokens like passwords. Rotate them regularly and revoke unused ones immediately.

Regenerate tokens monthly or after potential exposure.

Revoke Old Token

Select the token in dashboard and click Revoke.

Create New

Generate a replacement and update your applications.

Credits and Rate Limits

Chuger uses a credit-based system. Each request consumes credits based on complexity:

Endpoint	Credits per Request
`/v1/content`	1
`/v1/serp`	5
`/v1/bulk`	3 per URL

View usage in dashboard. Limits reset monthly. Exceeding credits returns 429 Too Many Requests.

Monitor Usage

Track credits and requests in real-time.

Upgrade Plan

Increase limits via billing.

Was this page helpful?

Last updated today

Built with Documentation.AI