UserCheck API

Setup

Wiring the UserCheck API by hand means attaching its bearer token, encoding the email or domain into the path, and maintaining your blocklist through separate calls yourself. Through Jentic you install once, import UserCheck from the API Directory, store the token once, and your agent calls it.

Permission scoping

UserCheck puts the domain in the URL path (/blocklist/{domain}), so a rule can pin your agent to one domain's blocklist entry: it can read that entry if you allow it. You choose the operations it may call, so blocklist deletion is not included unless you add it.

Credential isolation

Your UserCheck 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 'validate an email address' or 'check a domain', and Jentic returns the matching UserCheck operation with its input schema so the agent calls the right endpoint without browsing the reference docs.