Whitepaper

1. Introduction

Anyone building with AI today faces the same friction. The best chat models, the best image models, the best music and video models, and the best search tools all live with different providers. Each provider means another account, another credit card, another API key to store and rotate, another billing dashboard, and another integration to maintain. Teams routinely hold five or more vendor relationships just to ship one product.

The friction is worse for autonomous agents. An agent cannot sign up for an account, pass a card check, or wait for a human to provision keys. The account model that the AI industry inherited from the SaaS era assumes a person is in the loop, and the next generation of software increasingly has no person in the loop.

Ace Data Cloud addresses both problems with one gateway. For people and teams, it collapses the vendor sprawl into one key and one balance. For agents, it removes the account entirely and lets software pay for inference the way software should, per request, on-chain, with settlement it can verify.

2. The Platform

Ace Data Cloud has operated since 2023 as a production gateway to more than 200 models from over 30 providers. One API key reaches the entire catalog: chat completions across the leading frontier and open-source model families, image generation, video generation, music and audio through services such as Suno, voice synthesis, web search, and structured data extraction.

Billing is pay-per-use from a single balance, with no subscription required and free trial credits to start. For most of the catalog, per-call pricing runs materially below official provider rates. The gateway holds a 99.9 percent service level target with public status reporting at status.acedata.cloud.

2.1 Ace Studio

Ace Studio is the platform's web workspace. It gives individuals the full catalog through a browser, chat, image, music, and video in one place, without writing code, replacing a stack of separate AI subscriptions with one metered balance.

2.2 Developer surface

The developer stack is deliberately open and broad. The platform maintains more than 15 MCP servers that connect the catalog directly into agent coding environments such as Cursor, Claude Code, and Cline. Python and Node SDKs cover programmatic use, and a CLI covers scripted workflows. Everything lives publicly at github.com/AceDataCloud.

2.3 Workflows and Dify

The gateway exposes an OpenAI-compatible interface, which means it plugs directly into visual workflow builders such as Dify. A team points Dify at the platform's endpoint with their key, and every model on the catalog becomes a node they can compose into multi-step applications, chat that hands off to image generation, retrieval that feeds a music prompt, or any chain a workflow canvas can express, all metered against one balance. Workflow systems, including Dify, are a core part of the platform's engineering surface and continue to deepen as first-class infrastructure.

2.4 Agent Skills

Agent Skills are installable instruction packs that teach a coding agent how to use the platform's APIs correctly. A single command, npx skills add acedatacloud/skills, gives an agent working knowledge of the endpoints, parameters, and billing for services such as Suno music, Midjourney images, and web search. The skills follow the open agentskills.io standard and work across more than 30 agent environments.

2.5 Nexior

Nexior is the platform's open-source, white-label template. Anyone can fork it, apply their own brand, connect their Ace Data Cloud key, and operate their own AI product that sells chat, image, music, and video to their own users, with the gateway carrying the infrastructure underneath. Together with the Revenue Alliance referral program, it turns the platform into something a builder can resell, not just consume.

3. Live Usage

The platform is not a roadmap. In the thirty days preceding this document, 8.8 thousand unique users ran workloads across 108 active APIs on the gateway, and the platform has processed more than 300 million API calls since launch. Audio generation through Suno currently leads usage, ahead of chat, image, and video. Usage statistics are published on the platform and refreshed continuously.

The usage is revenue, not vanity. Since January 2026 the platform has generated more than $675,000 in revenue, averaging above $96,000 per month as of August 2026. That income funds the cost structure described in the governance section of this document, and it is the reason the platform can afford to keep its token mechanics conservative.

Everything described in the remainder of this document, the payment rails, the token utility, and the revenue governance, sits on top of this running usage rather than on projections.

4. x402: The Keyless Rail

x402 is an open payment protocol built on the HTTP 402 status code. Ace Data Cloud runs it natively as a second billing rail beside classic API-key billing.

