Apilio for AI agents
Apilio is a home automation platform that connects smart devices from many brands and lets users build automations with conditions, schedules, and integrations like IFTTT and Tuya. 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 Apilio.
Check a smart home variable's value
Read the current value of a boolean, numeric, or string variable used in an automation.
Review conditions before an automation runs
List the time-based or Tuya device conditions configured inside a logic block.
List logic blocks before making a change
List all logic blocks to understand what automations already exist before editing one.
8 Apilio actions, graded by risk.
Every Apilio action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
8Look things up. Allowed by default.
- apilio.get_conditionsGet Conditions
- apilio.get_logicblocksGet Logicblocks
- apilio.get_string_variablesGet String Variables
- apilio.list_time_conditionsList Time Conditions
- apilio.list_tuya_conditionsList Tuya Conditions
- apilio.get_boolean_variablesGet Boolean Variables
- apilio.get_numeric_variablesGet Numeric Variables
- apilio.list_variable_conditionsList Variable Conditions
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Apilio in three steps.
- 01Your users connect ApilioThey add their Apilio api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Apilio through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('apilio', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Apilio connects.
Users add their Apilio 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 Apilio 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 · Username and password
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Apilio from any agent.
Apilio and Arc0, answered.
Can I use Apilio with Claude, ChatGPT or Cursor?
Yes. Connect Apilio 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 Apilio actions you allow.
How do users connect Apilio?
Users add their Apilio 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 Apilio actions can my agent take?
8 in total: 8 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Apilio?
Yes. Allow read actions and deny writes in the Apilio policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Apilio too?
Yes. The same Apilio connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Apilio into your agent.
Your users connect Apilio once, under your brand. Your agent gets 8 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan