Install Jentic One Beta

Connect the Vision6 JSON-RPC API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Vision6 JSON-RPC API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fvision6.com.au%2Fvision6-com-au" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fvision6.com.au%2Fvision6-com-au" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Vision6 JSON-RPC API.

Call a Vision6 JSON-RPC method

Add contacts to a list

Search contacts in a list

Edit contacts in a list

Delete contacts from a list

GET STARTED

Start building with Vision6 JSON-RPC API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Vision6 JSON-RPC API for, with concrete tasks.

★ Marketing Operations

Use the Vision6 JSON-RPC API to perform marketing operations programmatically. The API provides 12 endpoints covering core functionality including call a vision6 json-rpc method, add contacts to a list, search contacts in a list.

Call POST / to call a vision6 json-rpc method

Automated API Management

Automate API operations by combining multiple Vision6 JSON-RPC API endpoints. Agents can add contacts to a list and then search contacts in a list in a single workflow.

Call POST /?method=addContacts to add contacts to a list, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Vision6 JSON-RPC API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'call a vision6 json-rpc method', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

12 endpoints — the vision6 email marketing platform api.

METHOD

PATH

DESCRIPTION

POST

Call a Vision6 JSON-RPC method

POST

/?method=addContacts

Add contacts to a list

POST

/?method=searchContacts

Search contacts in a list

POST

/?method=editContacts

Edit contacts in a list

POST

/?method=deleteContacts

Delete contacts from a list

POST

/?method=getContactById

Get contact by ID

POST

/?method=unsubscribeContact

Unsubscribe a contact

POST

/?method=addList

Create a new list

POST

Call a Vision6 JSON-RPC method

POST

/?method=addContacts

Add contacts to a list

POST

/?method=searchContacts

Search contacts in a list

POST

/?method=editContacts

Edit contacts in a list

POST

/?method=deleteContacts

Delete contacts from a list

POST

/?method=getContactById

Get contact by ID

POST

/?method=unsubscribeContact

Unsubscribe a contact

POST

/?method=addList

Create a new list

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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.

FAQs

Specific to using Vision6 JSON-RPC API through Jentic.

What authentication does the Vision6 JSON-RPC API use?

The Vision6 JSON-RPC API uses an API key passed in the `X-Api-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I call a vision6 json-rpc method with the Vision6 JSON-RPC API?

Yes. Use the POST / endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Vision6 JSON-RPC API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I call a vision6 json-rpc method through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'call a vision6 json-rpc method'. Jentic returns the matching Vision6 JSON-RPC API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Vision6 JSON-RPC API have?

The Vision6 JSON-RPC API exposes 12 endpoints covering API, account, contacts operations.

Can I limit what my agent is allowed to do with the Vision6 JSON-RPC API?

Yes. Because Vision6 is a JSON-RPC service where the method name and its contact targets travel in the request body, Jentic One, which you self-host, lets you decide exactly which operations your agent may call. Your own rules scope the agent to the methods it needs, such as adding contacts to a list or searching contacts, and a destructive operation like deleting contacts stays out of reach unless you add it. Jentic One also holds your API key and injects it only for the operations you have allowed.

Vision6 JSON-RPC API

Name: Vision6 JSON-RPC API
Brand: Vision6 JSON-RPC API
Availability: InStock

Official vendor OpenAPI document · agent-readyMarketingEmail MarketingapiKey12 EndpointsREST

For Agents

Programmatically call a vision6 json-rpc method, add contacts to a list. Covers 12 operations with apiKey authentication.

Use for: I need to call a vision6 json-rpc method, I want to add contacts to a list, Search for contacts in a list, Find all edit contacts in a list

Not supported: Does not handle payments, communications, or crm - use for marketing only.

The Vision6 email marketing platform API. Uses JSON-RPC over HTTP POST. All requests go to a single endpoint with a method name and parameters. Vision6 is now owned by Constant Contact. The API exposes 12 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Vision6 JSON-RPC API to your agent

Capabilities

Start building with Vision6 JSON-RPC API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Vision6 JSON-RPC API