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

Open Connections

  1. Open Connections and click Connect on Custom HTTP Tool.
  2. Enter your connection details, in order:
    • Name: for example my-http-tool
    • Base URL: must start with http:// or https://
    • Auth Type: None, API Key (custom header), Bearer Token, or Basic (username + password)
    • If Auth Type is API Key (custom header): Header Name (defaults to X-API-Key) and API Key
    • If Auth Type is Bearer Token: Bearer Token
    • If Auth Type is Basic (username + password): Username and Password
    • Endpoints (JSON): one JSON array entry per endpoint you want the agent to call
    • Timeout (s): default 10, accepted range 0.5–60
    • Max Response Bytes: default 65536, accepted range 1024–1048576
    • Allow private/loopback network targets (disables SSRF guard): off by default
Leave Allow private/loopback network targets (disables SSRF guard) off unless you need NOFire AI to reach an address inside your own network. Turning it on disables the SSRF guard.
Test checks the configuration and blocks private/loopback URLs. It does not call your endpoints. Each endpoint becomes an agent tool after save.
Click Connect. NOFire checks the credentials and creates the connection.

​
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:

​
Test the connection

  1. Open Connections and make sure that the Custom HTTP Tool connection shows Connected.
  2. Ask NOFire AI to call one of the endpoints you listed, by its name. A reply carrying the response from your API confirms the endpoint became an agent tool.
The Test button on the form checks the configuration only. It does not call your endpoints, so a passing test does not prove an endpoint works.

​
Troubleshooting

The value must be a JSON array, and every entry needs name, method, path, and description. Every placeholder in the path, such as {id}, must also appear under path_params.
The base URL resolves to a private or loopback address and the SSRF guard blocked it. Turn on Allow private/loopback network targets only if NOFire AI must reach an address inside your own network.
The response was larger than Max Response Bytes. Raise it, up to 1048576, or narrow the endpoint so it returns less.
Raise Timeout (s), up to 60. If the API is slower than that, it is not a good fit for an agent tool.