Skip to main content
Connect a read-only HTTP API to bring its data into NOFire’s system context. Before a deploy, that context shows what the change touches. When something breaks, the same signals are the evidence NOFire reasons over. You authenticate with the API’s own credential: an API key, a bearer token, or a username and password. You then choose exactly which endpoints NOFire AI can call.

​
Step 1: Prepare your API

Before you add the connection, have ready:
  • The base URL of the API, for example https://api.example.com
  • A credential, if the API requires one: an API key, a bearer token, or a username and password
  • For each endpoint you want NOFire AI to call: its HTTP method, path, and a short description of what it returns
Each endpoint you list becomes a callable agent tool once you save the connection. List read-only endpoints only.

​
Step 2: Add Custom HTTP Tool Connection to NOFire AI

Navigate to the Connections tab

​
Defining endpoints

One entry per endpoint you want the agent to call. Each entry needs a name, method, path, and description. Use path_params, query_params, or body_params to declare inputs. You must list placeholders in the path, like {id}, under path_params. The field starts pre-filled with a worked example: