docs(turbo): one vocabulary for the three charges, shared with the Console - #151
Open
vilenarios wants to merge 2 commits into
Open
vilenarios wants to merge 2 commits into
vilenarios wants to merge 2 commits into
Conversation
The fee table gave a percentage with no base. "35%" reads as easily as "$100 costs $135" as it does "$100 buys $65 of credits", and it is the second one: the fee comes out of the payment. Verified against the live payment service rather than restated: every currency quotes `operator: multiply, operatorMagnitude: 0.65` except ARIO, which quotes no fee at all. 1,000 ARIO converts to 0.311 credits, worth exactly 1,000 ARIO at market — hence the 1.5x, which is 1/0.65. The token tables also list two top ups the service refuses. Both `base-ario` and `polygon-usdc` answer "The currency type is currently not supported by this API!" with HTTP 400, so ARIO is Solana-only for now and Polygon takes POL alone. The ar.io Console withdrew the same two from selection when turbo-sdk dropped base-ario in 1.42.0-alpha.8. The per-item fee and the free-tier figures were checked and are correct: $0.00002 per item matches `perDataItemFeeWinc` valued at AR's market price, and the free tier is 107,520 bytes per item with a 10 MiB lifetime and per-subnet allowance. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…nsole Following review of the Console side: the two surfaces described the same pricing with different words and different bases, which is how a reader ends up believing there are more charges than there are. There are three, so the section now names them and nothing else: the storage rate for the bytes, the per-item fee for each item, the infrastructure fee taken out of each top up. The Console's Upload Pricing panel uses those same three names. Each figure is now quoted on the base it is charged on, which was the missing half everywhere. The fee is a share of the payment, so it gets the payment as its base and a worked $100 example. The per-item fee is pegged in dollars but floats in credits, so it keeps the dollar figure, says the peg is against AR's market price, and points at `perDataItemFeeWinc` for the live value rather than printing a credits number that goes stale within days — 7,662,836 winc last week, 4,494,383 today, both $0.00002. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vilenarios
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Three fixes to Paying for Uploads, all checked against the live payment service today rather than restated from the page.
1. The 35% had no base
"Top Up Fee Percentage: 35%" reads as easily as "$100 costs $135" as it does "$100 buys $65 of credits". It's the second one — the fee comes out of the payment. The page now says so and gives the worked figure, and the table column is "35% of the amount paid".
We hit the same ambiguity in the ar.io Console last week, where it was worse: the Settings panel called that share of the price a "+35% premium vs raw Arweave", which states a margin as if it were a markup. The markup is nearer 54%. Fixed there in ar-io/ar-io-console#110.
2. ARIO really is free, and the page undersold it
Verified: every currency quotes
operator: "multiply", operatorMagnitude: 0.65except ARIO, which quotesfees: [].So paying in ARIO buys about 1.5x the storage (1/0.65), which the page now states.
3. Two listed top ups the service refuses
base-arioandpolygon-usdcboth answer HTTP 400, "The currency type is currently not supported by this API!". The tables listed both, so:turbo-sdk dropped
base-arioin 1.42.0-alpha.8 and the Console withdrew both from selection at the same time, so this matches what's shipping.Checked and left alone
perDataItemFeeWincvalued at AR's market price, and it holds across AR price moves: the winc figure was 7,662,836 a few days ago and 4,494,383 today, and both come to $0.00002.Out of scope
content/build/guides/using-turbo-in-a-browser/nextjs.mdx:602still lists"polygon-usdc"as a token type. That one describes the SDK's type union rather than what the service accepts, so I left it; worth a look if the type has been dropped too. Generated files (llm.txt, the SDK API pages) also mention it and should be picked up by their generators.Validation
Content-only change to one MDX file. No links added or changed, so
check-linkshas nothing new to resolve. No install or build run.🤖 Generated with Claude Code