Developers · API v1

Integrate in three simple steps.

Use the decision API when you need server-side integration. No-custom-API options for forms, sign-ins and bots are also on our roadmap. Public pilot access is not yet open.

1. Submit a decision request

Keep your API key on the server. Provide the operation and a client IP validated by your trusted infrastructure.

Never embed API keys in browser JavaScript or public code.
HTTP request · Example
POST /api/v1/security/check
Authorization: Bearer <API_KEY>
Content-Type: application/json

{
  "operation": "login",
  "client_ip": "203.0.113.10"
}

2. Apply the result safely

Inspect allowed in an HTTP 200 response. false means block. HTTP 503 and timeouts are never implicit approval.

HTTP response · Example
{
  "decision": "block",
  "allowed": false,
  "reason": "rate_limit_exceeded",
  "rate_limit": {
    "limit": 5,
    "remaining": 0,
    "reset_after_seconds": 42
  },
  "request_id": "..."
}
Step 3 · Enforce in your application

Apply the decision with a safe fallback.

Your application must enforce allowed=false as a block and define safe handling for unavailable decisions. Public customer keys and production access are not yet available.

API reference

RouteMethodResult
/api/v1/security/checkPOST200 + allowed true/false; 400, 401, 405, 413, 415, 503

HTTP status semantics

HTTPMeaningIntegration action
200Valid security decisionInspect allowed true/false
400Invalid JSON or operationCorrect request input
401Missing/invalid Bearer keyCheck server-side credentials
405Wrong HTTP methodUse POST
413Request too largeReduce payload
415Unsupported media typeSend application/json
503Decision service unavailableNever auto-allow; apply safe fallback

Future integration capabilities (not live)

CAPTCHA verification, form components, plugins, login defenses and event APIs are on the roadmap. We do not advertise non-existent endpoints.

For the product capability set, see Features.