Posted on Leave a comment

Claude Agent SDK credits: what Pro and Max users actually get

Aitoque AI cost brief

Claude adds Agent SDK credits

Programmatic agent usage gets a separate monthly credit pool.

Pro $20 creditMax up to $200No rollover
$
Plan cost is now usage cost

Claude is separating agent-style usage from ordinary chat limits, which helps small automations but still requires buyers to watch monthly credit caps.

What changed

Anthropic says that starting June 15, 2026, Claude Agent SDK and non-interactive claude -p usage will no longer count against regular Claude subscription usage limits. Instead, eligible Pro, Max, Team, and Enterprise users can claim a separate monthly Agent SDK credit.

The published monthly credits include $20 for Pro, $100 for Max 5x, and $200 for Max 20x. Anthropic also says the credit is per user, refreshes monthly, and unused credit does not roll over.

Why it matters for buyers

This is good for people testing small agent workflows, but it is not the same as unlimited API access. The credit applies to Agent SDK usage, claude -p, Claude Code GitHub Actions, and supported third-party apps that authenticate through the Agent SDK. Interactive Claude chat and Claude Code in the terminal continue to use normal subscription limits.

Good fit
Small scripts, test agents, low-volume automations.
Watch out
Credits are per user and do not pool across teammates.
Budget rule
If extra usage is off, requests stop when the credit runs out.

Aitoque take

For buyers, the key question is whether you need Claude for chat, coding in the IDE, or automated agent runs. These now map to different limit pools. Choose the plan around the workflow, not only the model name.

Source: Anthropic Claude Agent SDK credit help.

Posted on Leave a comment

GitHub Copilot AI Credits: why coding subscriptions are becoming usage-based

Aitoque AI cost brief

Copilot billing shifts to AI Credits

Agentic coding work can cost differently from simple completions.

June 1 change1 credit = $0.01Code review adds Actions
$
Plan cost is now usage cost

GitHub Copilot billing is moving closer to API-style usage, making model choice, prompt size, and agentic workflows more important to total cost.

What changed

GitHub is moving Copilot billing from request-based usage to GitHub AI Credits on June 1, 2026. GitHub says interactions consume input, output, and cached tokens, then convert that usage into credits. One AI Credit equals $0.01 USD.

Simple code completions and next edit suggestions remain outside AI Credit billing for paid plans, but advanced chat, model choice, agentic work, and code review can behave differently. Copilot code review is especially important because it can consume both AI Credits and GitHub Actions minutes.

Why it matters for buyers

The old mental model was easy: buy a plan, watch request counts. The new model is closer to API spending: model choice, prompt length, cached context, and long-running agent work all affect cost.

Cost checklist before upgrading

  • Check whether your work is mostly completion, chat, or agentic coding.
  • Watch expensive model usage instead of only counting prompts.
  • For teams, set paid usage policy and budgets before June 1.

Aitoque take

Copilot is still useful, but users who only need occasional coding help should not assume a higher plan automatically means better value. If your usage is light, a cheaper or short-term access route may be enough. If your usage is agent-heavy, budget controls matter as much as the subscription price.

Sources: GitHub Copilot models and pricing, GitHub request allowance management.

Posted on Leave a comment

Google AI Pro and Ultra: what the new compute limits mean for subscription buyers

Aitoque AI cost brief

Google AI plans move toward compute limits

Pro and Ultra users now need to watch credits, not only plan names.

AI Ultra $100Compute-used limitsTop-up credits
$
Plan cost is now usage cost

Google AI subscriptions now require buyers to think in usage limits, credits, and agent workflows, not just monthly plan names.

What changed

Google used I/O 2026 to reposition AI subscriptions around higher usage tiers and compute-aware limits. The headline is a new $100 Google AI Ultra plan. Google also says AI Ultra gives higher usage limits in Gemini and Google Antigravity, while Pro and Ultra members can buy top-up AI credits for tools such as Antigravity and Flow.

