AnthropicFor applications routed through RedactWall.
Compatible applications you explicitly configure to route through RedactWall keep using the Anthropic protocol. Requests and responses on that route are checked before forwarding; direct provider traffic remains outside the gateway.
What that looks like
A routed application sends a customer file in an Anthropic request
Stopped before it reaches Anthropic, and the attempt is on the record.
An Anthropic response returns through RedactWall with an account number
Caught on the way back, before your application shows it.
An analyst tries a workaround the policy forbids outright
Refused, because 21 hard stops cannot be switched off by anyone.
What it takes to switch on
Configure each compatible application to use the RedactWall gateway endpoint for Anthropic traffic. Only requests and responses that use that route are governed.
How far this is proven
Proven liveRedactWall has been run against Anthropic’s live service under a real account, on 2026-08-14. The request went through, and the decision on the way out and the decision on the way back were both recorded.
Every limit, in one place: Disclosures.
Review the proposed first pilot
The proposed first pilot covers ChatGPT text in managed Chrome and a separately verified Anthropic gateway path. Other integrations are part of the broader product.
- Coverage is published for this integration
- Proof status is shown explicitly
- Pilot scope is agreed before onboarding