AI agent infrastructure cost: are your tool calls the real margin leak?

TL;DR: The largest AI agent infrastructure cost is often not model spend but repeated calls to managed SaaS, search, scraping and hosted storage services, where agent loops turn human-priced APIs into a margin drain, according to Archestra. The real control problem is governing downstream usage, not just watching token meters.

Editorial analysis by NHI Mgmt Group, based on content published by Archestra: “When the LLM is not the expensive part”.

Key questions

Q: How should teams control AI agent costs when tool calls matter more than token usage?

A: Treat every external call as part of the agent’s cost envelope.

Q: Why do AI agents create unpredictable SaaS and API spend?

A: Because agents do not behave like humans.

Q: What are the warning signs that agent economics are getting out of control?

A: Look for flat token spend paired with rising external service bills, higher retry counts, frequent cache misses and more calls per task over time.

Practitioner guidance

• Map every downstream service call Inventory each external dependency an agent can invoke, including search, scraping, transcription and retrieval, then classify which calls are required, optional or duplicative.
• Set hard usage guardrails Apply per-task and per-session limits on retries, query fan-out and call volume so the agent cannot turn one request into uncontrolled service consumption.
• Introduce caching for repeated lookups Cache normalised retrieval results and common search outputs so the same content is not purchased repeatedly within a single workflow or across similar sessions.

Bottom line: The article’s central point is that AI agent cost often comes from repeated external service usage, not from the model itself.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →