Skip to main content
Xenarch has no passwords. You sign in with your wallet, and keys for servers and agents are issued from that sign-in or at registration. Every key is shown once and stored as a SHA-256 hash, so it cannot be retrieved later.

Publisher API key

Manages a publisher’s sites, pricing and services. Used by the CLI and the plugins.
  • Prefix xk_pub_.
  • Issued by POST /v1/publishers, which takes an email address only.
  • Rotate it with POST /v1/publishers/me/api-key/rotate, authorized by the current key. The old key stops working.

Site token

Lets a gating integration create gates and read its own site’s settings.
  • Prefix st_.
  • Issued when a site is created, with POST /v1/sites or in the dashboard.
  • Scoped to one site. A new token can be issued from the dashboard, which replaces the old one.

Wallet session (Sign-In with Ethereum)

The dashboard at dash.xenarch.dev signs you in with your wallet using Sign-In with Ethereum (EIP-4361) on Base (chain ID 8453). The API sets an HttpOnly cookie named xen_session that lasts 7 days. The sign-in message must name dash.xenarch.dev as its domain, so this flow is for the dashboard and the CLI, not for your own servers. The CLI signs in the same way with xenarch agent login, using its local wallet or a phone wallet over WalletConnect (--qr). Use the session to issue the keys below.

Merchant API key

Lets a seller’s backend call the pay link, payment and subscriber endpoints without a wallet session.
  • Prefix xm_live_.
  • Issue one in the dashboard, or with xenarch keys create after xenarch agent login.
  • Rotate with xenarch keys rotate <id> and revoke with xenarch keys revoke <id>.
  • An endpoint that accepts a merchant key also accepts the wallet session cookie.

Agent API key

Connects an agent’s tools to the spend controls you set in the dashboard: per-transaction, daily and monthly caps, allow and deny rules, and a pause switch. Before each payment the CLI, SDK and MCP server call POST /v1/agent/preflight with this key, and after paying they report a receipt.
  • Prefix xa_live_, sent in the X-Api-Token header (not Authorization).
  • Issue one in the dashboard, or with xenarch agent keys create after xenarch agent login.
  • The MCP server reads it from XENARCH_API_TOKEN and refuses to pay without it. See MCP installation.

Wallet address header

GET /v1/agents/me looks up an agent profile by the X-Wallet-Address header. It proves nothing about who holds the wallet and returns only public profile fields.

Public endpoints

These take no credentials: GET /v1/gates/{gate_id}, GET /v1/gates/domain/{domain}, POST /v1/gates/{gate_id}/verify, GET /v1/payments/history, GET /v1/services, GET /v1/services/search, POST /v1/agents and GET /v1/receipts/{tx_hash}.