Read a smart lock's live status and capabilities via the Seam API
domain: docs.seam.co · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate requests to the Seam API with your workspace API key in the Authorization header
List connected devices filtered to capability 'lock' or 'access_code' to enumerate smart locks in the workspace
Retrieve a specific lock's device object and check can_remotely_lock, can_remotely_unlock, and can_program_online_access_codes to know what actions that brand/model supports
Read properties.locked, properties.online, and properties.battery.level to reflect real-time state in a dispatch or job app
Check properties.model.offline_access_codes_supported vs. online_access_codes_supported to decide whether to program a PIN online or push it for next offline sync
Known gotchas
Capability support varies significantly by manufacturer/model, so always check the device object rather than assuming a feature exists
device_type strings are brand-specific (e.g. schlage_lock); don't hardcode logic against a single brand
'locked' and 'online' reflect the last state Seam has synced, which can lag brief connectivity drops
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?