The flow is one round trip longer than a normal API call. An agent sends a request to an endpoint. The gateway responds with status 402 and the exact price of the call. The agent signs a USDC payment from its wallet, retries the request with proof of payment attached, and receives the model output. There is no account, no API key, and no prepaid balance. The wallet signature is the authentication, because the ability to pay is the only credential the gateway needs.

The rail is live on Base, Solana, and SKALE, and covers the same catalog as classic billing. Support for Robinhood Chain is merged and awaits activation, where agents will settle in USDG, the chain's native dollar. The x402 client is open source on the platform's GitHub, and full documentation lives at platform.acedata.cloud/x402.

The two rails serve different callers and coexist by design. Teams that meter spend against budgets use API keys and classic billing, where the $ACE holder discount applies. Agents and one-off callers use x402 and settle on-chain. Both reach the same 200 plus models.

5. The $ACE Token

$ACE is the utility token of Ace Data Cloud. It exists to make real usage of the platform cheaper for people who hold it. It is not an investment product, and nothing in this document is a prediction about its price.

Three properties of the launch deserve emphasis because each is verifiable on-chain. The mint authority is revoked, so the supply is permanently capped. The liquidity tokens from graduation were burned rather than locked, which is the stronger guarantee: burned LP has no unlock date and can never be withdrawn by anyone, including the team. And the contract address above is the only $ACE. Any other contract claiming the name is not associated with Ace Data Cloud.

6. Token Utility

Holding $ACE lowers the cost of using the platform. The mechanism is deliberately simple. A user holds $ACE in a Solana wallet they control, binds that wallet to their account on platform.acedata.cloud, and the platform applies a discount to their API billing automatically. There are six discount tiers scaled to holdings, rising to 20 percent off at the highest tier, so smaller holdings earn a smaller but real discount rather than nothing.

The discount applies across the full catalog, from Claude and GPT to Suno, Midjourney, and video models, and it applies to pay-per-use pricing that already runs below official provider rates. The holder discount therefore stacks on the cheaper number, not on list price.

This is the entire utility claim: hold the token, bind the wallet, pay less for the same working product. Utility that depends on future features is deliberately excluded from this document. If new holder benefits ship, they will be documented when they are live.

7. Revenue Governance

Ace Data Cloud governs two separate streams of money under a strict separation. Creator Fees, generated by token activity, are reserved entirely for token-side and ecosystem purposes. Platform Revenue, the business income of Ace Data Cloud and Nexior, funds the actual cost structure of the platform, cost first. Neither stream borrows from the other's purpose.

7.1 Creator Fees

The liquidity injection is the centerpiece and it is deliberately conservative. At the end of each month, a quarter of creator fees is added to the ACE/SOL pool as depth. This adds real liquidity rather than buy pressure. The platform does not market-buy to move its own price, does not run volume incentives, and keeps LP transactions transparent on-chain.

7.2 Platform Revenue

Platform revenue is cost-first by design. The infrastructure that keeps the gateway reliable is paid before any growth spending and before any token-facing action. Buybacks exist in both streams but are deliberately small and low-priority, executed only when revenue is stable and liquidity is already healthy, and they may be paused, deferred, or accumulated. They are never used as a price signal.

8. Open Ecosystem

The platform's growth model runs through builders rather than advertising. The open-source surface, Nexior, the MCP servers, the SDKs, the x402 client, and the Agent Skills, gives developers real components to fork and ship. The Revenue Alliance referral program shares platform revenue with the people who bring usage. Ecosystem incentives from creator fees reward contribution that can be verified on-chain or in shipped code, and explicitly exclude hype-driven campaigns.

This is a deliberate constraint. Incentives follow measurable usage and contribution, not speculation, and the platform declines the short-term tactics, paid vanity listings, volume incentives, and sentiment-driven buybacks, that trade long-term credibility for short-term attention.

9. What Comes Next

The near-term roadmap is short and concrete, in keeping with the rest of this document. The agent surface will continue to deepen, with more skills, more MCP coverage, and further work to make the catalog the default destination for agents that pay their own way. Exchange accessibility for $ACE will expand as listing processes conclude.

Anything further than that belongs in future versions of this document, once it is real.