Authenticate to the Kisi API with an API key and remotely unlock a door
domain: docs.kisi.io · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Generate an API key for an admin or service user in the Kisi dashboard
Send requests with the header Authorization: KISI-LOGIN <API_KEY>
POST to https://api.kisi.io/locks/{id}/unlock to remotely trigger that lock
Respect the rate limit of 5 authenticated requests per second per user
Check the response to confirm the unlock request succeeded before assuming the door opened
Known gotchas
Unlocking with admin/API-key credentials is the simplest integration method but doesn't provide a per-end-user unlock audit trail the way user-specific unlock flows do
The rate limit (5 req/s) is enforced per authenticated user and separately per IP for unauthenticated calls — bursts can get throttled
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?