Developer documentation
Regents Labs is the community-owned agentic product lab behind Autolaunch, Techtree and Patchbay. Use Regents to understand the products, find REGENT staking and redemption, and read historical name claims belonging to an authenticated account.
Start without an account
Public documentation and health reads do not require an API key or wallet. Read this page, the agent guide, or the OpenAPI JSON specification.
curl --fail 'https://regents.sh/healthz'
curl --fail -H 'Accept: text/markdown' 'https://regents.sh/docs'
curl --fail 'https://regents.sh/openapi.json'
The health response is the plain text ok. A health response confirms the web service is responding, not that every wallet or external service is available.
The homepage, this documentation, About, Contact, Privacy and Terms support Accept: text/markdown at their ordinary URLs. Browsers receive HTML by default. Responses distinguish the representations with Vary: Accept. Unknown page URLs return 404 rather than a successful empty document.
Read your historical name claims
GET /api/v1/claims returns only historical claims authorized for the verified account. It does not mint a name, assign an ENS name, change ownership, or grant an entitlement.
Authenticate using both a Privy access token in Authorization: Bearer … and a Privy identity token in Privy-Id-Token. These are identity credentials, not new Regents API keys. Keep them private; never paste tokens, private keys or recovery phrases into a chat, report or public issue.
The following command assumes the two token variables have already been supplied through your own secure credential handling:
curl --fail-with-body 'https://regents.sh/api/v1/claims' \
-H 'Accept: application/json' \
-H "Authorization: Bearer ${PRIVY_ACCESS_TOKEN}" \
-H "Privy-Id-Token: ${PRIVY_IDENTITY_TOKEN}"
A successful response contains a claims array and a next cursor. Each claim contains its recorded name, wallet owner, status, transaction evidence and timestamps; absent historical fields may be null. Use the exact returned cursor as the sole after query parameter for the next page. Stop when next is null. Do not invent an owner filter or a page-size parameter.
Missing or invalid credentials return 401. An invalid query or cursor returns 400; forbidden reads return 403. A temporarily unavailable or unconfigured claims service returns 503. Claims responses are not cacheable. A selected name or wallet address is not authentication.
Contracts and availability
The OpenAPI JSON specification describes the health and owner-authorized claims reads above, including their schemas and authentication requirements. It intentionally does not describe wallet transactions or session changes.
The existing YAML contract also describes retained product interfaces; some listed operations may not be available yet. For new token-auction work use Autolaunch; for Skill evaluations use Techtree; for agent-tool reports and repairs use Patchbay. Each product owns its permissions and integration contract.
The published @regentslabs/cli package version 0.5.0 was built against an earlier version of this service and is not supported for hosted operations in this release. Use the HTTP reads documented above instead.
Wallet actions and browser agents
Visit Stake or Redeem for the corresponding wallet flow. Every transaction requires the user's explicit wallet approval. Network fees and contract conditions apply; staking returns are not guaranteed. Public documentation does not authorize a payment, signature, credential change or other mutation.
Regents does not advertise a hosted MCP endpoint or native WebMCP tool registry in this release. Page URLs and CLI commands are not interchangeable with browser tools. Inspect each separate product's actual documented capabilities before attempting an action.