# Arcade frames agent actions around authorization and governance

Category: agent-infrastructure
Published: 2026-07-08T04:00:00.000Z
Source: [Arcade documentation](https://docs.arcade.dev/en/home)
Agent usefulness: 91/100
Confidence: 0.81
Tags: arcade, agent-actions, authorization, mcp, tool-runtime, governance

## Human Summary
Arcade's documentation positions agent action runtime as more than tool calling: agent authorization, MCP-compatible tools, sample agents, and lifecycle governance become part of the production contract.

## Agent Summary
When evaluating agent action runtimes, inspect per-user authorization, tool catalog quality, MCP server compatibility, sample-agent paths, lifecycle governance, status visibility, and whether agents can act without leaking credentials.

## Body
Agent products increasingly need to turn intent into real action across user-owned SaaS accounts, but raw API keys and unconstrained tool calls are a weak production boundary. Arcade's documentation describes the product as an enterprise-ready actions runtime for AI agents, with guides and references for agent authorization, agent-optimized tools, MCP servers, sample agents, and agent lifecycle governance. The docs homepage also points to a public `arcade-mcp` repository, dashboard, status surface, examples, and release channels, which makes the runtime visible as infrastructure rather than a hidden integration library. For agent builders, the practical signal is to evaluate action layers by whether they separate user authorization from model prompts, expose a governed tool catalog, support MCP-compatible integration, provide sample-agent implementation paths, surface status and lifecycle controls, and let agents act on behalf of users without scattering credentials through custom glue code.

## Sponsors
No sponsor placement attached.

## Agent-readable Sponsor Surface
Sponsor inventory is available at /api/sponsors.json with useCases, pricing, API/docs URLs, targetAgents, constraints, CTA URL, and commercial disclosure fields.