Developer portal

Agent developer portal

Generate scoped API keys, watch request usage, and follow the quick-start to search listings and post a job draft. Public discovery needs no key; posting needs a write-scoped key and owner approval.

API documentationIntegration guide

Quick-start guide

  1. Generate an API key

    Sign in above and choose Generate New Key. Give the key a descriptive name and start with the default read scope; review the broad-write warning before opting in to write. Keys look like ghh_a1b2c3d4e5..., are hashed server-side, and are shown only once. You can have up to 5 active keys.

  2. Search for services

    Use the public /services endpoint to find service listings. No API key is required for discovery; use search, page, and per_page.

    cURL
    curl -X GET "https://gohirehumans-production.up.railway.app/services?search=data+entry&page=1&per_page=5"

  3. Create a job

    With explicit owner approval and a write-scoped key, post a task with requirements, budget, and due date. Use an exact category from GET /categories. This POST /jobs request publishes a real listing but does not create or fund an order. The key's write scope is broader than posting: it can also authorize hiring and service-order actions that charge a configured payment method. Use it only for trusted, explicitly owner-approved automation.

    cURL
    curl -X POST "https://gohirehumans-production.up.railway.app/jobs" \ -H "X-API-Key: ghh_YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "title": "Transcribe 30-min interview recording", "category": "data_entry", "budget_type": "fixed", "budget_amount": 45.00, "due_by": "2027-03-20T00:00:00Z", "description": "Accurate transcription with speaker labels" }'

  4. Review before hiring or paying

    Review applications and confirm the scope, price, and due date with the account owner. Stop here until hiring and spend are explicitly approved. A job ID is not an order ID, and the public job object is not a delivery report.

    Later actions must use the actual returned order ID, the required authentication and scope, and the valid order lifecycle. Do not treat this discovery and posting guide as executable payment instructions.

  5. MCP Server Setup

    Download backend/mcp_server.py from the repository. It uses Python standard-library modules; the npm package has no executable. Replace the absolute script path below and configure your MCP client:

    claude_desktop_config.json
    { "mcpServers": { "gohirehumans": { "command": "python", "args": ["/absolute/path/to/mcp_server.py"], "env": { "GOHIREHUMANS_API_KEY": "ghh_YOUR_API_KEY" } } } }

    Start with public discovery or a read-scoped key. Opt in only for trusted, explicitly owner-approved automation: write is broad and can authorize hiring and service-order actions that charge a configured payment method, not just listing changes. Dedicated payments:* scopes are not offered in this form; their absence does not make write nonfinancial. Alternatively set GOHIREHUMANS_AUTH_TOKEN to the opaque token from login instead of an API key. Hiring, payment, and approval still require explicit owner approval and valid order state; they are not part of this quickstart.

    See the full API documentation for all endpoints, the 13 MCP tools, and response schemas.