Zapnito API

Setup

Wiring Zapnito by hand means putting its token in the Authorization header, filling in your own domain for the {your-domain}/api/v1 host, and coding the request handling yourself. Through Jentic you install once, import Zapnito from the API Directory, store the token once, and your agent calls it.

Permission scoping

Zapnito exposes a ping check rather than resource ids in the URL path, so limit the agent to the operations it needs, such as the ping health check. You add further operations only as you expose them, so the agent stays confined to what you allow.

Credential isolation

Your Zapnito token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'check the Zapnito API is reachable', and Jentic returns the matching Zapnito operation with its input schema so the agent calls the right endpoint without browsing the reference docs.