[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"article-coding-plan-alibaba-cloud-ide-billing-en":3,"article-related-coding-plan-alibaba-cloud-ide-billing-en":29,"series-tools-085aabb2-11df-4384-82dd-c188ef79c19e":74},{"id":4,"slug":5,"title":6,"content":7,"summary":8,"source":9,"source_url":10,"author":11,"image_url":12,"cover_image":12,"category":13,"language":14,"translated_content":11,"related_article_id":15,"keywords":16,"key_takeaways":22,"views":26,"created_at":27,"published_at":28,"topic_cluster_id":11},"085aabb2-11df-4384-82dd-c188ef79c19e","coding-plan-alibaba-cloud-ide-billing-en","Coding Plan turns Alibaba Cloud into IDE billing","\u003Cp data-speakable=\"summary\">Alibaba Cloud's Coding Plan turns \u003Ca href=\"\u002Ftag\u002Fai-coding\">AI coding\u003C\u002Fa> into a fixed-fee subscription instead of per-call billing.\u003C\u002Fp>\u003Cp>I've been using \u003Ca href=\"\u002Ftag\u002Fai-coding-tools\">AI coding tools\u003C\u002Fa> long enough to know when the pricing model is lying to me. The model feels cheap at first, then I hit a refactor, a debug spiral, or a \u003Ca href=\"\u002Ftag\u002Flong-context\">long context\u003C\u002Fa> session and the bill starts acting like it has a grudge. Even worse, I keep seeing teams wire the same key into everything: IDE plugins, scripts, backend jobs, little cron tasks nobody admits owning. That is exactly where things get messy. The tool looks like one thing, the billing system looks like another, and the usage rules are the part everyone reads only after something breaks.\u003C\u002Fp>\u003Cp>Alibaba Cloud's Coding Plan is the first thing in a while that made me stop and read the fine print instead of skipping it. The source that kicked this off is a Zhihu post by 云多多网络 on \u003Ca href=\"https:\u002F\u002Fzhuanlan.zhihu.com\u002Fp\u002F2061515864340444437\">zhuanlan.zhihu.com\u003C\u002Fa>. It lays out the subscription model, the supported tools, the model list, and the hard boundary between interactive coding and automated API use. It also includes the two endpoints people keep mixing up: OpenAI-compatible at \u003Ca href=\"https:\u002F\u002Fcoding.dashscope.aliyuncs.com\u002Fv1\">coding.dashscope.aliyuncs.com\u002Fv1\u003C\u002Fa> and Anthropic-compatible at \u003Ca href=\"https:\u002F\u002Fcoding.dashscope.aliyuncs.com\u002Fapps\u002Fanthropic\">coding.dashscope.aliyuncs.com\u002Fapps\u002Fanthropic\u003C\u002Fa>.\u003C\u002Fp>\u003Ch2>The part everyone gets wrong: this is not normal API billing\u003C\u002Fh2>\u003Cblockquote>Coding Plan is a fixed monthly subscription built for interactive coding in supported AI tools, not backend automation or batch API calls.\u003C\u002Fblockquote>\u003Cp>What this actually means is simple: Alibaba Cloud is selling a coding seat, not a general-purpose model pipe. The post says the plan is meant for interactive coding assistance inside tools like Cursor, Cline, Qwen Code, and similar editors or CLIs. It is not meant for background jobs, batch scripts, or any workflow where you are basically turning it into a cheap \u003Ca href=\"\u002Ftag\u002Finference\">inference\u003C\u002Fa> backend.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786435438696-k107.png\" alt=\"Coding Plan turns Alibaba Cloud into IDE billing\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>I ran into this exact confusion with other providers before. A team thinks, “We’ll just reuse the same key for the IDE and the service.” Then someone adds retries, another person adds a nightly job, and suddenly the account is doing work it was never priced for. That is how you get disabled access and a very annoying morning.\u003C\u002Fp>\u003Cp>The useful mental model here is: if a human is sitting there steering the conversation, you are probably in the intended lane. If a system is firing requests on its own, you are probably not.\u003C\u002Fp>\u003Cp>How to apply it:\u003C\u002Fp>\u003Cul>\u003Cli>Use Coding Plan in editor plugins, chat-based coding tools, or terminal assistants.\u003C\u002Fli>\u003Cli>Do not point it at backend services, scheduled jobs, or bulk automation.\u003C\u002Fli>\u003Cli>Keep a separate plan for production integration, especially if multiple people or systems will touch it.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>Why fixed-fee pricing matters when you code like a maniac\u003C\u002Fh2>\u003Cp>The post frames the plan as a fixed monthly fee with request quotas, which is exactly why it feels appealing to developers who do bursty work. If I am deep in a debugging session, I do not want to think about every prompt like it is a tiny invoice. I want to ask follow-ups, ask for a rewrite, ask for another rewrite because the first one was too clever, and not feel punished for being iterative.\u003C\u002Fp>\u003Cp>The article says the Pro plan is the only version currently available for new purchase and renewal, while Lite has been phased out for new buying. It also notes a limited-time first-month price of 200 RMB for new users, with later renewals discounted for first-time buyers. I am not going to pretend that makes pricing magically simple, but it does make the subscription story clearer than raw token billing for a lot of solo developers.\u003C\u002Fp>\u003Cp>What this actually means is that the plan is optimized for people who use AI like a power tool during development, not like an embedded server component. That distinction matters because the cost shape is different. A coding session has spikes. A service has a heartbeat. This plan is built for spikes.\u003C\u002Fp>\u003Cp>How to apply it:\u003C\u002Fp>\u003Cul>\u003Cli>If your usage is mostly personal IDE help, estimate value by monthly seat cost, not by token math.\u003C\u002Fli>\u003Cli>If your usage is a team service, do not force it into a coding subscription just because it looks cheaper.\u003C\u002Fli>\u003Cli>Compare the seat price against your current per-call spend over a real month, not a fantasy week.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>The quota system is the real product, not the headline price\u003C\u002Fh2>\u003Cp>The post spends a lot of time on the layered quota design, and I think that is the part worth paying attention to. Pro includes a 5-hour rolling quota, a weekly cap, and a monthly cap. The source says the monthly ceiling is up to 90,000 requests, with 45,000 per week and 6,000 per 5-hour rolling window. Those numbers matter less as bragging rights and more as behavior shaping.\u003C\u002Fp>\n\u003Cfigure class=\"my-6\">\u003Cimg src=\"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786435435287-sjsb.png\" alt=\"Coding Plan turns Alibaba Cloud into IDE billing\" class=\"rounded-xl w-full\" loading=\"lazy\" \u002F>\u003C\u002Ffigure>\n\u003Cp>What this actually means is that Alibaba Cloud is trying to prevent one person from torching the entire month in one weekend. The rolling 5-hour bucket is there to handle bursts. The weekly and monthly limits stop abuse and force some pacing. That is annoying if you want unlimited everything, but it is also why the plan can stay priced like a seat instead of a runaway usage meter.\u003C\u002Fp>\u003Cp>I have seen people underestimate this kind of quota because they only look at the monthly number. That is a mistake. If your workflow depends on a long debugging marathon, the rolling window can be more relevant than the monthly cap. If you are doing steady daily work, the monthly number matters more. If you are organizing a team, the weekly reset becomes the hidden constraint nobody planned for.\u003C\u002Fp>\u003Cp>How to apply it:\u003C\u002Fp>\u003Cul>\u003Cli>Map your real usage pattern: bursty, steady, or occasional.\u003C\u002Fli>\u003Cli>Check whether the 5-hour window will interrupt your longest sessions.\u003C\u002Fli>\u003Cli>Use the quota page in the plan dashboard before you commit to it.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>The model list is broad, but it is still a fenced garden\u003C\u002Fh2>\u003Cp>The source says the plan includes models from Qwen, Kimi, GLM, and MiniMax, with examples like qwen3.5-plus, qwen3-max-2026-01-23, qwen3-coder-plus, qwen3-coder-next, Kimi K2.5, and GLM 4.7. The important detail is not just that these are popular models. It is that the plan only supports the models inside the subscription list. If you try to call something outside that list, it errors.\u003C\u002Fp>\u003Cp>That is the tradeoff. You get a curated set of models that are already wrapped for coding workflows, but you do not get open-ended model selection like you would in a general API product. For a lot of developers, that is actually fine. Most of the time I do not need 47 models. I need three that behave predictably in my editor and do not make me babysit them.\u003C\u002Fp>\u003Cp>What this actually means is that the plan is less about model shopping and more about coding ergonomics. You are buying access to a stable set of options that work inside the tools you already use.\u003C\u002Fp>\u003Cp>How to apply it:\u003C\u002Fp>\u003Cul>\u003Cli>Check whether your favorite model is actually in the supported list before subscribing.\u003C\u002Fli>\u003Cli>Do not assume the model catalog matches the general Alibaba Cloud platform catalog.\u003C\u002Fli>\u003Cli>Pick the plan if your coding workflow values convenience more than model variety.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>The tool support is the reason this is interesting\u003C\u002Fh2>\u003Cp>The article lists a pretty wide tool ecosystem: Cursor, Cline, Lingma or Qoder CN, Qwen Code, Codex, Kilo CLI, \u003Ca href=\"\u002Ftag\u002Fopenclaw\">OpenClaw\u003C\u002Fa>, Hermes Agent, QwenPaw, OpenCode, Cherry Studio, and Chatbox. That is the real hook for me. A subscription is only useful if I can actually plug it into the tools I already have open all day.\u003C\u002Fp>\u003Cp>I have been burned by provider plans that technically support “integration” but only if I am willing to rewrite half my setup. This one is more practical. The post says the tools connect through a dedicated API key and a provider-specific base URL, and that the same key is not interchangeable with the standard pay-as-you-go setup. That is the kind of detail that saves you from a dumb afternoon.\u003C\u002Fp>\u003Cp>What this actually means is that the plan is not trying to be a universal cloud account. It is trying to be a coding identity inside a specific set of tools. That is a narrower promise, but it is easier to use.\u003C\u002Fp>\u003Cp>How to apply it:\u003C\u002Fp>\u003Cul>\u003Cli>Pick one primary tool first, then verify the connection flow there before spreading to others.\u003C\u002Fli>\u003Cli>Store the plan key separately from your general Alibaba Cloud keys.\u003C\u002Fli>\u003Cli>Document the base URL in your team notes so nobody pastes the wrong endpoint.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>The key and base URL split is where people shoot themselves in the foot\u003C\u002Fh2>\u003Cp>The source is very explicit here, and honestly I appreciate the bluntness. Coding Plan uses a dedicated API key format, described as different from the standard Alibaba Cloud key, plus a dedicated base URL. The post lists two URLs: the OpenAI-compatible endpoint at \u003Ca href=\"https:\u002F\u002Fcoding.dashscope.aliyuncs.com\u002Fv1\">coding.dashscope.aliyuncs.com\u002Fv1\u003C\u002Fa> and the Anthropic-compatible endpoint at \u003Ca href=\"https:\u002F\u002Fcoding.dashscope.aliyuncs.com\u002Fapps\u002Fanthropic\">coding.dashscope.aliyuncs.com\u002Fapps\u002Fanthropic\u003C\u002Fa>. It also warns not to mix the Coding Plan key and base URL with the regular billing system.\u003C\u002Fp>\u003Cp>What this actually means is that configuration hygiene matters more than usual. If you paste the wrong key into the wrong provider profile, it does not just fail gracefully. It may fail in a way that looks like a model outage, when the real issue is simply that you mixed two billing worlds that are not connected.\u003C\u002Fp>\u003Cp>I have seen this happen with IDE plugins more times than I care to admit. Someone copies a config snippet from one doc, changes one line, and assumes the rest is compatible. Then the tool throws a vague auth error and everyone wastes time blaming the network.\u003C\u002Fp>\u003Cp>How to apply it:\u003C\u002Fp>\u003Cul>\u003Cli>Label the key as “Coding Plan only” in your secret manager.\u003C\u002Fli>\u003Cli>Keep separate environment variables for standard API access and Coding Plan access.\u003C\u002Fli>\u003Cli>Match the protocol to the tool: OpenAI-compatible for OpenAI-style clients, Anthropic-compatible for Anthropic-style clients.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>When I would choose Coding Plan, and when I would not\u003C\u002Fh2>\u003Cp>The article draws a line between Coding Plan and Token Plan, and that line is actually useful. Coding Plan is for personal interactive coding. Token Plan is for team workflows, automation, production integrations, and broader enterprise use. That split is sane. I wish more vendors were this direct instead of pretending one pricing model fits every problem.\u003C\u002Fp>\u003Cp>If I am working solo, writing code, debugging, and iterating inside an editor, Coding Plan looks like the cleaner option. If I am building a service, coordinating a team, or running any kind of autonomous agent pipeline, I would rather use a plan that is designed for that reality instead of hoping a coding seat can stretch forever.\u003C\u002Fp>\u003Cp>What this actually means is that the right plan follows the shape of the work. Human-in-the-loop coding gets one bucket. Machine-driven integration gets another.\u003C\u002Fp>\u003Cp>How to apply it:\u003C\u002Fp>\u003Cul>\u003Cli>Choose Coding Plan for solo development, prototyping, and daily coding help.\u003C\u002Fli>\u003Cli>Choose Token Plan or another API-oriented plan for shared services and automation.\u003C\u002Fli>\u003Cli>Do not share a Coding Plan seat across multiple people or workflows just to save money.\u003C\u002Fli>\u003C\u002Ful>\u003Ch2>The template you can copy\u003C\u002Fh2>\u003Cpre>\u003Ccode># Alibaba Cloud Coding Plan setup notes\n\n## What this is for\nUse this plan only for interactive coding inside supported tools.\nDo not use it for backend automation, batch jobs, or production API services.\n\n## Supported endpoints\n- OpenAI-compatible: https:\u002F\u002Fcoding.dashscope.aliyuncs.com\u002Fv1\n- Anthropic-compatible: https:\u002F\u002Fcoding.dashscope.aliyuncs.com\u002Fapps\u002Fanthropic\n\n## Key handling rules\n- Keep the Coding Plan key separate from standard Alibaba Cloud API keys.\n- Do not mix the Coding Plan key with pay-as-you-go endpoints.\n- Store it in a secret manager as: CODING_PLAN_API_KEY\n\n## Suggested environment variables\nCODING_PLAN_API_KEY=sk-sp-xxxxx\nCODING_PLAN_BASE_URL=https:\u002F\u002Fcoding.dashscope.aliyuncs.com\u002Fv1\nCODING_PLAN_ANTHROPIC_BASE_URL=https:\u002F\u002Fcoding.dashscope.aliyuncs.com\u002Fapps\u002Fanthropic\n\n## Tool selection checklist\n1. Confirm the tool supports either OpenAI-compatible or Anthropic-compatible endpoints.\n2. Paste the correct base URL for that protocol.\n3. Test with a single interactive prompt.\n4. Verify usage stays within the 5-hour, weekly, and monthly limits.\n5. Keep all automated workloads on a different plan.\n\n## Decision rule\nUse Coding Plan if:\n- You are coding interactively in an IDE or CLI\n- You are working solo\n- You want fixed monthly pricing\n- You do not need backend automation\n\nUse a token-based team plan if:\n- Multiple people need access\n- You are integrating into a product or service\n- You need automation or batch execution\n- You need broader enterprise controls\n\n## Quick warning\nIf auth fails, first check:\n- wrong key\n- wrong endpoint\n- wrong protocol\n- mixing Coding Plan with standard Alibaba Cloud billing\n\u003C\u002Fcode>\u003C\u002Fpre>\u003Cp>The version above is my distilled read of the source, not a vendor doc. I kept the operational rules and stripped out the marketing fluff so you can drop it into your own notes, onboarding doc, or internal setup guide.\u003C\u002Fp>\u003Cp>Source attribution: the original article is on Zhihu at \u003Ca href=\"https:\u002F\u002Fzhuanlan.zhihu.com\u002Fp\u002F2061515864340444437\">https:\u002F\u002Fzhuanlan.zhihu.com\u002Fp\u002F2061515864340444437\u003C\u002Fa>. My breakdown is derivative, but the setup template and the way I frame the tradeoffs are mine.\u003C\u002Fp>","Alibaba Cloud's Coding Plan is a fixed-fee coding subscription with model access, tool support, and strict usage boundaries.","zhuanlan.zhihu.com","https:\u002F\u002Fzhuanlan.zhihu.com\u002Fp\u002F2061515864340444437",null,"https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786435438696-k107.png","tools","en","df203653-afe2-4c37-9d70-af6d94461423",[17,18,19,20,21],"Alibaba Cloud","Coding Plan","AI coding tools","API keys","subscription pricing",[23,24,25],"Coding Plan is a fixed-fee interactive coding subscription, not a general API backend.","The key and base URL are separate from Alibaba Cloud's pay-as-you-go system.","Use it for solo coding workflows; use a token-based plan for team or automated use.",1,"2026-08-11T08:03:27.598531+00:00","2026-08-11T08:03:27.591+00:00",{"tags":30,"relatedLang":33,"relatedPosts":37},[31],{"name":19,"slug":32},"ai-coding-tools",{"id":15,"slug":34,"title":35,"language":36},"coding-plan-bailian-developer-subscription-zh","Coding Plan把百炼变订阅","zh",[38,44,50,56,62,68],{"id":39,"slug":40,"title":41,"cover_image":42,"image_url":42,"created_at":43,"category":13},"c24a9808-1757-4971-9b9c-83c9be09b6bf","doubao-turns-game-prompt-into-mini-arcade-en","Doubao turns a game prompt into a mini arcade","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786437225143-b9yd.png","2026-08-11T08:33:17.825592+00:00",{"id":45,"slug":46,"title":47,"cover_image":48,"image_url":48,"created_at":49,"category":13},"d5ff5ff4-6bed-4820-8ce4-650d9a5a6eb5","baidu-wenxin-search-to-free-agent-en","Baidu Wenxin turns search into a free agent","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786365227346-puo3.png","2026-08-10T12:33:19.92436+00:00",{"id":51,"slug":52,"title":53,"cover_image":54,"image_url":54,"created_at":55,"category":13},"d5325d38-a48e-43b7-b373-2ecefff808cd","opcode-supports-deepseek-glm-qwen-gpt-models-en","OpenCode now supports DeepSeek, GLM, Qwen, GPT","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786363373903-d4u3.png","2026-08-10T12:02:30.602542+00:00",{"id":57,"slug":58,"title":59,"cover_image":60,"image_url":60,"created_at":61,"category":13},"0aab53f7-2569-4c05-93f1-9bed53def12b","deepseek-codex-ai-coding-costs-en","DeepSeek in Codex Will Cut AI Coding Costs Hard","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786321971893-69cj.png","2026-08-10T00:32:33.297704+00:00",{"id":63,"slug":64,"title":65,"cover_image":66,"image_url":66,"created_at":67,"category":13},"0d0d262b-65b7-4388-82e5-bab51244f9c0","token-vs-word-chinese-tokenization-matters-en","Token vs. word: why Chinese tokenization still matters","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786320173873-ptb3.png","2026-08-10T00:02:32.1747+00:00",{"id":69,"slug":70,"title":71,"cover_image":72,"image_url":72,"created_at":73,"category":13},"0eba42be-cb97-4711-9189-e7f4d0d9ffbe","openai-api-pricing-august-2026-token-costs-en","OpenAI API Pricing Hits $0.05 to $180\u002FM Tokens","https:\u002F\u002Fxxdpdyhzhpamafnrdkyq.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Fcovers\u002Finline-1786300371726-ccpx.png","2026-08-09T18:32:26.984366+00:00",[75,80,85,90,95,100,105,110,115,120],{"id":76,"slug":77,"title":78,"created_at":79},"8008f1a9-7a00-4bad-88c9-3eedc9c6b4b1","surepath-ai-mcp-policy-controls-en","SurePath AI's New MCP Policy Controls Enhance AI Security","2026-03-26T01:26:52.222015+00:00",{"id":81,"slug":82,"title":83,"created_at":84},"27e39a8f-b65d-4f7b-a875-859e2b210156","mcp-standard-ai-tools-2026-en","MCP Standard in 2026: Integrating AI Tools","2026-03-26T01:27:43.127519+00:00",{"id":86,"slug":87,"title":88,"created_at":89},"165f9a19-c92d-46ba-b3f0-7125f662921d","rag-2026-transforming-enterprise-ai-en","How RAG in 2026 is Transforming Enterprise AI","2026-03-26T01:28:11.485236+00:00",{"id":91,"slug":92,"title":93,"created_at":94},"6a2a8e6e-b956-49d8-be12-cc47bdc132b2","mastering-ai-prompts-2026-guide-en","Mastering AI Prompts: A 2026 Guide for Developers","2026-03-26T01:29:07.835148+00:00",{"id":96,"slug":97,"title":98,"created_at":99},"3ab2c67e-4664-4c67-a013-687a2f605814","garry-tan-open-sources-claude-code-toolkit-en","Garry Tan Open-Sources a Claude Code Toolkit","2026-03-26T08:26:20.245934+00:00",{"id":101,"slug":102,"title":103,"created_at":104},"66a7cbf8-7e76-41d4-9bbf-eaca9761bf69","github-ai-projects-to-watch-in-2026-en","20 GitHub AI Projects to Watch in 2026","2026-03-26T08:28:09.752027+00:00",{"id":106,"slug":107,"title":108,"created_at":109},"9f332fda-eace-448a-a292-2283951eee71","practical-github-guide-learning-ml-2026-en","A Practical GitHub Guide to Learning ML in 2026","2026-03-27T01:16:50.125678+00:00",{"id":111,"slug":112,"title":113,"created_at":114},"1b1f637d-0f4d-42bd-974b-07b53829144d","aiml-2026-student-ai-ml-lab-repo-review-en","AIML-2026 Is a Bare-Bones Student Lab Repo","2026-03-27T01:21:51.661231+00:00",{"id":116,"slug":117,"title":118,"created_at":119},"6d1bf3f6-e191-4d30-b55b-8a0722fa6afe","ai-trending-github-repos-and-research-feeds-en","AI Trending Tracks Repos and Research Feeds","2026-03-27T01:31:35.709532+00:00",{"id":121,"slug":122,"title":123,"created_at":124},"010539a1-4c3a-4bd3-937a-26616422ee0d","awesome-ai-for-science-research-tools-map-en","Awesome AI for Science Is Becoming a Real Research Map","2026-03-27T01:46:50.89513+00:00"]