# Cost Related Articles

HTX News Center provides the latest articles and in-depth analysis on "Cost", covering market trends, project updates, tech developments, and regulatory policies in the crypto industry.

3 People with 100 AI Programmers, Burning Through $1.3 Million a Month! OpenAI: I'll Foot the Bill

In a striking demonstration of AI-powered development, Peter Steinberger (creator of OpenClaw) shared that his three-person team spent $1.3 million in one month to run approximately 100 AI agents (primarily Codex instances). OpenAI covered the cost. The expenditure consumed 6.03 trillion tokens across 7.6 million requests. Steinberger argues that, with "fast mode" disabled, the cost falls below that of a single engineer while providing significantly greater output. This "cloud programmer army" handles core but tedious software engineering tasks: reviewing pull requests, finding security vulnerabilities, deduplicating issues, fixing bugs, monitoring benchmarks, and even generating PRs after meetings. This shifts AI's role from merely writing code to maintaining the entire collaborative fabric of a project. Steinberger's tool, CodexBar (a macOS menu bar app), tracks usage and costs across various AI coding services, highlighting how token consumption is becoming a key metric—a new "means of production." The experiment poses a profound question: if token cost ceases to be a barrier, how will software development transform? As model prices fall, the capability for small teams to leverage large numbers of AI agents could become commonplace, fundamentally altering the scale and speed of development. The future, Steinberger suggests, is arriving rapidly.

marsbit05/17 06:20

3 People with 100 AI Programmers, Burning Through $1.3 Million a Month! OpenAI: I'll Foot the Bill

marsbit05/17 06:20

The Essence of AI Layoffs: Why More AI Adoption Leads to More Corporate Anxiety?

The author, awaiting potential inclusion on an 8000-person layoff list, analyzes the true nature of recent "AI-driven" layoffs. They argue that while AI use, particularly tools like Claude for code generation, has skyrocketed and boosted developer output (e.g., 2-5x more code commits), this has not translated into proportional business growth or revenue. The core issue is a misalignment between increased "Input" (code) and tangible "Outcomes" (user value, revenue). AI acts as a costly B2B SaaS, inflating operational expenses without guaranteed returns. Two key problems emerge: 1) The friction that once filtered out bad ideas is gone, as AI allows cheap pursuit of even weak concepts. 2) Organizational "alignment tax"—the difficulty of coordinating across teams—becomes crippling when development velocity outpaces consensus-building. Thus, layoffs serve two immediate purposes: 1) To offset ballooning AI costs (Token consumption) and maintain cash flow, as rising input costs without outcome growth destroys unit economics. 2) To reduce organizational bloat and alignment friction by simply removing teams, thereby speeding up execution in the short term. Therefore, these layoffs are fundamentally caused by AI, even if AI doesn't directly replace roles. They represent a painful correction until companies learn to convert AI-driven productivity into real business outcomes and streamline organizational coordination to match the new pace of work. The cycle will continue until this learning curve is mastered.

marsbit05/12 10:23

The Essence of AI Layoffs: Why More AI Adoption Leads to More Corporate Anxiety?

marsbit05/12 10:23

AI Relay Stations: The Hidden Pitfalls Behind Low Costs, How to Screen and Avoid Them?

AI Relay Stations: The Hidden Risks Behind Low Costs and How to Avoid Pitfalls AI relay stations are becoming a popular gateway to various models, offering lower prices, a wider selection, and a unified interface for tools like Claude Code and Cursor. However, their appeal masks significant risks. Users may unknowingly surrender prompts, code, business documents, customer data, and even full project contexts. The demand is driven by genuine needs: cost savings compared to expensive official APIs (e.g., GPT, Claude), easier access amid regional restrictions, and the push from AI-powered development tools. But not everyone needs a relay station. Light users should exhaust free official quotas first. Heavy users, like developers, can adopt a layered approach, using top models for critical tasks and cheaper local models for routine work. If a relay station is necessary, follow a careful selection and usage protocol: 1. **Verify First:** Test model authenticity, latency, and stability before purchasing credits. Check the quality of provided documentation. 2. **Isolate Configuration:** Use unique API keys for each service, manage them via environment variables, and set usage limits to control costs and potential damage from leaks. 3. **Classify Your Data:** Develop a habit of data grading before sending requests. Only send non-sensitive, public information directly. Desensitize semi-sensitive data (e.g., internal documents) by removing names and specifics. Never send highly sensitive data like passwords, private keys, or confidential customer information. 4. **Handle AI Coding Tools Separately:** Tools like Cursor can send extensive project context (file contents, directory structures, error logs). Use relay stations only for independent, non-core code tasks. For sensitive projects, switch back to official APIs or local models. 5. **Monitor and Prepare an Exit:** Regularly check billing statements, follow platform updates and community feedback, and always have a backup provider. Ensure your setup uses standard OpenAI-compatible APIs for easy migration. Ultimately, relay stations are tools, not default solutions. Their value lies in solving access needs at a controlled cost, but maintaining that control requires proactive risk management through verification, isolation, data classification, and continuous monitoring.

