UptimeToolbox API

Setup

Wiring the UptimeToolbox API by hand means combining its bearer token with the X-ORGANIZATION-ID header on every call and routing heartbeat and node requests yourself. Through Jentic you install once, import UptimeToolbox from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

UptimeToolbox puts the heartbeat id in the URL path (/heartbeat/{heartbeat}), so a rule can pin your agent to one heartbeat: it can post and read that heartbeat and nothing else. You choose the operations it may call, so nothing beyond the ones you list runs.

Credential isolation

Your UptimeToolbox bearer token and organization id are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'post a heartbeat ping' or 'read a node by GUID', and Jentic returns the matching UptimeToolbox operation with its input schema so the agent calls the right endpoint without browsing the reference docs.