For builders

Add protected AI to the systems your team already uses.

Use RedactNode as a controlled boundary for internal tools, workflows, and custom AI experiences. This overview explains the integration shape before you dive into endpoint-level details.

Contact engineering

The request path

Your application sends a prompt to the protected workflow. Rules identify sensitive values, safe tokens are sent to the provider, and the response is restored for the authorised user.

  • Application to protected gateway
  • Rule evaluation before provider access
  • Masked provider request
  • Restored response returned to your application

Keep secrets out of logs

Integration should preserve the same privacy boundary as the portal. Log operational metadata, not the raw prompt or token map.

  • Use request IDs for tracing
  • Keep provider responses scoped
  • Apply retention to audit metadata
  • Never include raw PII in error messages

Connect incrementally

Start with one internal workflow and synthetic test data. Once the path is understood, expand the rules and provider coverage with confidence.

  • Test normal and sensitive prompts
  • Verify masking and restoration
  • Handle provider failures safely
  • Define an escalation owner

Need the full reference?

The exact API surface depends on your deployment and identity model. Talk to the team for environment-specific documentation and pilot access.

  • Hosted Safe Zone integration
  • Private deployment planning
  • Custom rules and provider routing
  • Authentication and audit requirements

Make safe AI the easy default.

Start with the workflow that fits your organisation, then add the controls your compliance team needs.

Read the getting-started guide