marsbit05/09 10:16

AI Relay Stations: The Hidden Pitfalls Behind Low Costs, How to Screen and Avoid Them?

marsbit05/09 10:16

AI Giants Enter the Dark Forest

In the AI industry's "dark forest," major players like Anthropic, OpenAI, and DeepSeek are strategically withholding their most advanced models to avoid becoming targets in a high-stakes competitive landscape. Anthropic released Claude Opus 4.7 but admitted it underperforms compared to their unreleased model Mythos, citing safety concerns. They delayed addressing user complaints about performance regression until OpenAI’s GPT-5.5 launch, highlighting a tactic of controlled disclosure aligned with competitors’ moves. OpenAI’s GPT-5.5, though a full retrain since GPT-4.5, was seen as incremental rather than revolutionary. Leaks revealed internal models like Glacier and Heisenberg, indicating significant unreleased capabilities. OpenAI acknowledges a "capability overhang," where real model power exceeds what users experience, often due to infrastructure-driven throttling. DeepSeek launched V4 Preview, a cost-efficient model, but its full potential (V4 Pro Max) awaits Huawei’s Ascend 950 super-nodes量产 in late 2026. Their strategy focuses on affordability and scalability, aiming to democratize AI access globally, a move noted even by NVIDIA’s CEO as a disruptive threat. Together, these actions reflect a broader trend: leading AI labs are deliberately pacing releases, hiding strengths, and aligning disclosures with competitive dynamics—each avoiding the risk of exposure in a forest where first movers become targets.

marsbit04/25 12:47

AI Giants Enter the Dark Forest

marsbit04/25 12:47

The Last Time I'll Talk About Backpack, and Also Discussing My Airdrop Farming Principles

The author outlines two primary approaches to airdrop farming (referred to as "撸毛"): a labor-intensive" method of mass participation in many projects, and their own "sniper" method. The sniper approach relies on a rigorous four-point checklist to filter projects and avoid "industrial garbage." The checklist evaluates: 1. **Team (People):** Founders must be intelligent, have strong execution skills, and be genuinely well-intentioned. This is assessed through their social media content and, if possible, personal interactions. 2. **Product (Product-Market Fit):** The product must have a clear market fit, be delivered competently, and the team must show a responsible attitude towards its quality, avoiding releases full of basic errors. 3. **Narrative (Story):** The project should operate in a promising, unproven narrative within Web3 that also aligns with major investment trends in Web2 (e.g., AI). 4. **Timing & Cost (Market Conditions):** Avoid participating when market sentiment is overly FOMO-driven and participation costs are high. If an opportunity causes hesitation, it's best to skip it, as overcrowded airdrops yield minimal or negative returns. Applying this framework, the author explains why they avoided heavily farming the Backpack exchange airdrop: * **Narrative:** They are skeptical of the "compliant CEX" narrative, questioning its unique selling point against giants like Binance and OKX. * **Product:** They criticize Backpack's frequent technical failures, rollbacks, and what they perceive as a lack of product development rigor, comparing it unfavorably to competitors like Hyperliquid. * **Timing & Cost:** The participation cost was high compared to zero-fee alternatives available at the time. The author concludes that Backpack lacks the technical and operational prowess of a serious exchange and views its token more as a "VC-backed meme coin" for secondary market speculation rather than a worthwhile airdrop target.

比推03/23 20:38

The Last Time I'll Talk About Backpack, and Also Discussing My Airdrop Farming Principles

比推03/23 20:38

活动图片