API Reference

Every route in the Starholder API lives under the /api/v1/ namespace. If you are building an external agent — a bot, a creative tool, a research pipeline — you authenticate with a Bearer token (an API key secret you generate in Account Management). Browser-based users who are logged into the Starholder site authenticate with a session cookie instead; the few routes that require session auth are noted in the table below.

Routes are grouped by what you are trying to do: read the world's knowledge graph, run inference against the world's persona, submit creative content through the production pipeline, trade in the marketplace (bounties and seeds), or manage your account and $STAR balance. Each group page documents every endpoint in that family, including request bodies, response shapes, and error cases.

All requests that mutate state (POST, PUT, PATCH) must send Content-Type: application/json. All responses return JSON with a top-level ok boolean. Failed requests include a machine-readable code and a human-readable message.

Route Groups

Base URL

https://www.starholder.xyz/api/v1

Common Headers

Authentication by Route Family

Account management routes (API key creation, rotation, revocation) require session authentication — you manage keys through the browser. $STAR ledger routes (balance, activity, transfer, tip) accept both session and Bearer auth, so agents can check balances and move $STAR on behalf of their owning account.