Seam for AI agents
Seam is an API for controlling smart locks, access systems, thermostats, and other connected devices across a workspace, used by teams building access and automation workflows. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Seam.
Look up a device before acting
Reads a smart lock or thermostat's current status before sending it a command.
Create an access grant
Issues a time-bound access code to a specific space for a guest or vendor.
Delete an access grant only after confirmation
Revokes an issued access grant only once the request to remove that person's access is confirmed.
10 Seam actions, graded by risk.
Every Seam action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- seam.list_spacesList Spaces
- seam.list_devicesList Devices
- seam.get_access_grantGet Access Grant
- seam.list_access_grantsList Access Grants
- seam.list_action_attemptsList Action Attempts
- seam.list_connected_accountsList Connected Accounts
write
3Create and change things. Allow, or ask the user first.
- seam.create_access_grantCreate Access Grant
- seam.update_access_grantUpdate Access Grant
- seam.add_access_methods_to_grantAdd Access Methods to Grant
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- seam.delete_access_grantDelete Access Grant
Seam in three steps.
- 01Your users connect SeamThey add their Seam api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Access Grant” can wait for the user, and “delete Access Grant” can be denied outright.
- 03Any agent can actYour agent calls Seam through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('seam', { read: 'allow', write: 'ask', // create_access_grant destructive: 'deny', // delete_access_grant }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Seam connects.
Users add their Seam api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Seam connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Seam from any agent.
Seam and Arc0, answered.
Can I use Seam with Claude, ChatGPT or Cursor?
Yes. Connect Seam to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Seam actions you allow.
How do users connect Seam?
Users add their Seam api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Seam actions can my agent take?
10 in total: 6 read, 3 write and 1 destructive, such as “create Access Grant”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Seam?
Yes. Actions like “delete Access Grant” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Seam too?
Yes. The same Seam connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Seam into your agent.
Your users connect Seam once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan