Introduction

What Xcity AI OS is, who it's for, and how the pieces fit together.

Xcity AI OS is the operating system for a solar-powered AI civilization. It bundles four product layers — Builder, Exchange, Agent, and Runtime — on top of a 100 GW solar compute base in Argentina, and exposes them through a single account, a single billing plane, and a single OpenAI-compatible inference gateway.

This documentation covers everything a developer, integrator, or enterprise buyer needs to ship on top of Xcity: account setup, the inference API, billing model, sub-product integration, deployment, and operational guarantees.

Who this is for

  • Developers building applications against the inference gateway (tokenhub.xcity.one).
  • Integrators wiring a browser sub-product into the unified identity + billing flow.
  • Enterprises evaluating Xcity for compliance, SLA, residency, and procurement.
  • Operators running the Xcity stack — staging deploys, rotating secrets, debugging webhooks.

What you get

LayerWhat it doesURL
L1 BuilderHosted app and agent platformxcity.one
L2 ExchangeModel + agent marketplacemarket.xcity.one
L3 Agent / RuntimeOpenAI-compatible inference gatewaytokenhub.xcity.one
L4 InfraSolar compute zone, network, identity(operated by Xcity)

All four layers share one identity (Xcity Account), one billing relationship (Stripe-backed), and one usage ledger.

How the docs are organized

  • Get Started — install, authenticate, make your first request.
  • Concepts — mental model for accounts, plans, keys, agents, and the gateway.
  • Products — per-vertical guides (AI Platform, Energy, Estates, Immigration).
  • API Reference — every public endpoint with request/response examples.
  • Guides — task-shaped recipes (integrate auth, ship a sub-product, handle webhooks).
  • Operations — runbooks, deploy, SLAs, incident response.
  • Security & Compliance — DPAs, regions, encryption, audit posture.
  • Enterprise — procurement, custom SLAs, dedicated capacity.

If you’re new, start with Quick Start. If you’re integrating an existing app, jump to Sub-product Integration.

Last updated: