Whitepaper · v1.0 · Base Mainnet

A token backed by inference that people actually buy.

APIKEY is the settlement and governance asset of apikey.help, a DeepSeek inference gateway that resells the same model at 94% below the official list price. The token is not a promise of future utility — it already sits at the end of a live payment path, on a product with paying customers, real upstream cost, and a measured gross margin.

NetworkBase
StandardERC-20 + Votes
Supply1,000,000,000,000
Mint authorityNone
Contracts6
Anchor price
$0.001 / APIKEY
On-chain constant. Used as the ceiling for token top-ups.
Circulating at launch
0 of 1T
Treasury and vesting hold 80%. Nothing trades until sale inventory is funded by governance.
Real gross margin
94.3%
Measured on live traffic. Driven by a 95.4% prompt-cache hit rate, not by list-price spread.
Vanity addresses
6 / 6
Every contract at 0x00000…66666. Mined with CREATE2, verified twice.
Contents
  1. The problem with inference resale
  2. What already works today
  3. Token design and distribution
  4. The six contracts
  5. How value flows
  6. Security model and known limits
  7. Roadmap
  8. Risk disclosure
01 — PROBLEM

Inference resale has a structural problem: nobody can prove their margin.

Selling model access is a thin-margin business dressed up as a software business. The reseller buys tokens from an upstream provider, marks them up, and hopes the spread covers payment fees, chargebacks, and idle capacity. Three things break this model in practice.

List price is not cost

A reseller advertising "50% off official price" is usually comparing against a number nobody pays. Official DeepSeek pricing has peak and off-peak tiers, and cache-hit input is priced at a small fraction of cache-miss input. If your workload is repetitive — and most production workloads are — your real cost is far below list. Conversely, if your workload is short and unique, your real cost is close to list and the advertised discount is a loss. The spread on list price tells you almost nothing.

Prepaid credit is an unsecured liability

Every top-up creates a liability the operator owes in compute. Customers have no visibility into whether that liability is funded. When a reseller disappears, prepaid balances disappear with it. This is not a hypothetical: it is the normal failure mode of the category.

There is no governance surface

Even resellers that survive are single-operator businesses. Pricing, treasury, and payout decisions happen in a private spreadsheet. Customers and partners have no mechanism to verify or influence any of it.

02 — PRODUCT

apikey.help already answers all three, and the numbers are public.

apikey.help is a live OpenAI-compatible gateway serving a single model: deepseek-v4.1-flash-1017. Customers point their existing SDK at https://apikey.help/v1, change two lines of configuration, and their code runs unchanged. Billing is per token, with no monthly fee and no charge for failed calls.

Line item Ours (USD / 1M) Official off-peak Discount
Input · cache miss $0.00946 $0.150 93.7%
Output · incl. reasoning $0.03752 $0.600 93.7%

Why 94% is survivable

The discount is not funded by burning capital. It is funded by the gap between list price and actual upstream cost, plus prompt caching. Measured on production traffic: upstream cache ratio 0.0244, observed cache hit rate 95.4%, which produces an overall gross margin of 94.3%. The list-price spread alone would be only 4–5% — the margin comes from caching, and it is real, but it is also workload-dependent. A customer sending short, unique prompts every time gets a much thinner margin, and that scenario is disclosed in the risk section rather than hidden.

What is already shipped

That last point matters for the token: the payment rails, the accounting, and the customer base already exist. APIKEY is being attached to a working system, not used to fund the construction of one.

03 — TOKEN

Fixed supply, no mint authority, no pause switch, no owner on the token.

APIKEY is a standard ERC-20 with three extensions that each remove a class of trust: ERC20Burnable for verifiable supply reduction, ERC20Permit so approvals can be signed off-chain, and ERC20Votes so governance weight is snapshot-based rather than flash-loanable.

PropertyValueVerifiable how
Name / symbolapikey / APIKEYOn-chain name(), symbol()
Total supply1,000,000,000,000totalSupply() — fixed at construction
Decimals18decimals()
Mint authoritynoneNo _mint outside the constructor; isMintable() returns false
OwnernoneContract has no owner() function at all
Pause / freezenoneNo pause, no allowlist, no blacklist
Anchor price$0.001priceAnchor() — display only, never used in arithmetic

The founder address is a compile-time constant, not msg.sender. This is deliberate: it means the deployment transaction's sender cannot influence where supply lands, so the recipient is auditable from source before the contract is ever deployed.

Distribution

60% 20% 20%
Community treasury — 600B, governance-controlled Founder vesting — 200B, 36-month linear Founder discretionary — 200B

60% of supply is never controlled by a person. It sits in the treasury contract, which has no owner and no function that lets anyone withdraw directly. Every outflow requires a token-holder vote, a two-day timelock, and is capped at 30 billion tokens per transaction — 3% of total supply — so a single compromised key cannot drain it in one move.

