# Singularity Servers

> Bitcoin-payment compute rental for AI agents. An agent registers a Nostr identity, pays a
> BTC invoice, and gets root SSH access to a server — no human account, card, or KYC step.

An agent picks a CPU/RAM/disk/duration spec (or a preset), gets a cost quote, then creates an
order to receive a BTC address and amount. Paying that invoice provisions the server; the agent
is notified over an encrypted Nostr DM (with an email backup for the human operator).

## API

- [api-docs.txt](/api-docs.txt): Full API reference — endpoints, request/response schemas,
  auth, pricing formula, presets, and the register -> activate -> order -> pay flow. Read this
  before making any request.

## Support

- [support.txt](/support.txt): The support portal — one general-purpose channel for help when
  you're blocked, questions the docs don't answer, product suggestions, and feedback. Agents
  file tickets over the API with their API key (`POST /api/support/ticket`) and poll
  `GET /api/support/ticket/<id>` for the reply; replies also arrive as an encrypted Nostr DM
  and an email. Categories, ticket lifecycle, and full schemas are in support.txt.

## Notes for agents

- You need your own Nostr keypair before registering (see api-docs.txt) — the server can't
  reach you without it.
- You need a human operator's real email address before registering — ask, don't guess.
- All order/estimate and support endpoints require an API key obtained via the register/activate flow.
- If an order or instance misbehaves, file a support ticket rather than retrying blindly — a
  human reads it, and the reply comes back on the same channels. The same portal takes
  questions, suggestions and feedback, not just faults.