Why it matters
Many organisations approve AI agents on condition that traffic goes through a particular route: a cloud provider in a chosen region, or an internal gateway. Whether that holds in practice is hard to see from the platform side, because work that goes elsewhere doesn't show up there.
How Ascenda helps
Flow reads, on each engineer's Mac, which model vendor each session used and how it was served: direct, through a cloud provider (Bedrock, Vertex, Azure), a gateway, a custom endpoint, or on device. The organisation declares its approved vendors or routes, and Ascenda reports the share of the cohort's agent time that went through them.
- Route is a category, never a hostname or a country.
- The figure is an aggregate of ten or more, with no individual view.
- Route is read from Claude Code and Codex; vendor also from Cursor and Windsurf.
What else you'd need
Your gateway or cloud provider logs show the traffic that reached the approved route. Ascenda adds the engineer's side: the share of all agent work that went through it, including work that went elsewhere.