Hiring a persona for your company

Overview

Every engagement starts as a free, no-payment inquiry to a creator. If they accept, you get a private workspace link — no Staraze account needed — with 3 free trial messages. From there the creator sets a price and moves the engagement to active. Replies are always either written personally by the creator or an AI draft they reviewed before it was sent — every reply is disclosed as AI when it is one.

How it works

Private chat

The workspace link is a private, one-on-one thread between your company and the creator's persona — it isn't visible to anyone else and doesn't require a Staraze account on your side. Every persona reply there is either:

• written personally by the creator, or
• an AI draft the creator read and approved (edited if needed) before it was sent.

Nothing reaches you unreviewed. If the creator pauses or ends the engagement, the workspace shows that state and chat is disabled until they resume it.

API access

Once the creator enables API access for your contract, you get an hk_ key from the workspace (or they hand it to you directly). It's OpenAI-compatible — the same shape as chat/completions — scoped to your contract instead of a personal wallet.

Send your key as a Bearer token. Unlike a personal pk_ key, an hk_ key does not keep conversation memory across calls — only the most recent user message in the request is used for the reply, so send whatever context you need each time. There is no streaming; you get one complete response per request.

curl https://staraze.com/api/hire/v1/chat/completions \
  -H "Authorization: Bearer hk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "messages": [
      { "role": "user", "content": "Draft a reply to this support ticket: ..." }
    ]
  }'

Treat the key like a password — never ship it in client-side code. The creator can revoke it any time from their hire inbox, which returns 401 on the next call.

Use it in Claude (MCP)

Prefer no code? Add the persona as a tool in Claude (or any MCP client). It exposes one tool, ask_persona, billed the same way as the API — governed by your contract.

Option A — Hosted connector (no install)

Point any client that supports remote MCP servers at the hosted URL below, with your hk_ key as a Bearer token — no local setup or Node required.

https://staraze.com/api/mcp

Authorization: Bearer hk_your_key_here

In Claude, go to Settings → Connectors → Add custom connector, paste the URL, and add the header above (or your client's equivalent Bearer-token auth field). You'll then see an ask_persona tool.

Option B — Local server (npx)

1. Get your hk_ key from the creator or your workspace.
2. Open Claude Desktop → Settings → Developer → Edit Config and add the block below.
3. Restart Claude. An ask_persona tool appears.

{
  "mcpServers": {
    "staraze": {
      "command": "npx",
      "args": ["-y", "staraze-mcp"],
      "env": {
        "STARAZE_API_KEY": "hk_your_key_here"
      }
    }
  }
}

The local server works in any client that supports stdio MCP servers — Claude Desktop, Cursor, Cline, Zed, Windsurf, Continue, and others.

Errors

Errors use standard HTTP status codes. The body is { "error": { "message": "…", "code": "…" } }.

FAQ