---
title: "Authenticating Tools"
---

Each tool in our library has its own method of authentication. These methods are enforced by the API Provider itself.
On this page, you can find how to authenticate the tools that are availaible in the library currently.

## Supported Authentication Methods

1. **Bearer Authentication**
2. **Basic Authentication**
3. **API Key-Based Authentication** (via query parameters or headers)
4. **OAuth Authentication** (e.g., for Microsoft, X)

## Tools Authentication by Provider

Below is a list of tools available in our library along with a column for their corresponding authentication method.

| Tool Provider             | Authentication Type                           |
| ------------------------- | --------------------------------------------- |
| Airia                     | None                                          |
| AlphaVantage              | Query Parameter Authentication                |
| ArXiv                     | None                                          |
| Asana                     | Bearer Authentication                         |
| Atlassian                 | Basic Authentication                          |
| Exa                       | Header Authentication (x-api-key)             |
| FireCrawl                 | Bearer Authentication                         |
| Google                    | OAuth (Google)                                |
| IP API                    | None                                          |
| Jina                      | Bearer Authentication                         |
| LinkPreview               | Header Authentication (X-Linkpreview-Api-Key) |
| Math.js                   | None                                          |
| Microsoft                 | OAuth (Microsoft)                             |
| Microsoft Bing            | Airia Universal Key                           |
| Mongo                     | Username and Password Authentication          |
| Ms. SQL                   | Username and Password Authentication          |
| MySQL                     | Username and Password Authentication          |
| MySQL                     | None                                          |
| NASA                      | Query Parameter Authentication (api_key)      |
| Nutrionix                 | Bearer Authentication                         |
| OpenAI                    | Bearer Authentication                         |
| Postgres                  | Bearer Authentication                         |
| Reddit                    | Bearer Authentication                         |
| Salesforce                | OAuth (Salesforce)                            |
| Serper                    | Header Authentication (X-API-KEY)             |
| Snowflake                 | Private Key Authentication                    |
| Spotify                   | Bearer Authentication                         |
| Strava                    | Bearer Authentication                         |
| Twillio                   | Bearer Authentication                         |
| WeatherStack              | Query Parameter Authentication (access_key)   |
| Wolfram Alpha             | Query Parameter Authentication (appid)        |
| X                         | OAuth (X)                                     |
| YouTube                   | Airia Universal Key / Bearer Authentication   |
| World Health Organization | Airia Universal Key                           |

## End User Auth

In addition to authenticating with a credential as an Admin, you can also let your End Users provide their own authentication details when interacting with the tool in the Airia Chat app.

To get started, configure your tool to have "End User Auth" enabled when adding the Tool to a project. For tools with multiple credential options, you will see the option to select the preferrred authentication method.

Once your Tool is deployed to Airia Chat, you will see the option to authenticate the tool as an Integration before talking to the Agent.

<Note>
  _Tool definitions for un-authenticated tools are not sent to a Model, so a Model may not "see" a Tool if it has not been authenticated by a user first._
</Note>

User Authentication is supported for all tools in the Airia Tools library, including MCP Servers.
