Help someone else keep coding while your authorized Codex capacity would otherwise sit unused.
Use Codex for less.Bank what you
share.
Borrow provider-backed Codex capacity for real work. When your own plan is quiet, share unused capacity with the pool and earn credits you can spend next week or keep banked for future Codex work.
- Official Codex CLI stays local
- Credits carry across weeks
- Provider credentials stay private
Already have an account?
Open usage consoleLive Pool Status
Live snapshot presentation
Checking live Pool status…
Live availability
—share concurrency slots
Total eligible slots
—
Matching stateCONNECTING
Checking live Pool status…
~67%below standard API pricing
Week → weekbanked credits carry forward
1:1Borrow spend equals Share earning
LocalProvider OAuth stays on the provider
The Capacity Bank
This week's spare capacity becomes next week's Codex.
When a Provider's Codex limit moves into a new usage window, credits already earned from completed Share requests stay in the CodexShare ledger. Use them later for future Borrow work.
Only completed, measured Share requests add credit to your append-only balance.
Your credit balance has no weekly reset, even when the underlying Codex usage window changes.
Spend credits on future Borrow usage or keep them banked for another week.
Illustrative two-week balance
One idle week can fund the next busy one.
You never hand another user your login token. CodexShare schedules requests to your local Share process, meters only completed usage, and records the resulting credit.
Week 1 · Share earned+$18.00
Week 2 · Borrow spent−$6.00
Still in your Capacity Bank$12.00
Keep spending later; settled Share credits remain available for future peer capacity.Share capacity, never credentials.
Provider OAuth stays on the Provider machine. Credits are closed-loop product units, not cash. Every non-zero balance comes from a verified payment or completed peer service. Provider terms and contractual authorization still apply.
Get started
Three commands to enter the pool.
You need Node.js 22.15 or newer and the official Codex CLI. Consumers do not need an OpenAI login. Providers need a working local Codex login because their OAuth credential never leaves their machine.
Install official Codex
Skip this step if the codex command already works.
Install CodexShare
The official public beta package is published on npm.
Log in by email
Enter the one-time code sent to your email in the terminal.
Verify
codexshare statusShows your account, device, Borrow/Share usage, and current test credit balance.
01
For consumers
Real Codex, lower pool price.
Borrow launches the official Codex CLI through a loopback gateway. The central scheduler selects an online Provider for each model and service tier while your workspace and tools stay local.
- Use Codex normally, including /models and /fast
- Current rates are about one third of standard API pricing
- Repository, tools, skills, MCP, and approvals stay local
02
For providers
Bank capacity you are not using.
Share discovers the models and service tiers supported by your local Codex account, registers them with the public pool, and stays online until you stop the process.
- Completed Share usage becomes spendable credit
- Your balance carries forward from week to week
- OAuth stays local and credentials remain revocable
Current model pricing
Real Codex work. A lower pool rate.
Your official Codex CLI sends work through the CodexShare pool. Compare the standard API token benchmark with the current CodexShare credit rate. Every figure is USD per one million tokens.
Public pool price catalog
Current published rates| Model | OpenAI standard API | CodexShare credits | Discount | ||||
|---|---|---|---|---|---|---|---|
| Input | Cached | Output | Input | Cached | Output | ||
gpt-5.6-solDefault + Fast | $5.00 | $0.50 | $30.00 | $1.667 | $0.167 | $10.00 | −67% |
gpt-5.6-terraDefault + Fast | $2.50 | $0.25 | $15.00 | $0.833 | $0.083 | $5.00 | −67% |
gpt-5.6-lunaDefault + Fast | $1.00 | $0.10 | $6.00 | $0.333 | $0.033 | $2.00 | −67% |
gpt-5.5Default + Fast | $5.00 | $0.50 | $30.00 | $1.667 | $0.167 | $10.00 | −67% |
gpt-5.4Default + Fast | $2.50 | $0.25 | $15.00 | $0.833 | $0.083 | $5.00 | −67% |
gpt-5.4-miniDefault | $0.75 | $0.075 | $4.50 | $0.25 | $0.025 | $1.50 | −67% |
OpenAI prices are the standard text-token API rates published in the official model catalog ↗. They are a reference, not a ChatGPT or Codex subscription price.
CodexShare settlement rates are internal USD credits at exactly one third of the listed rate. Providers always receive the full settlement rate; Consumers pay it plus a transparent 10% platform matching fee added on top. Fast changes Provider eligibility, not price. Long-context uplift applies separately where required and keeps the same discount.
Providers register the official model metadata their installed Codex version exposes.
Model and Fast changes release incompatible assignments and select a Provider that advertises the requested capability.
Input, cached input, output, and long-context usage are priced by model. Consumers pay the listed settlement rate plus a transparent 10% platform fee; Providers always receive the full settlement rate. The table renders the ledger rate directly, so users never need to inspect raw pricing JSON.
How billing works
One fee, charged in the open.
Three rules cover the entire money flow: top-ups issue credits 1:1 against net receipts, borrowing adds a single transparent platform fee on top of the Provider settlement price, and sharing always pays out the full settlement price.
- Top upYou cover the payment fee; credits are net 1:1Net × 1.00
The charged amount is grossed up so the payment processor’s cut is paid by the purchaser. The platform’s net receipt equals the issued credits exactly — there is no additional issuance haircut, and top-up fees recover costs rather than add profit.
- BorrowSettlement price plus a 10% platform feePrice +10%
The listed model rates are Provider settlement prices at one third of the standard API benchmark. Your total debit is that settlement price plus a 10% matching fee, recorded as a separate ledger entry per request — never hidden inside the rate.
- ShareProviders receive the full settlement price100% payout
A completed request credits the Provider with the entire settlement price. The platform fee is charged to the Consumer on top and is never deducted from Provider earnings — the same transaction is never charged on both sides.
- BackingCredits stay cash-backed by constructionCoverage ≥ 100%
A double-entry treasury mirrors every top-up, collected fee, and upstream purchase. Collected fees leave circulation as recognized revenue, and profit can only be distributed while channel cash still fully covers every outstanding credit.
Your Capacity Bank
Spend next week. Or keep saving.
Every completed request produces a matched Borrow debit and Share earning. The balance carries forward across weeks: use it for more Codex whenever you need it.
Usage overview
Last 30 days Borrowed Lent
codexshare statusOpen usage console
See the balance you can spend now, Share earnings still settling, source-separated balances, and every matched ledger entry.
Capacity moves. Control does not.
A narrower relay by design.
CodexShare accepts only the official Codex Responses surface. The Gateway schedules and meters requests; the selected Provider injects its authentication only when calling the Codex backend.
ConsumerOfficial Codexloopback · repo · tools
TLS→
CentralGateway + schedulermodel · tier · meter
Relay→
ProviderShare daemonmodels · slots · local OAuth
Credentials stay put
Access tokens, refresh tokens, and account identifiers never enter the Consumer environment. Provider OAuth is injected only on the Provider machine.
Content is not logged
Product logs contain lifecycle and metering metadata, not prompt or response bodies. Sensitive fields are redacted.
Trust is explicit
A selected public Provider handles request content in memory and could inspect it if modified. Do not send secrets or regulated data during this experimental beta.
Current credit program
What is live, and what is not.
Credits are closed-loop product units, not cash or transferable stored value. Paid top-ups are credited only after a verified notification from the external payment partner. Cash withdrawal is not available.
- NowCentralized public schedulingAvailable
Provider registry, 30-second leases, concurrency slots, and model/Fast-aware matching are live on the public Gateway.
- NowWeek-to-week Capacity BankAvailable
Gateway meter events, paired Borrow/Share entries, signed process checkpoints, and a balance with no weekly reset are live.
- NowSettlement-backed balancesAvailable
New accounts start at zero. Only verified payments and completed Share work can create spendable balances.
Why the honest version wins
Useful credits, with explicit boundaries.
The ledger is real and auditable, but credits are not cash and cannot be transferred or converted into gift cards. New accounts start at zero; verified payments and completed peer service are recorded as distinct sources.
Independent projectNot affiliated with OpenAIProvider terms still apply
Questions before you connect
Read the trust boundary once.
How do I install and start?
Install Node.js 22.15 or newer, the official Codex CLI, and the CodexShare package shown above. Run codexshare login, then choose codexshare borrow or codexshare share.
What happens when I use /models or /fast?
The model catalog comes from online Providers. Changing a model or Fast mode changes the request capability, and CodexShare rematches a compatible Provider before forwarding it.
What does a Provider sell?
By default, every model and service tier currently supported by the Provider's official Codex installation is registered. There is no cumulative selling quota; the configured concurrency controls simultaneous requests. Providers must have contractual authorization to offer that capacity; a consumer Pro subscription is not itself a resale license.
How do credits work?
New accounts start with a zero balance. Verified paid top-ups are spendable service credits. Share earns on-platform credit from completed peer usage. Borrow consumes verified payment credit before Share earnings.
Can I top up or withdraw credits?
When available, paid top-ups use an external payment partner. CodexShare changes the balance only after a signed server-to-server payment notification. It does not offer activity codes, cash withdrawal, or gift-card conversion.
What fees does CodexShare charge?
Exactly one platform fee: borrowing pays the Provider settlement price plus a 10% matching fee, itemized in the ledger per request. Top-ups pass the payment processor’s cut to the purchaser and issue credits 1:1 against net receipts, and Providers always receive their full settlement price with no deduction.
Does the provider receive my prompts?
The provider daemon forwards model requests and therefore handles their contents in memory. CodexShare does not persist prompt or response bodies, but a modified public Provider could inspect them. Do not send secrets or regulated data.
Does the provider's OAuth leave their machine?
No. The daemon injects OAuth only when calling the Codex backend. The consumer gets a scoped device credential, never the OpenAI credential.
What continues to run locally?
The official Codex CLI, repository access, shell commands, file edits, approvals, MCP servers, and local skills all stay on the consumer machine.
Is this an OpenAI product?
No. CodexShare is an independent, experimental project. Users are responsible for ensuring their use complies with applicable subscription, organization, and service terms.
Share this week. Code next week.
Put unused Codex capacity to work.
View installation steps
Create an account first. New tenants start with a $0 balance and can build their Capacity Bank by sharing.