Install Jentic One Beta

Connect the Visible API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Visible 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%2Fvisible.vc%2Fvisible-vc" | 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%2Fvisible.vc%2Fvisible-vc" | 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 Visible API.

Create Update

List Updates

Get Update

Query and filter Visible API records by parameters

Monitor Visible API operational status and events

Use Cases

GET STARTED

Start building with Visible API

Explore with Jentic One

View OpenAPI Document

Automated Investors Management

Automate investors operations by combining multiple Visible API endpoints. Agents can list updates and then get update in a single workflow.

Call GET /updates to list updates, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Visible 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 'create update', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

8 endpoints — investor relations and reporting api (apiary documentation tls certificate issue).

METHOD

PATH

DESCRIPTION

POST

/updates

Create Update

GET

/updates

List Updates

GET

/updates/{id}

Get Update

POST

/metrics

Create Metric

GET

/metrics

List Metrics

GET

/metrics/{id}

Get Metric

GET

/investors

List Investors

GET

/investors/{id}

Get Investor

POST

/updates

Create Update

GET

/updates

List Updates

GET

/updates/{id}

Get Update

POST

/metrics

Create Metric

GET

/metrics

List Metrics

GET

/metrics/{id}

Get Metric

GET

/investors

List Investors

GET

/investors/{id}

Get Investor

Why Jentic?

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

Setup

Wiring the Visible API by hand means passing its apiKey in the Authorization header and threading it through the updates, metrics, and investors calls yourself. Through Jentic you install once, import the Visible API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Visible puts the record id in the URL path (/updates/{id} and /metrics/{id}), so a rule can pin your agent to one update or metric. You choose the operations it may call, so it can read a record without being able to post new updates unless you add that.

Credential isolation

Your Visible 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 'create an investor update' or 'read a metric value', and Jentic returns the matching Visible operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Visible API through Jentic.

What authentication does the Visible API use?

The Visible API uses an API key passed in the `Authorization` 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 create update with the Visible API?

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

What are the rate limits for the Visible 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 create update through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create update'. Jentic returns the matching Visible API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Visible API have?

The Visible API exposes 8 endpoints covering investors, metrics, updates operations.

Can I limit what my agent is allowed to do with the Visible API?

Yes. Because you run Jentic One yourself, your own rules decide which Visible API operations and credentials the agent may use. You can allow it to list or read a single record with GET /updates/{id} or GET /metrics/{id} without granting POST /updates or POST /metrics, so it cannot create new updates or metrics unless you add those operations. Since the record id sits in the URL path, a rule can also pin the agent to one specific update or metric.

Visible Vc Visible API

Name: Visible API
Brand: Visible API
Availability: InStock

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey8 EndpointsREST

For Agents

Programmatically create update, list updates. Covers 8 operations with apiKey authentication.

Use for: I need to update, I want to updates, Search for update, Find all metric

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

Investor relations and reporting API (Apiary documentation TLS certificate issue). The API exposes 8 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document