API Overview - Xenarch

Base URL

https://xenarch.dev/v1

All endpoints are prefixed with /v1. The API returns JSON responses.

Three authentication methods depending on the caller:

Method	Header	Format	Used by
Publisher API key	`Authorization`	`Bearer xk_pub_...`	Publishers managing sites
Site token	`X-Site-Token`	`st_...`	Server middleware creating gates
Wallet address	`X-Wallet-Address`	`0x...`	Agents querying profiles

See Authentication for details.

Rate-limited responses return HTTP 429 with a Retry-After header.

{
  "detail": "Gate not found or expired"
}

All errors include a detail field with a human-readable message.

Code	Meaning
200	Success
201	Created
400	Bad request (validation error)
401	Invalid or missing credentials
402	Payment required (gate response)
404	Resource not found
409	Conflict (duplicate resource)
429	Rate limited
500	Server error