Boundaryby OraXLabs

Start here · Synthetic data only

One task.
One visible result.

Use the browser demonstration to inspect a proposed agent action and see the mock policy’s answer. It takes no production access, customer data, API key, or model connection.

Open the synthetic check

A 20-minute walkthrough

  1. Choose one question. For example: should deleting a synthetic CSV export require approval? Write down the allowed resource and the stop condition before evaluating.
  2. Inspect the exact request. In the demonstration, choose “Remove one synthetic CSV export.” Confirm the tool and path use only the supplied fabricated data.
  3. Predict, then evaluate. The first evaluation should request human approval. Simulating approval permits the exact action once inside the mock; no deletion happens. Evaluate again and see approval required again.
  4. Change the consequence. Select the protected-file scenario. The request should be denied. A request outside the fixed policy cannot be made permissible by changing the instruction text.
  5. Record the result and next step. Keep only the synthetic scenario, expected decision, observed decision, and question left open. Compare with the published test evidence.

Assisted or asynchronous

If you want to discuss a walkthrough, email [email protected] with one synthetic task, the scope you want to examine, a stop criterion, and your preferred next step. We can discuss a short assisted session or exchange written observations. A time, availability, scope, and any future commercial terms must be agreed; this page does not confirm a booking or a free pilot.

Stop at the boundary

Stop if the task needs a real credential, customer record, production log, filesystem access, outgoing message, payment, or deletion. Do not paste such data into the demo or send it by email. The browser controls are a teaching simulation, not a secure execution broker.

What counts as a result

A synthetic result is an observed mock policy decision for one fabricated request. A page visit or expression of interest is not product first use. Boundary’s model request routing and policy checks are planned; a real product result requires a separately agreed, available implementation. See the measurement definitions.

Explore the security handbook · Read product scope and status