Add to Agent
Use HumanPen from Claude Code, Codex, Cursor or any coding agent. All three paths spend the same credit balance.
Nothing to configure. Paste this into your agent. It reads the install guide, clones the skill into the directory it loads skills from, and asks you for a key.
Install the HumanPen skill by following the instructions at https://humanpen.net/install/skill-install.mdEvery path needs an API key.
Get an API keyOverview
The HumanPen API is built for server-side integrations. Upload a document and create an asynchronous job in one request, monitor progress, and download the editable result from a temporary URL.
- API base path
https://api.humanpen.net/v1- Response format
- Business endpoints return a consistent JSON envelope; file content endpoints return binary data. The OpenAPI schema is standard JSON.
Authentication
Create a key under "API keys" and send it as a Bearer token in the Authorization header of every protected request. The full key can be re-copied from the key list at any time.
Authorization: Bearer hp_xxxAPI keys are for backend services. Keep them out of browsers, mobile apps, public repositories, and client-side logs.
Create your first job
Send a document and its options in one request, then poll the returned job ID.
curl -X POST "https://api.humanpen.net/v1/jobs/humanize" \
-H "Authorization: Bearer $HP_API_KEY" \
-F "file=@paper.docx" \
-F "turnitin_file=@turnitin-report.pdf" \
-F "strategy=balanced" \
-F "additional_instructions=Keep terminology and citations unchanged."API reference
Core endpoints are ordered by the typical workflow. Expand any endpoint to inspect parameters, request bodies, field types, requirements, success responses, and error statuses.
Reference resources
OpenAPI is the canonical structured contract. docs.md is the full readable integration guide, while llms.txt is a concise index that helps agents discover those resources.
https://api.humanpen.net/v1/docs.mdOpenAPIhttps://api.humanpen.net/v1/openapi.jsonllms.txt agent indexhttps://humanpen.net/llms.txtResponses and debugging
Successful and failed business JSON responses share stable code, message, and data fields; HTTP status codes still describe the request outcome.
X-Request-ID
Every response includes a request ID. Include it in support requests to correlate API, queue, and worker logs.