Vision6 JSON-RPC API

Setup

Wiring the Vision6 JSON-RPC API by hand means passing its API-key request header, packing each method name and its arguments into the JSON-RPC body, and posting to the single endpoint yourself. Through Jentic you install once, import the Vision6 JSON-RPC API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Vision6 is a JSON-RPC service where the method and its contact targets travel in the request body rather than the URL path, so scope the agent to the operations it needs, such as adding or searching contacts. You choose that set, so a destructive operation like deleting contacts is not included unless you add it.

Credential isolation

Your Vision6 API key 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 'add a contact to a list' or 'search contacts', and Jentic returns the matching Vision6 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.