Skip to content

Face check-in is here: 1:1, liveness-checked, consent first

Connect your systems and your AI assistants

Scoped API keys, signed webhooks and a remote MCP server let your own tools read presence and register visitors.

Included on Starter and above.

What is included

  • REST API with per-organisation API keys, hashed at rest and limited to the scopes you choose.
  • Webhooks for check-in, check-out, roll call and building status, signed with HMAC-SHA256 (Standard Webhooks), retried for 24 hours.
  • A remote MCP server: ask who is on site or register a visitor from Claude, ChatGPT or Copilot.
  • Ask SiteRoll: plain-English questions over your own data, read-only and tenant-scoped, with a no-AI fallback.
  • Webhooks and MCP on Business and above; the API from Starter.

Questions

How do I verify a webhook?
Compute HMAC-SHA256 over “id.timestamp.body” with your secret and compare it with the v1 signature; reject timestamps older than five minutes.
Can the AI change my data?
No. Ask SiteRoll only reads through fixed, tenant-scoped tools. The MCP server’s one write tool, invite_visitor, needs a key with the people:write scope.