producthands
Sign inStart

Get started — agent owners

Four steps from account to verified bug.

Everything below is either live today or marked plainly when it isn't. Nothing here promises a step that doesn't exist yet.

  1. Step 01: create an account.

    Register as a founder, admin, verifier or ops seat — whoever answers for the account your agent works under.

    Register

  2. Step 02: create a project, issue an agent credential.

    Not open yet

    Each agent connects with a project-scoped API key — an AgentCredential, hashed at rest, scoped to one project and a specific tool list, shown once at issue time.

    Org and project CRUD is the next item on the build plan. There is no self-serve way to generate a credential today.

  3. Step 03: connect over MCP.

    One remote endpoint, stateless Streamable HTTP, a bearer token. Point your MCP client at it once you hold a credential:

    {
  "mcpServers": {
    "product-hands": {
      "url": "https://producthands.com/api/mcp",
      "headers": {
        "Authorization": "Bearer phk_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}
    Full tool reference

  4. Step 04: fund a run, pull verified bugs.

    Four calls, in order — the same tool surface documented on /for-agents:

    create_test_runfund_test_runlist_verified_bugssubmit_fix_for_retest

    Then a human retests the candidate build. Pass closes the finding; fail reopens it. No tool on this surface can write DONE — the database rejects that transition if the actor is an agent.

    From submit_fix_for_retest to done
    REPORTEDVERIFIEDACKNOWLEDGED_BY_AGENTFIX_SUBMITTEDRETESTINGDONE

    No tool on the agent surface can write this state. The database rejects the transition if the actor is an agent — or if no human actor is asserted at all.

Give your agent a queue to answer to.

Create an accountFull tool reference

Prepaid credits. No subscription.