Arcade.dev
AI InfrastructureFreemiumVisit Site
One control point for the actions agents take in real systems — user-scoped auth, 8,000+ permission-aware tools, and an audit trail per action.
Overview
The unglamorous reason agent projects stall in production is authorisation. The demo works because it runs on a service account with god-mode access to Salesforce and Google Workspace; security kills it for exactly that reason. Arcade fixes the shape of the problem: agents authenticate through your existing identity provider and act on behalf of a specific authenticated user, inheriting that user's permissions, with every action logged. It ships 8,000+ permission-aware tools plus support for your own MCP servers, so you are not hand-rolling OAuth per integration. Pricing is the part worth noting in a demo-gated category — Free covers 2,000 auth events and 2,000 tool calls a month, Team is $25/month plus $0.10 per auth event and $0.01 per tool call, and Enterprise adds VPC or air-gapped deployment, SSO, RBAC, and a private registry. Buy it when your agent needs to write, not read. If your agent only reads public data, this is overhead you do not need yet.
Pros & Cons
Pros
- Agents act as a specific user, not a god-mode service account
- Published usage pricing in a category that is usually demo-gated
- 8,000+ pre-built permission-aware tools plus custom MCP support
- Per-action audit trail — the artifact security actually asks for
- SOC 2 certified, with VPC and air-gapped deployment options
Cons
- Another layer between your agent and its tools — added latency and a new dependency
- Usage pricing on auth events can surprise you at high user counts
- Only worth it once agents take write actions, not just read
- Requires engineering integration; not a business-user product
- Tool coverage is broad but you should verify your specific systems
Workflows that use Arcade.dev
Get a new AI workflow each week — many feature Arcade.dev and other tools in this category.