INTEGRATIONS

One verification contract across different stacks.

The current integration surface uses versioned browser SDKs and an HTTP verification boundary that works with any backend capable of sending a request.

Developer experience

Browser and HTML

Use the versioned loader in traditional forms, server-rendered pages, SPAs, or WebViews that provide a supported browser origin.

  • V1 widget loader
  • V2 managed SDK
  • V3 execute SDK

Developer experience

PHP and Laravel

Submit the token and secret from a trusted server, then enforce hostname, action, and score policy in application code.

  • HTTP-compatible endpoint
  • Stable JSON response
  • No client-side secret

Developer experience

Framework adapters

React, Vue, WordPress, and other dedicated packages belong to the integration phase; the underlying API is already framework-neutral.

  • Plain JavaScript today
  • Package contracts next
  • No undocumented package claims

Build a safer user journey.

Register a hostname and choose the amount of verification friction each action deserves.

Create account