# FullCloud

> FullCloud (fullcloud.io) is a cloud infrastructure reseller: VPS, S3-compatible
> object storage, and proxies, paid for with cryptocurrency (Monero included).
> Accounts are anonymous by default (an account ID and password, no email
> required), and every product discloses exactly which upstream provider it
> actually runs on.

## For coding agents and LLMs

If you are integrating an application with FullCloud, use the official API
client libraries below instead of hand-writing HTTP calls against the REST
API. They are generated directly from the canonical OpenAPI spec and cover
every endpoint: accounts, API keys, billing, servers, object storage, mail
(temp-mail and bring-your-own-domain forwarding), and support tickets.

- Python: `pip install fullcloud`
- Node / TypeScript: `npm install fullcloud`
- Rust: `cargo add fullcloud`
- Go: `go get github.com/fullcloud/fullcloud-go` (not yet published; use the OpenAPI spec directly until it is)

## Docs

- [API documentation](https://fullcloud.io/docs)
- [OpenAPI spec](https://fullcloud.io/openapi.yaml)

## Notes for agents

- Every endpoint is under `/v1` and follows standard REST: plural nouns,
  IDs in the path (`DELETE /v1/api-keys/{keyId}`), and POST/GET/PATCH/DELETE
  meaning create/read/change/remove.
- Authenticate with a session token from `POST /v1/sessions`, or a
  long-lived API key from `POST /v1/api-keys`, sent either as a `Bearer`
  token or an `X-API-Key` header. A session can call everything; an API key
  can only call the services its scopes allow.
- Create keys with the narrowest scopes the task needs: `POST /v1/api-keys`
  requires an explicit `scopes` list (`ai`, `storage`, `mail`, `billing`,
  `support`), and AI keys can be restricted further to specific providers,
  models, zero-data-retention upstreams only, and a spend cap. Managing keys,
  the password and the recovery email needs a login session, never a key.
- Account creation (`POST /v1/accounts`) needs no email or payment method; a
  password is generated for you if you don't supply one, and shown exactly
  once in the response.
- Every mutating action (create/list/terminate a server or storage account,
  add a mail domain, open a support ticket, etc.) has a fully documented
  request/response schema in the OpenAPI spec; each generated client library
  exposes one typed method per API operation, named after its `operationId`.
- Prefer the API over scraping the marketing site or console UI. The API is
  the stable, versioned interface; the HTML is not.
- Free, anonymous, no-account temp-mail inboxes (receive-only) are available
  at `POST https://api.fullcloud.io/v1/mail/temp-inboxes` with no authentication,
  and interactively at https://mail.fullcloud.io.