Product scope · Prelaunch
A model router.
A defined boundary.
Boundary is a prelaunch commercial model API router from OraXLabs. The security handbook covers general agent security; reading a guide does not mean Boundary currently implements the controls it explains.
What is planned
For model requests sent through the router, the planned scope includes defined sensitive-data pattern checks, model and provider policies, API usage limits, and policy decision metadata. Supported APIs, integration details, availability, pricing, and final behavior will be confirmed before launch. These are plans, not a live enforcement API.
What the demonstration actually does
The current agent-action prototype evaluates fabricated requests against a small client-side policy and simulates approval of one exact action. It uses synthetic paths, example recipients, and defined fake secret markers. It never reads or deletes a real file, runs a shell command, sends a message, takes payment, or calls a model.
The prototype is an educational simulation. Browser JavaScript and a simulated approval button are not trusted production enforcement. Lexical path checks do not resolve real filesystem paths or symlinks. A canonical request fingerprint is serialization, not an authentication credential.
What the router does not cover
A model request route does not automatically control an agent’s file access, shell or tool execution, deletion, external messages, or payments. It cannot enforce a policy on requests that bypass it. Pattern checks do not recognize every secret, personal detail, encoding, or semantic disclosure. We do not promise complete protection or complete prompt-injection detection.
Registration is not product access
Existing product pages may offer an interest or beta list. A registration records interest; it is not model API runtime access, a security pilot, a verified email address, a paid subscription, or an agreement to terms that have not been set.
Existing product page
The earlier Boundary security router page remains available for its existing context. Its links and history are preserved.
Contact OraXLabs
For product questions, email [email protected]. Describe your workflow without sending credentials, customer data, private logs, or production access.
Read the security handbook