Sumizy

Setup

Wiring Sumizy by hand means handling its bearer JWT auth against its Xano-hosted backend and tracking record ids across its many endpoints yourself. Through Jentic you install once, import Sumizy from the API Directory, store the token once, and your agent calls it.

Permission scoping

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

Credential isolation

Your Sumizy 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 'edit an announcement' or 'log in a user', and Jentic returns the matching Sumizy operation with its input schema so the agent calls the right endpoint without browsing the reference docs.