Authorize tools before the agent runs
With Just-in-time authentication, the agent will request the user to authorize each tool before running it. In many cases, this experience is not what you want to provide to your users. For example, you may expect the users to be able to list their emails, as well as send emails immediately after. With JIT auth, the user would have to authorize each tool separately, which may result in too much friction.
Overview
In this guide, you’ll learn how to use Arcade to authorize multiple tools before the agent runs.
This involves the following steps:
- Get a list of all the tools that the agent will use
- Authorize all the tools (grouped by their Auth provider)
- Run the agent only after all the tools are authorized
This guide will rely on Arcade’s built-in user verification system. If you want to run this in production, you’ll need to implement a custom user verifier. Learn more about user verification.
Prerequisites
Building real Agents with Arcade
Welcome to the Arcade foundations course! In this free interactive course, you’ll learn the core features of Arcade by building a real agentic application.
What you’ll build
(screenshot placeholder)
In this course, you’ll build a chatbot that can interact with your personal context, contained in third party applications like Gmail, Slack, Notion, Google Docs, etc. The application will have:
- User login and registration
- A dashboard to manage integrations and configurations
- Choose the LLM provider
- The ability to choose the LLM model
- Secure tool calling with MCP
- Just-in-time authentication
- Human-in-the-loop
- Multi-user support
- Building your own tools
- Integrating with third party apps
Overview
Here’s an overview of the features you’ll learn in this course:
- Agentic application architectures
- Agentic frameworks
- Agentic gateways
- Tool calling
- MCP
- Just-in-time authentication
- Human-in-the-loop
- Agentic testing and evals
- Agentic monitoring and observability