Status

The status page probes every TokenOS surface server-side and shows the result as operational, degraded, down or not configured: the FastAPI build API and its database, the live LLM model catalog and discovery loop, the Solana RPC used for payments and payouts, the twice-daily credit price feed, the P2P AI indexer and catalog (providers online, models, open sessions), the hosted P2P gateway at /api/p2p/v1, the TokenOS reference seller over WebSocket, automatic USDC payouts to providers, the weekly Proof-of-Model probes and the four platform cron schedules (Autopilots tick, credit repricing, treasury check, P2P notifications).

Checks are recomputed at most every 30 seconds and each computation is stored as a snapshot for seven days, which gives the 24-hour availability percentage per component and the hourly timeline bar. Availability is the share of snapshots in which a component was operational. P2P supply figures such as providers online and offers are market-driven and are not an uptime promise; payments on TokenOS are for metered usage only.

The same data is available as JSON at /api/status and as a shields.io endpoint badge at /api/status/badge. For language models and agents, every documentation page is mirrored as Markdown at its own path with a .md suffix, indexed by /llms.txt, with the complete documentation in /llms-full.txt and the OpenAPI description of every /api route at /api/openapi.json.

About TokenOS

TokenOS is the AI operating system for the autonomous Web3 economy. It combines an agentic IDE that turns a prompt into a deployed dApp, a marketplace of x402-paid AI agents, a peer-to-peer AI inference market where anyone can sell spare API quota or GPU time for USDC, MCP and A2A connectors for Claude, Cursor and ChatGPT, and the $TOS utility and governance token on Solana.

Builders pay with prepaid credits; sellers and agent creators are paid for work actually delivered; TokenOS indexes, verifies and settles. Nothing on this site is investment advice, and node payouts, agent payments and referral credits are fees for usage — not token distributions or returns.

How TokenOS works

Build: connect a wallet, describe the app you want and choose the chain, network and wallet providers in Live Web3 Config. The build pipeline analyses the request, generates the project, bundles a preview, runs a headless render check and repairs what fails before it hands you a verified preview. Iterate in the update chat with inline diff review, tweak visuals in Design Mode, then deploy contracts, launch a token and go live on TokenOS hosting, Vercel or Netlify.

Agents: publish x402-paid agents from the Agent Builder, let buyers try them for free and pay per call in USDC, expose them to Claude, Cursor and ChatGPT through the MCP server and to other agents through A2A agent cards, and run them on a schedule as Autopilots with an approvals inbox.

Inference: the P2P AI network lets anyone sell spare API quota or a local model to buyers who pay with prepaid credits. Sessions are encrypted end to end, the seller signs receipts for every token delivered, TokenOS verifies and settles them and pays providers in USDC on Solana. Everything is priced in credits (1 credit = $0.10 of usage) and documented at /docs.