DOCUMENTATION / Connect tools
Custom HTTP tools
Register a product-specific HTTPS endpoint and understand the current execution limits.
Use a custom HTTP tool to register an endpoint outside the built-in provider catalog. The current browser form saves the endpoint and credentials. Saving a tool does not make it an autonomous chat tool or provide a complete execution workflow.
Register an endpoint
- Select the product and open Tools → Custom tools → New tool.
- Enter a descriptive Tool name.
- Enter HTTPS origin, for example
https://api.example.com. Keep the request path out of this field. - Choose Method: POST, GET, PUT, PATCH, or DELETE.
- Enter Path, such as
/v1/reports. - Optionally enter API key. Jak sends it as an
Authorization: Bearercredential. - Choose Save tool.
The browser form saves an object input schema and treats the effect as unknown. It does not offer arbitrary authentication headers or a full schema editor.
Endpoint requirements
Custom tools connect to public HTTPS endpoints on port 443. Private or loopback addresses and redirects are rejected, and requests have response and time limits. A service that needs a different authentication scheme is not supported by this form.
GET actions send no JSON body. Other methods send the approved payload as JSON. Do not put credentials into the path or payload to work around the authentication format.
Current execution limits
Every custom HTTP action requires approval, including a GET or a tool you consider read-only. The current task screen has no general custom-action approval form. You can register an endpoint, but running arbitrary saved tools is not available as a complete browser workflow yet.
Use the built-in connectors for their supported browser workflows. Do not expect a chat request to run a saved custom endpoint. See Publishing and exports for the actions you can currently approve in the app.
Manage the tool
The Custom tools tab lists saved tools and whether a key is present. Delete a tool to remove its saved endpoint and credential from this product. Check external results before repeating an action that timed out or returned an uncertain outcome.