Connections
Your APIs — calling your own systems
Register your own API so an agent can call it through Call a connected system, with method and path limits.
Settings → Connections → Your APIs. Needs connection.manage (Owner/Admin).
A connection lets the Call a connected system tool reach your API with credentials Ragenta keeps (encrypted) instead of anything in a prompt.
The form
| Field | Notes |
|---|---|
| Connection id | Slug the agent refers to it by. |
| Name | Display name. |
| Base URL | The https root of the API. |
| API key | Stored encrypted; only a hint is shown after saving. |
| Sent in header, Prefix | For example header Authorization, prefix Bearer . |
| Extra headers | Fixed additional headers. May contain {{visitor.id}} / {{visitor.email}} — filled with the visitor identity when the agent runs from an embedded chat. |
| Methods allowed | GET / POST / PUT / PATCH / DELETE — only the ticked ones. |
| Paths must start with | Allowed path prefix; the agent cannot call outside it. |
Test sends a probe request to confirm the credentials. A connection labelled provided comes from the deployment and cannot be edited.
Private and internal address ranges are blocked for every outbound agent request (SSRF guard); response size and time are capped too.
In Configuration, enable Call a connected system and mention the connection by name in the Instructions so the agent knows when to use it.