Grok 4.6 실행 사례와 token 비용 비교, 성공 결과당 가격 기준

On tokens and prices per token. I said I’d write more about this, so here goes: an OpenAI token != another model’s token. We compare AI prices in dollars per million tokens as if a token were a standardized unit, like a gram or a kilowatt-hour. It isn’t. Different models use and produce the exact same text using different numbers of tokens, which means a lower price per token does not necessarily mean a lower bill. Imagine two identical pizzas. One is cut into 8 slices at $2 each. The other is cut into 16 slices at $1.25 each. The second place advertises cheaper slices, but the whole pizza costs $20 instead of $16. Bummer ... your stomach doesn't actually care about the number of slices you just ate. I know you are hungry now, but back to tokens. In one small comparison spanning English, technical, multilingual, and numerical text, the tokenizer we use for GPT-5.6 Sol used 766 tokens versus an estimated 1,170 for Claude Opus 5. That's a very significant difference of about 34.5% fewer tokens. You can get the same exact text, but pay for all those extra tokens. The price per token doesn't really tell this story. Even correcting for tokenizer differences misses the bigger point. What actually matters is price per successful outcome, and for that you can use benchmarks as a starting point, but really you have to try it and measure on your own use cases. That's all. May the tokens flow.

I'll write more extensively about this, but OpenAI token != A\ token. We use different tokenizers. And OpenAI's tokenizer is significantly more efficient. This is important given you pay per token over the API and in usage. The difference is ~30% in number of tokens, definitely significant.

Ok Grok 4.6 is getting scary good. Games. 3D worlds. Game trailers. Even real-world 3D prints. 10 wild examples:

Min Choi

@minchoi

2. Grok made its own video game trailer It played, recorded, edited, and voiced everything itself.

Nice thing about Grok @bot is that you can throw any idea into the @bot , even a backburner one. The @bot will just implement it, waiting for you to review. Today I saw my kid struggling to understand how to break down a number into power sums, and I could not find a good video to explain it, so I asked the @bot to make one. It even made a cheerful voice using the @grok voice API.