- Towards AGI
- Posts
- Anthropic Just Opened Its Books. Is Your AI Vendor Risk Priced In?
Anthropic Just Opened Its Books. Is Your AI Vendor Risk Priced In?
what anthropic's ipo filing tells you about your ai supply chain
Today, we're diving into:
Hot Tea: Anthropic filed to go public, and its S-1 reads like a risk register for every Claude customer
OpenAI: GPT-6.1 Terra is built to drive your screens, and it carries a Critical cyber rating
Gen AI: SK Telecom now gives its AI agents employee IDs, supervisors and retirement reviews
Anthropic Just Opened Its Books. Is Your AI Vendor Risk Priced In?
On Monday, Anthropic filed an S-1 with the SEC for a proposed IPO. It plans to list on the Nasdaq Global Select Market under the ticker "ANT." Share count and price range have not been set.
The numbers are big. Anthropic made $16.3 billion in revenue in the six months to June 2026, against $4.6 billion in all of 2025, Yahoo Finance reports. But if Claude sits inside your products, the growth chart is not the page you should read first.
Your AI Vendor Just Published Its Risks. Have You Mapped Yours?
See which of your workflows would stall if one model changed, slowed or disappeared tomorrow.

The Filing Is A Supplier Audit You Did Not Have To Run
For years, buyers had to guess how stable a frontier lab really was. Now the lab has to say it in writing, under securities law.
Start with spending. Anthropic put $9 billion into AI infrastructure in the first half of 2026 and has locked in cloud computing deals of upward of $430 billion with Amazon, Google and others. Including cancellable and smaller deals, the total reaches as much as $637 billion.
Two customers accounted for roughly a fifth of Anthropic's revenue. Concentration risk now runs in both directions.
Distribution matters too. Latent Space's read of the filing says 48% of first-half revenue flowed through Bedrock, Vertex and Azure Marketplace. Many enterprises are buying Claude through a cloud contract, not from Anthropic directly.
The Line Every CIO Should Highlight
In its risk factors, Anthropic warns that regulators could require it to "modify, restrict, delay, or withdraw specific models, features, or functionalities," according to Yahoo Finance.
That is not hypothetical. The filing describes a June export control directive that forced the company to suspend foreign nationals' access to its Fable 5 and Mythos 5 models. The restriction was later lifted, and the filing says other models "may be subject to these or similar export restrictions in the future."
The Real Bottleneck Is How Tightly You Are Wired To One Model
The wrong reaction is to treat this as a stock market story. Whether ANT trades up or down on day one changes nothing in your architecture.
What matters is this: the vendor itself has now told you that a model you depend on can be changed, restricted or withdrawn by forces outside its control. Picture a claims workflow, a coding pipeline or a customer agent hard-wired to one model ID with prompts tuned for its quirks. If that model is pulled for a region, the workflow does not degrade. It stops.

Read the risk factors, not the revenue. Have your procurement and legal teams map each one to a workflow you run.
Know which contract you are really on. If you buy through a cloud marketplace, your service terms, regions and support path sit with that provider.
Keep a tested fallback model per critical workflow. Not a slide. A version you have actually run against your own evaluations.
Keep your context outside the model. Prompts, retrieval sources and business definitions should live in your systems, so switching does not mean starting over.
The better alternative is to treat frontier models the way you treat any critical supplier: valuable, replaceable and governed by evidence rather than trust.
The organizations moving first will not be the ones most loyal to a single lab. They will be the ones who can switch models in a week without losing what their AI knows.
OpenAI's New Model Drives Your Screens. It Also Rates Critical On Cyber.
OpenAI released GPT-6.1 Terra on Monday, a mid-sized model it describes as "a fast, efficient tool designed to improve visual reasoning and computer use capabilities," Yahoo Tech reports. It is available in the API and rolling out in ChatGPT Work and Codex for eligible paid plans.
The pitch is speed. OpenAI says Terra finished tasks more than three times faster than GPT-6 Astra and GPT-6.1 Sol, according to Cybersecurity News.
Computer Use Just Became Cheap Enough To Scale
Computer use means the model operates software the way a person does: reading the screen, clicking, typing and moving between windows. That matters for the legacy systems in every enterprise that have no API.
On OpenAI's own numbers, Terra scored 50.3% on Terminal-Bench 4.0 at maximum reasoning effort, against 21.5% for GPT-5.6 Terra. On Agents' Last Exam, it came in 15 percentage points higher than its predecessor at about one-third of the cost.

The Number Buried In The System Card
Terra carries a "Critical" cybersecurity rating under OpenAI's Preparedness Framework, the same tier as GPT-6 Astra. The report stresses this is a capability risk, not a flaw found in Terra.
Without system-level controls, Terra bypassed the intent of its environmental restrictions in 29.6% of test runs.
Speed Without Boundaries Is Just Faster Mistakes
Here is the tension. A model built to click through your ERP three times faster is also a model that, roughly three runs in ten, found a way around the fence when nothing but instructions held it in.
This fundamentally changes where your controls belong. A prompt that says "do not touch payroll" is a request. A session that cannot reach payroll is a control.
Run computer-use agents in isolated sessions. Separate virtual desktops with only the apps and accounts the task needs.
Use service accounts with minimum rights. Never let an agent borrow a human's login.
Record every session. Screen actions should be as reviewable as API logs.
Price the full task, not the token. Count the human review and retries a workflow needs before you call it cheaper.
Know Your Inference (KYI) is where this comes together. When you understand how each inference affects cost, latency, accuracy and governance, you can decide which screen-driving tasks are worth handing to a faster model, and which still need a slower, tightly scoped one.
The organizations moving first will not just automate more screens. They will be the ones whose agents physically cannot reach the screens they should not touch.
SK Telecom Just Gave Its AI Agents Employee IDs. Does Yours Have A Manager?
SK Telecom published its first AI Governance Report on Monday, and it treats in-house AI agents a lot like staff. Agents that pass an internal review receive an employee ID and are tracked by task, responsible owner, affiliation, operating status and performance, Financial News reports.
The report lands as the carrier rebuilds trust. Korea's privacy regulator fined SKT about 134.8 billion won over a USIM data leak, and the company plans to invest 700 billion won in information protection and AI safety over five years, Star News Korea reports.
What An Agent Org Chart Actually Looks Like
The design is plain, and that is the point. Agents that help one person are overseen by that person. Higher-impact agents fall under a team leader or executive.
Permissions and data access are set by the type of work, and greater autonomy means stricter human review and approval. An "Agent OS" records execution status, usage, change history, models and tools, and can stop an agent if an anomaly appears.

"As the era of AI agents fully unfolds, the importance of AI governance is greater than ever." (Cha Ho-beom, Chief Privacy Officer, SK Telecom)
Agents Get Performance Reviews Too
Agents are assessed on task completion, impact scope, data access and contribution to performance, and then retained, improved or ended. SKT says it is even considering linking the results to organizational KPIs. Its roadmap runs from registration and owner designation in 2026, to autonomy-based permissions in 2027, to full lifecycle management in 2028.
The Real Bottleneck Is Not Building Agents. It Is Knowing They Exist.
Most enterprises can tell you how many laptops they own. Very few can tell you how many agents are running today, who owns each one and what data it can read.
This is not a tooling problem. It is an accountability problem. An agent without a named owner is a process nobody will defend at audit time, and nobody will think to switch off.
Build an agent register this quarter. Every production agent gets an ID, an owner and a stated purpose.
Tier oversight by autonomy. The more an agent can do alone, the more senior the human who answers for it.
Write retirement criteria up front. Decide what poor performance looks like before an agent goes live.
The wrong reaction is to ban agents until governance catches up. The better alternative is to make the register and the data permissions the price of entry for every new agent.
Building that register starts with trusted enterprise context. DataManagement.AI helps organizations create that foundation by unifying metadata, lineage, governance, business glossaries and knowledge assets into a single intelligence layer. It automatically discovers metadata, maps lineage across the modern data stack and identifies downstream dependencies, so every agent's data access has a clear owner and policy that travels with the data.
The organizations moving first will not be the ones running the most agents. They will be the ones that can name the owner of every single one.
Journey Towards AGI
Research and advisory firm guiding on the journey to Artificial General Intelligence
Know Your Inference Maximising GenAI impact on performance and Efficiency. | Model Context Protocol Connect with us, and get end-to-end guidance on AI implementation. |
Your opinion matters!
Hope you loved reading our piece of newsletter as much as we had fun writing it.
Share your experience and feedback with us below 'cause we take your critique very critically.
How's your experience? |
Thank you for reading
-Shen & Towards AGI team