Jules, Google’s asynchronous coding agent, is also out of public beta. Google says Jules gets higher limits under Google AI Pro and Ultra, with Ultra aimed at heavier multi-agent workflows.

Why it matters for buyers

The practical change is simple: the plan name alone is no longer enough. A buyer should check the specific quota, the refresh window, whether credits are shared, and what happens after a cap is reached. Heavy coding, video, or agent tasks can consume more than ordinary chat.

Light users
Prioritize stable Pro access and avoid overbuying Ultra.
Creators
Check Flow, video, and credit top-up rules before choosing.
Developers
Jules and Antigravity limits matter more than storage perks.

Aitoque take

If you only need occasional Gemini access, look for the lowest reliable access path first. If your workflow depends on agents, coding tasks, or video generation, compare the real usage cap before paying for a higher tier.

Sources: Google AI subscription update, Google Jules announcement, Google One AI credits help.

Posted on Leave a comment

xMemory: The Research That Cuts AI Agent Token Costs by 50% — Without Losing Accuracy

AI Memory Neural Network
9,000+
tokens per query
BEFORE xMemory
~4,700
tokens per query
AFTER xMemory
~50% Token Reduction + Improved Accuracy
The only memory system that saves money AND makes AI smarter

The Problem: Why Standard RAG Fails AI Agents

Standard RAG was built for large document databases with highly diverse content. AI agents have something much harder: a continuous, correlated stream of conversation where chunks are near-duplicates of each other.

The citrus fruit problem: A user said “I love oranges,” “I like mandarins,” and separately discussed what counts as citrus. Standard RAG treats all as semantically close — and retrieves 10 copies of “citrus preference” while missing the actual category facts needed to answer the query. The agent starves for context it already has.

Why Existing Fixes Make It Worse

Engineering teams typically reach for post-retrieval pruning or compression — filtering out noise after retrieval. Sounds reasonable. But this fails for AI agents because human dialogue is “temporally entangled”:

  • • Co-references: “it” and “that” link to earlier context
  • • Ellipsis: missing words that only make sense given prior sentences
  • • Timeline dependencies: facts that only matter in sequence

Pruning tools accidentally delete vital conversation fragments. The AI loses the thread. Answers become incoherent. You paid for those tokens and got nothing.

xMemory: A 4-Level Memory Hierarchy

Researchers at King’s College London and The Alan Turing Institute built xMemory — a framework that organizes conversation into a searchable semantic hierarchy instead of dumping everything into context.

4
Theme Level
High-level topics and categories — search starts here
3
Semantic Level
Distilled reusable facts — core knowledge, no repetition
2
Episode Level
Contiguous summarized blocks of conversation
1
Raw Messages
The original conversation stream

The Key Innovation: Uncertainty Gating

💡 Semantic similarity is a candidate-generation signal.
Uncertainty is a decision signal.

— Lin Gui, Co-author, King’s College London

Traditional systems retrieve based on similarity alone. xMemory adds a second gate: uncertainty. After finding candidates, it asks: “Does adding this actually reduce my uncertainty about the answer?” If no, it stops. This is why xMemory achieves better accuracy with fewer tokens.

Similarity tells you what is nearby. Uncertainty tells you what is actually worth paying for in the prompt budget.

xMemory vs The Alternatives

System Structure Redundancy Accuracy Cost
Flat RAG (MemGPT) Raw logs High Drops High
Structured RAG (A-MEM) Hierarchy/Graph Medium Moderate Medium
xMemory ⭐ 4-Level + Uncertainty Gate Low Improves -50%

What This Means for Coding Agents

For AI coding agents running multi-session workflows, xMemory is directly applicable:

  • ✅ Agent can maintain coherent project memory across hours or days of work without blowing up context
  • ✅ Relevant code decisions from earlier sessions are retrieved without re-injecting full history
  • ✅ Fewer tokens per query = lower API bills + faster responses
  • ✅ Better accuracy because irrelevant conversation is structurally excluded, not just pruned

Stop paying for tokens you do not need.

The future of AI memory is not bigger context windows — it is smarter retrieval. xMemory proves you can have both: less cost AND better answers.


Research: xMemory (arXiv:2602.02007) — King’s College London & The Alan Turing Institute | Via VentureBeat
Tags: #xMemory #AIResearch #TokenOptimization #CodingAgent #RAG #LLMMemory #FinOps #AI

Posted on Leave a comment

The Hidden Cost of AI Coding: Why Your Agent Is Burning $30 Per Session

AI Coding Cost
$15,000
Cost of 8 months of daily Claude Code usage — 10 BILLION tokens consumed

Every AI Coding Tool Has Two Prices

There is the marketing price — $20/month, $100/month, free tier. And there is the real price: token consumption, API overages, agent loops that burn through context, and the three other AI subscriptions you are also paying for.

70%
of coding agent tokens are pure waste
$20-40
Daily cost of heavy Claude Code usage
40-70%
Cost reduction with routing + compaction

Where the Money Actually Goes

A coding agent does not just generate code. It reads files, searches codebases, runs commands, reads the output, reasons about what to do next — and then generates code. The code generation is the cheap part. Everything else is the expensive part.

Activity % of Tokens Cost Driver
File Reading & Code Search 35-45% Agent reads entire files when it only needs one function
Tool/Command Output 15-25% 60 commands at 3,500 tokens each = 210K tokens of noise
Context Re-sending 15-20% Full conversation history resent on every API call — grows linearly
Reasoning & Planning 10-15% Agent thinking — necessary but compounds with context size
Code Generation 5-15% The part you actually want — cheapest line item

The Compounding Disaster

At turn 1, the agent sends the system prompt + your request
= 5K tokens

At turn 50, the agent sends the full conversation history
= 200K tokens

40x cost increase — paying for the SAME tokens over and over

The Agent Loop Tax

When a coding agent gets stuck, it does not stop. It loops. It tries one approach, fails, tries a variation, fails again, backs up, tries something else. Each iteration adds tokens to the context. The context grows. The next iteration costs more. The agent cannot tell it is stuck because it lacks self-awareness to recognize circular reasoning.

Real data: 70% of coding agent tokens are pure waste. A developer on DEV Community tracked every token across 42 agent runs on a FastAPI codebase. The agent read too many files, explored irrelevant code paths, and repeated searches it had already done — over and over.

The Fix: Smart Routing + Context Compaction

⚡ Smart Model Routing

Use Sonnet/Haiku for simple tasks. Reserve Opus for complex reasoning only. A coding agent making 200 API calls: mixed model = $1-5/session. All Opus = $15-30/session. Same output quality, 6x cheaper.

🔄 Context Compaction

Replace long conversation history with a concise summary when context approaches limits. Keep key decisions + task state. Discard full history. xMemory research: 50% token reduction + improved accuracy. Context compaction can achieve 70-94% cost savings in production.

How to Cut 40-70% of Your AI Coding Cost

  • Route simple tasks to Haiku/Sonnet — save Opus for complex reasoning only
  • Enable automatic compaction — summarize history before it compounds
  • Use MCP (Model Context Protocol) for targeted retrieval instead of full file reads
  • Set command output limits — truncate verbose CLI results before they hit context
  • Trim AGENTS.md — over-instruction can increase cost by 20%+ with minimal benefit
  • Store large docs in vector DB — retrieve only relevant chunks instead of inlining everything

The agent is not the cost. The context is the cost.

Every token you save from context bloat is pure margin. Start measuring context per task, not just model selection.


Sources: MorphLLM AI Coding Costs Report 2026, DEV Community, Augment Code, VentureBeat xMemory, MindStudio, CloudZero
Tags: #AICoding #TokenCost #CodingAgent #Claude #LLMOptimization #FinOps