> ## Documentation Index
> Fetch the complete documentation index at: https://silmaril.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Verify your integration

> Confirm traffic, connected boundaries, and enforcement before production rollout.

Use a test environment and the deployment credentials supplied by Silmaril. Begin in Shadow or Warn mode so you can review would-block decisions while the workflow runs.

## Confirm traffic

Send a benign request through your integration. Record its timestamp, request ID, conversation ID, and verdict. Open the supplied dashboard, select the matching Firewall and time window, and check **Monitoring** for traffic. Use available request and trace evidence to correlate the event.

A traffic count establishes that requests arrived. Inspect a specific event to verify its hook, tool name, and deployment.

## Check each boundary

| Integration | Check |
| - | - |
| Direct SDK | Each intended input, tool, and output path calls `classify()` and handles the result |
| Framework | Model and tool callbacks run on the model or graph used by the application |
| Deep Agents | Root and subagent checks run through protected constructors |
| LiteLLM | Pre-call and post-call checks appear for the proxy traffic you intend to cover |
| Vercel AI SDK or Gateway | Calls use the wrapped model and generated text passes the explicit output check |
| Agent plugin | A new supported-agent session produces activity for its supported lifecycle hooks |

For endpoint deployment, follow [macOS verification](https://silmaril.dev/docs/macos/verify.md).

## Verify a block

Arrange a controlled blocking test with Silmaril for your deployment. Run it through the same connected path in a test environment.

In observation mode, confirm the would-block finding and continued execution. Enable Block for that boundary, repeat the test, and confirm the application stops or safely replaces the event before it is consumed. Review the [integration's enforcement behavior](https://silmaril.dev/docs/guides/enforcement.md).

Check the application's handling of an unavailable Firewall endpoint in the test environment. Confirm it follows the error policy you chose.

## Expand the rollout

Review findings and legitimate workflows from the pilot. Keep the tested mode, credentials, and integration version in the deployment configuration. Expand one cohort or boundary at a time and repeat verification after changes.

If blocking interrupts legitimate work, return the affected boundary to the previous mode while you [report the finding](https://silmaril.dev/docs/operate/findings.md#report-a-false-positive). Keep unaffected protections in place.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.