Selah
developers

Three calls and a gate.

Our engine is three endpoints in front of any agent: POST /v1/gate/check for input, POST /v1/evaluate for actions, POST /v1/validate/output for responses. The tenant resolves from your key, the verdicts share one rail, and the live schema at api.selahcore.com/openapi.json is authoritative.

The shape of an integration

Your agent emits a structured proposal instead of acting. A permit returns a decision identifier; a hold routes to the review surface for your tenancy; a deny stops. Carry an idempotency key in the action context and a retry can never act twice. Connectors execute permits server side with credentials your agent never sees.