canonical: https://jentic.com/apis/visible.vc/visible-vc

# Visible Vc Visible API

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

## For AI agents

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

## Scope

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

## Capabilities

- Create Update
- List Updates
- Get Update
- Query and filter Visible API records by parameters
- Monitor Visible API operational status and events

## Use cases

### Developer Tools Operations

Use the Visible API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including create update, list updates, get update.

Example prompt: Call POST /updates to create update

### Automated Investors Management

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

Example prompt: 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.

Example prompt: Search Jentic for 'create update', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **Investors** — Operations for investors
- **Metrics** — Operations for metrics
- **Updates** — Operations for updates

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/visible.vc/visible-vc/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.