Skip to main content
Not available in the current beta. The internal_api tool is recognized by the policy engine and can be used in policies today, but the dashboard does not expose it as a connectable integration and gateway-proxy does not forward to internal API targets. This page will be updated when the integration ships.

​
What it will do

Internal API support will let you:
  • Route agent calls to your own backend services through Sentrail
  • Apply allow/block/require_approval policies to any HTTP endpoint your agents hit
  • Capture a full audit trail of agent → internal service interactions

​
Current state

The internal_api tool name is a valid ToolName in the type system: 
type ToolName = "github" | "linear" | "slack" | "notion" | "internal_api" | "mcp";
You can create policies scoped to tool = "internal_api" today, and they will evaluate when evaluate-action or simulate-action is called with that tool. However, gateway-proxy does not forward to internal API targets and the beta dashboard does not offer an Internal API connection flow. For internal API gating today, use the evaluate-action endpoint directly in your pipeline and enforce the decision in your own code.