Ziflow API

Setup

Wiring Ziflow by hand means picking one of its several auth styles, bearer, basic, or an apikey header or query parameter, and pointing requests at the api.ziflow.io host yourself. Through Jentic you install once, import Ziflow from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Ziflow puts the proof id in the URL path (/proofs/{id}), so a rule can pin your agent to one proof: it can read and update that proof and nothing else. You choose the operations it may call, so destructive ones like proof deletion are not included unless you add them.

Credential isolation

Your Ziflow credential 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 'create a new proof' or 'search proof activity', and Jentic returns the matching Ziflow operation with its input schema so the agent calls the right endpoint without browsing the reference docs.