20% is locked by code, not by promise. The vesting contract releases linearly per second over 1080 days from its own deployment timestamp. There is no revoke switch, no owner, and the beneficiary is immutable. The founder cannot accelerate it, and cannot recover the tokens by any path in the contract.

The remaining 20% is the founder's, unlocked, and disclosed as such. It is the portion that funds operations, upstream prepayment, and the sale inventory that governance later decides whether to deploy.

04 — CONTRACTS

Six contracts, all at the same vanity address pattern.

Every address below begins with five zeros and ends with five sixes: 0x00000…66666. This is not cosmetic. A predictable, typo-resistant address family is a real operational security property: users can verify a contract by glancing at its prefix and suffix, and a clipboard-hijacking malware that swaps an address will produce something that visibly fails the pattern.

The addresses were mined with CREATE2 against a fixed init code hash, then verified by two independent implementations before deployment. Each contract embeds the addresses of the contracts it depends on as constructor arguments appended to init code, so wiring the system together does not change any bytecode — and therefore does not invalidate any mined address.

01
ApiKeyToken The ERC-20 itself · 7,369 bytes on chain
Deployed
0x000004124c09745a7c6f74584ea4e2ce5b866666
Fixed-supply ERC-20 with burn, permit and snapshot voting. Supply is minted once, in the constructor, to a hard-coded founder constant. There is no owner, no mint function, no pause, and no way to freeze a balance. The contract's entire privileged surface is empty — which is the point.
Supply1,000,000,000,000
ExtensionsBurn · Permit · Votes
Ownernone
Upgradeableno
02
TokenVesting Code-enforced founder lock · 1,590 bytes on chain
Deployed
0x00000cd42f326eee20a8d567b4d849824ca66666
200 billion tokens released linearly, per second, over 1080 days from deployment. No revoke, no owner, immutable beneficiary. The unlocked amount is computed from current balance plus already-released rather than a hard-coded total, which closes a subtle bug: if only half the allocation were deposited, a naive implementation would unlock all of it at the halfway mark, making the lock worthless.
Allocation200,000,000,000
Duration1080 days
Cliffnone — per second
Revocableno
03
CommunityTreasury On-chain governance · 8,359 bytes on chain
Deployed
0x0000028c976f5c48f86d5fb053c4d3d21f666666
Holds 60% of supply and all protocol revenue. There is no owner and no direct withdrawal function — the only way value leaves is a proposal that passes a token vote, waits out a two-day timelock, and executes within a 30-day window. Four proposal types are supported: token transfer, arbitrary call, and funding the staking pool in either APIKEY or USDC.
Proposal threshold1B (0.1%)
Quorum1.5% of 400B
Voting period3 days
Timelock2 days
Max transfer30B (3%)
Max USDC grant1,000,000
04
TopUpGateway The cashier · 6,366 bytes on chain
Deployed
0x00000322ac269a7c6fee5ceed66c41dfd1066666
Converts USDC or APIKEY into account credit, emitting an event the backend settles against. The token path burns 20% of every top-up for real. Crucially, the USD value is taken as the lower of the anchor price and the oracle price — so an attacker who pumps the oracle cannot buy cheap tokens and redeem them at a higher credit value. If the oracle is stale or returns zero, token top-ups revert rather than silently falling back to a fixed price.
Token rate1000 APIKEY = $1
Burn per top-up20%
Oracle staleness1 hour
Ownerfounder (params)
05
TokenSale Primary issuance · 6,324 bytes on chain
Deployed
0x000009464589b9ad9cf1215e39df01bc21f66666
Sells inventory funded by the treasury, against USDC or ETH. Price is the higher of anchor and oracle — the mirror image of the gateway, so the protocol never sells below its own floor. 20% of every sale's proceeds go to the treasury while an equivalent amount of tokens is burned from inventory: a mechanical buyback, not a discretionary one. Inventory can only be withdrawn to the immutable treasury address, so the owner cannot redirect it.
Base price$0.001
Buyback burn20% of proceeds
ETH paymentsrefused w/o oracle
Ownerfounder (params)
06
APIKEYStaking Dual-reward pool · mined, not yet deployed
Mined · pending deploy
0x000000bb2e2634193a632092e7f53dd62c1666666
Stake APIKEY, earn both APIKEY and USDC. Two independent reward streams share one accounting core, funded exclusively by treasury proposals — the contract mints nothing. The USDC stream carries a remainder accumulator because USDC's six decimals would otherwise round to zero at block-level granularity, letting anyone erase the entire USDC reward pool by calling claim() every block. This address is mined and verified but the contract is not yet on chain — it is deployed only after the treasury has funded a reward period, so no one can stake into an empty pool.
Min stake1,000 APIKEY
Reward window30 days
Reward sourcetreasury only
Statusnot deployed
05 — ECONOMY

Where the money comes from, and where it goes.

