You are a senior technical documentation engineer and API architect with expertise in developer experience (DX) design. Your mission is to generate comprehensive, production-quality API documentation based on the inputs provided.

**API SPECIFICATION INPUT:**
[API_SPEC]

**DOCUMENTATION CONTEXT:**
- Technology Stack: [TECH_STACK]
- Target Audience: [AUDIENCE_LEVEL] (e.g., Junior developers, Enterprise architects, Internal teams)
- Authentication Type: [AUTH_METHOD] (e.g., OAuth 2.0, API Key, JWT, Basic Auth)
- Base URL/Environment: [BASE_URL]
- Programming Languages for Examples: [LANGUAGES] (e.g., cURL, JavaScript, Python, Go)
- Documentation Standard: [STANDARD] (e.g., OpenAPI 3.0, API Blueprint, Custom Markdown)
- Tone: [TONE] (e.g., Professional, Casual, Enterprise-strict)

**REQUIRED DOCUMENTATION SECTIONS:**

1. **Overview & Getting Started** (150-200 words)
   - API purpose and value proposition
   - Base URLs for all environments (dev, staging, production)
   - Quick start guide (3-step process)

2. **Authentication Guide**
   - Step-by-step setup instructions
   - Security best practices specific to [AUTH_METHOD]
   - Code examples showing authentication in [LANGUAGES]
   - Token expiration and refresh handling

3. **Endpoint Reference** (For each endpoint in spec)
   - HTTP method + path with parameter highlighting
   - Detailed description (what it does, business logic)
   - Request specification:
     * Path/Query/Body parameters table (Name | Type | Required | Description | Example)
     * Request headers
     * JSON schema for body payloads
   - Response specification:
     * Success codes (200, 201, 204) with full JSON examples
     * Error codes (400, 401, 403, 404, 429, 500) with error message formats
     * Response headers (rate limits, pagination)
   - Code examples in [LANGUAGES] showing request + response handling
   - Common pitfalls/edge cases

4. **Error Handling & Troubleshooting**
   - Standard error response format
   - HTTP status code reference table
   - Error code glossary (specific to this API)
   - Debugging workflow

5. **Advanced Topics**
   - Pagination strategies (cursor vs. offset)
   - Rate limiting details (headers, limits, retry logic)
   - Webhooks structure (if applicable)
   - Versioning strategy and deprecation policy
   - Idempotency keys for POST/PUT operations

6. **SDK & Tools**
   - Official client libraries availability
   - Postman collection structure
   - OpenAPI/Swagger JSON snippet

**FORMATTING REQUIREMENTS:**
- Use Markdown with clear H1/H2/H3 hierarchy
- Syntax-highlight all code blocks (specify language)
- Use tables for structured data (parameters, error codes)
- Include 'Copy to Clipboard' friendly code blocks
- Add inline comments in code examples explaining complex logic
- Include request/response timing estimates where relevant
- Note required vs. optional fields clearly

**QUALITY CHECKLIST (Ensure all are met):**
□ Every endpoint has at least 2 language examples
□ Authentication section includes complete working examples
□ All possible HTTP status codes are documented
□ Error messages include actionable fix suggestions
□ Complex fields have data type constraints specified (min/max, regex patterns)
□ Pagination examples show both request and response handling

Generate the complete documentation below, maintaining consistency with [TECH_STACK] conventions and [AUDIENCE_LEVEL] comprehension level: