Agent platform teams
- Boundary enforcement without threading region state through the framework
- Deterministic refusals instead of unpredictable fallbacks
An agent is a sequence of decisions. Any hop can cross a border. The router must hold the boundary for the full run, including tool calls your framework makes for you.
Survives the full trajectory
The problem
A run that starts in-region can hand off to a summarisation or search step outside the boundary.
Tool definitions and retrieved context are resent on every hop, making each hop a new transfer decision.
Retry logic may favour a successful request over one that stays in place.
The approach
Jurisdiction is bound to the session or key. Every hop inherits the boundary without the framework passing it along.
Unsupported hops return a specific error and are not retried elsewhere.
Trajectory-level records show every region a run touched.
Models for this workload
| Model | Provider | Context | Input, per 1M | Regions | Residency |
|---|---|---|---|---|---|
| Kimi K3 | Moonshot AI (Kimi) | 1.05M | $3.00 | cn-beijing · cn-hongkong | In region |
| DeepSeek V4 Pro | DeepSeek | 1M | $0.3 | CN · cn-beijing | In region |
Who this is for
Other solutions
01
Retrieval for data that must stay in the country
02
Images, audio and video under text's rules
04
Second waveCompletions and refactors without exporting the repository
05
Second waveStreaming assistants with residency that holds under load
06
Second waveRanking and reranking inside the same boundary as model output
Describe a different workload
Start