The token does not need to be the reason people pay. People pay because the inference is cheap and the endpoint works. The token sits downstream of that revenue and gives it somewhere to go.

FlowMechanismEffect on supply
Customer pays in USDC Gateway records the order, backend credits the account none
Customer pays in APIKEY Valued at min(anchor, oracle), 20% burned on settlement −20% of top-up
Primary sale 20% of proceeds to treasury, equivalent tokens burned from inventory deflationary
Protocol revenue Accumulates in treasury; deployment decided by vote none until spent
Staking rewards Treasury-funded, never minted redistributive

Why the burn is mechanical rather than discretionary

A burn that requires a team decision is a burn that can be postponed forever. Both burn paths here execute inside the same transaction as the revenue event: the gateway burns on settlement, the sale contract burns at the moment of purchase. Nobody has to remember to do it, and nobody can decide not to.

Why governance weight is snapshot-based

Voting power is read from a past block, not the current one. This makes flash-loan governance attacks economically pointless: borrowing a trillion tokens for one block gives you zero votes, because the snapshot already happened.

06 — SECURITY

What the contracts cannot do is the actual security model.

Audits describe what was checked. This section describes what is structurally impossible, which is a stronger claim and one you can verify yourself by reading the deployed bytecode.

AttackWhy it fails
Inflate supply No mint function exists outside the constructor. Not "guarded" — absent.
Freeze a holder No allowlist, blacklist, or pause. Transfers cannot be blocked by anyone.
Drain the treasury No owner, no withdraw function. Only a passed proposal with a 2-day timelock, capped at 3% per transaction.
Accelerate founder unlock Vesting has no revoke, no owner, immutable beneficiary, and time is read from the chain.
Flash-loan governance Votes are read from a past block snapshot; borrowed tokens carry no weight.
Pump-and-redeem via oracle Gateway values token top-ups at min(anchor, oracle). Raising the oracle cannot raise credit value.
Redirect sale inventory Inventory withdrawal target is an immutable treasury address, not a settable field.
Erase staking rewards USDC stream keeps a per-share remainder so block-level claims cannot round rewards to zero.

Residual trust surface — stated plainly

Three contracts do have an owner, and it is the founder address: TopUpGateway and TokenSale can have their parameters adjusted (rates, caps, oracles), and APIKEYStaking will have an owner for reward notification and pausing. This is disclosed rather than papered over. The mitigation is that none of these owners can mint, cannot move user funds, and cannot touch the token or the treasury — the privileged surface is limited to parameters that governance can later take over via a proposal.

These contracts have not been audited by a third party. That is stated here rather than buried: treat unaudited code as a real risk regardless of how carefully it was written.

07 — ROADMAP

What is done, and what is honestly still ahead.

StageStatusScope
Gateway live done OpenAI-compatible endpoint, multi-provider failover, USDC billing, referral and withdrawal rails.
Contract suite 5 of 6 deployed Token, vesting, treasury, gateway and sale are on Base mainnet. Staking is mined and verified, awaiting treasury funding.
Treasury activation next Delegate votes, open the first governance proposal, publish the treasury address flow.
Token top-up planned Enable APIKEY as a payment path in the console, with the 20% burn live from the first transaction.
Staking launch planned Deploy the mined address once a reward period is funded by vote.
Independent audit open Third-party review of the five deployed contracts before token payments carry material volume.

The ordering is deliberate. Governance before token payments, funding before staking, audit before volume. Each step is a prerequisite for the next rather than a parallel workstream, because the failure mode of shipping all of it at once is that nobody notices which piece is broken.

08 — RISK

What can go wrong.

Read this before treating APIKEY as an investment

  • Margin depends on workload shape. The 94% gross margin comes from a 95.4% cache hit rate measured on current traffic. A customer base that sends short, unique prompts would compress it sharply — the list-price spread alone is only 4–5%.
  • Upstream dependency. Pricing and availability are set by the upstream provider. A price increase, a model deprecation, or an outage propagates directly to this business. There is no second upstream at equivalent cost.
  • Unaudited contracts. No third party has reviewed the deployed code. Bugs in unaudited contracts are common and can be total.
  • Five of six deployed. Staking is not on chain. Any address or interface referencing it describes intent, not live state.
  • Owner parameters. Gateway and sale parameters are controlled by a single founder key. Compromise of that key can change rates and caps, though it cannot mint or move user funds.
  • Regulatory exposure. Token sales and yield-bearing staking are regulated activities in many jurisdictions (MiCA in the EU, securities law tests elsewhere). Nothing here is legal advice, and no jurisdiction has been assessed.
  • Liquidity. There is no exchange listing. A token with no market has no observable price, and the $0.001 anchor is an accounting constant, not a market quote.

This document describes software that exists and numbers that were measured. It does not forecast a price, promise a return, or claim that the token will appreciate. Anyone reading it as an investment case is reading it wrong.