# Ecosystem (/docs/learn/ecosystem) openvoidnet is the whole: one umbrella for AI apps — tools, models, and agents — plus the products around them that make the marketplace work. One company, one account system, one API, one bill. Under it sit two sides. **Voidnet** is the developer side: builders connect, build, and ship through it. **VoidAI** is the consumer side: powered by Voidnet, no code, no API keys, no setup. Two doors into the same family. The parts, each doing exactly one job: * **Voidnet Console** — the marketplace and dashboards ([openvoidnet.com](https://openvoidnet.com)). * **Voidnet** — the API between buyers and publisher apps ([api.openvoidnet.com](https://api.openvoidnet.com)). * **Void Accounts** — the one login for everything ([accounts.openvoidnet.com](https://accounts.openvoidnet.com)). * **VoidAI** — chat connected to the marketplace and a workspace ([chat.openvoidnet.com](https://chat.openvoidnet.com)). * **Void Share** — public links out of the workspace ([share.openvoidnet.com](https://share.openvoidnet.com)). * **Docs** — this site: the contract, written from the live system. What each part does, in detail, follows. ## Voidnet Console [#voidnet-console] The home of the ecosystem. Buyers discover apps in the Marketplace, purchase access, manage API keys, and track usage and spend. Publishers verify and publish apps, set free and paid tiers, connect Stripe once, and track earnings and payouts. Two ways to buy: free access is one click; paid access goes through the wallet (top up once, spend per call) or Stripe checkout (one-time or subscription). Purchases are per app and permanent — buying what you already own is rejected, never double-billed. Developers meet the marketplace here; everyone else meets the same apps in the Void Store, without the developer parts. Everything human-facing — buying, publishing, paying, reconciling — happens here. ([openvoidnet.com/console](https://openvoidnet.com/console)) ## Voidnet [#voidnet] The API between buyers and publisher apps. Every call is authenticated, checked for access, limited, metered, and billed before the answer returns. One endpoint, adapter in the path, per protocol. Buyers never connect to publisher servers directly, and publishers never see buyer credentials. The gateway stands between them on every call. ([api.openvoidnet.com](https://api.openvoidnet.com)) ## Void Accounts [#void-accounts] One login for everything. Sign-up, sign-in, sessions, two-factor, and social login live here; every other product redirects logins to it. An identity created once works across Console, VoidAI, and Share. Developers enroll once and claim a username, which becomes the publisher identity everywhere. Accounts also mints the API keys developers call through. ([accounts.openvoidnet.com](https://accounts.openvoidnet.com)) ## VoidAI [#voidai] Chat with AI connected to the marketplace. The assistant answers with a model and calls published tools mid-turn — checking data, running tools, quoting models — without leaving the conversation. VoidAI is a buyer like any other: same access rules, same metering, same billing. ([chat.openvoidnet.com](https://chat.openvoidnet.com)) ## Workspace [#workspace] Behind every conversation sits a workspace: files the assistant reads, writes, edits, runs, and shares while it works. Work organizes into areas — Notes, Mindmaps, Docs (Word files the AI builds), Slides, Sites (shareable pages), Codespaces (code plus terminal), per-conversation scratches, and Outputs for finished artifacts. Each area opens a matching surface: paged preview for documents, present mode for slides, sandboxed rendering for sites. The assistant works files inside the turn: listing, reading, drafting, editing, running code, handing back links. Files stay private until shared; shared files are pinned while unshared drafts expire under lifecycle rules. ## How AI uses apps and workspace together [#how-ai-uses-apps-and-workspace-together] One turn can span all three: answer with a marketplace model, call a marketplace tool mid-sentence (`appname.toolname`), write the result into a workspace file, build it into a document or deck, and return a public share link. Bring your own keys (Groq, DeepSeek, OpenRouter, OpenAI) and switch models per conversation, or use the built-in models. ## Void Share [#void-share] Workspace results become public links: no login required to view. Documents preview as pages, slides present fullscreen, sites run isolated, PDFs stream, spreadsheets download. Share links rotate or revoke instantly, and oversized files serve as downloads instead of previews. Shared artifacts link back into the ecosystem. ([share.openvoidnet.com](https://share.openvoidnet.com)) ## Docs [#docs] Guides and references for building on Voidnet Console — this site. Protocols, buyer and publisher guides, billing rules, full error catalog. Docs are written from the live system and versioned with it: what you read is the contract you get. ## For publishers: CLI and SDK [#for-publishers-cli-and-sdk] Work from the Console or the terminal. The `openvoidnet` CLI logs in through the browser, lists apps, rotates keys, and tails live request logs. The JavaScript SDK wraps a tool server in one call, including the domain-verification file route. ## How all work together [#how-all-work-together] A buyer signs up in Accounts, gets a key, finds an app in Console, gets access, and calls it through the Voidnet. A publisher enrolls in Accounts, verifies a domain and publishes in Console, serves traffic through the Voidnet, and tracks usage in the same dashboard. No product duplicates another: Console never proxies app traffic, the Voidnet never renders a page, Accounts never touches money, VoidAI never publishes apps, Share never bills. Each request and each dollar crosses each boundary exactly once, in the same order, every time. ## How the ecosystem forms [#how-the-ecosystem-forms] Publishers list capabilities, buyers pay to use them, payouts fund more publishers. Console reduces publishing to a form plus a server URL. The wallet reduces buying to one top-up instead of one checkout per app. VoidAI reduces discovery to a sentence in a chat. Each turn adds supply and demand together: a published app is a reason to sign up, and every signup is an audience for the next app. Share carries artifacts onto the open web, where they return as new users. ## Network effects [#network-effects] More apps make keys and top-ups worth having. More buyers make publishing worth doing. More usage makes payouts larger, which funds better apps. The moat is structural: the purchase graph, usage history, and payout rails grow more valuable with every participant, and none of them transfer by copying code. ## Identity [#identity] Publishers are `@username` — lowercase letters, numbers, and hyphens, 3–20 characters, chosen once at enrollment and never changeable. Every app belongs to exactly one publisher, and every app's public identity is `username/appname`: ``` POST /v1-beta/{adapter}/{username}/{appname} ``` App names are unique per publisher (`a-z, 0-9, -, _`, 3–50 chars). The same pair identifies the app across marketplace pages, purchase records, usage logs, API keys, and gateway routes — MCP tools, LLM models, and beyond. The full system — users, developers, tools, models, agents, keys, and the trust chain — is [Identity](https://docs.openvoidnet.com/docs/learn/identity). ## Composability [#composability] One gateway, one credential shape, one meter — so apps compose. An assistant answers with a model and reaches for tools mid-sentence. An outside product calls a marketplace model for language and marketplace tools for everything else. No special integration: if an app can be called, it can be combined. ## Developer resources [#developer-resources] * [Void Apps](https://docs.openvoidnet.com/docs/learn/void-apps) — app types and how they are consumed and published. * [Voidnet](https://docs.openvoidnet.com/docs/learn/voidnet) — the API contract: one endpoint, errors, auth. * [Identity](https://docs.openvoidnet.com/docs/learn/identity) — the one identity system behind users, developers, tools, models, and agents. * [Get Started](https://docs.openvoidnet.com/docs/get-started) — credentials and your first call. * [API Reference](https://docs.openvoidnet.com/docs/reference/api-reference) · [Error Reference](https://docs.openvoidnet.com/docs/reference/error-reference). * Code: [GitHub](https://github.com/openvoidnet/) · [npm](https://www.npmjs.com/package/openvoidnet) · [PyPI](https://pypi.org/project/openvoidnet/).