Atomically claim logins for one run

Reserves identities so two runs on the same brief cannot deliver the same candidate. A login is claimable when it is not on the list or its previous claim has expired; seen entries and live claims come back as unavailable instead of being stolen. Claims expire, so an interrupted run releases its candidates and the next search can return them again. The list is created on first claim under the same plan cap as POST /v1/lists/{name}/logins, so a fresh brief needs no prior write; exceeding the cap is an invalid_request. Debits 0 monthly credits.

post/v1/lists/{name}/claims

Request

  • Base URL: https://api.githunt.ai
  • URL: https://api.githunt.ai/v1/lists/{name}/claims
  • Auth: one of:
    • HTTP bearer
    • API key in header X-Api-Key

Path parameters

namestring required

Seen list name, 1-64 characters of a-z, 0-9, "-" or "_", starting with a letter or digit. Trimmed and lowercased server-side.

Request body

loginsstring[] required
ttlSecondsinteger

Claim lifetime. Out-of-range values are clamped.

Response

Claim result

successtrue

Example response

{
  "meta": {
    "quota": {
      "month": "2026-07",
      "cost": 1,
      "rollover": 340
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.