Trychroma Chroma Cloud REST API

Name: Chroma Cloud REST API
Brand: Chroma Cloud REST API
Availability: InStock

✓ Official Vendor SpecAI/MLEmbeddings Searchbearer20 EndpointsREST

For Agents

Programmatically server heartbeat, get server version. Covers 20 operations with bearer authentication.

Install Jentic One Beta

Connect the Chroma Cloud REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Chroma Cloud REST 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Chroma Cloud REST API.

Server heartbeat

Get server version

Pre-flight checks

Create a tenant

GET STARTED

Start building with Chroma Cloud REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Chroma Cloud REST API for, with concrete tasks.

★ AI and Machine Learning Operations

Use the Chroma Cloud REST API to perform ai ml operations programmatically. The API provides 20 endpoints covering core functionality including server heartbeat, get server version, pre-flight checks.

Call GET /api/v2/heartbeat to server heartbeat

Automated Server Management

Automate server operations by combining multiple Chroma Cloud REST API endpoints. Agents can get server version and then pre-flight checks in a single workflow.

Call GET /api/v2/version to get server version, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Chroma Cloud REST 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 bearer tokens manually.

Search Jentic for 'server heartbeat', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

20 endpoints — chroma is an open-source ai-native vector database.

METHOD

PATH

DESCRIPTION

GET

/api/v2/heartbeat

Server heartbeat

GET

/api/v2/version

Get server version

GET

/api/v2/pre-flight-checks

Pre-flight checks

GET

/api/v2/tenants/{tenant}

Get a tenant

POST

/api/v2/tenants

Create a tenant

GET

/api/v2/tenants/{tenant}/databases/{database}

Get a database

POST

/api/v2/tenants/{tenant}/databases

Create a database

POST

/api/v2/tenants/{tenant}/databases/{database}/collections

Create a collection

GET

/api/v2/heartbeat

Server heartbeat

GET

/api/v2/version

Get server version

GET

/api/v2/pre-flight-checks

Pre-flight checks

GET

/api/v2/tenants/{tenant}

Get a tenant

POST

/api/v2/tenants

Create a tenant

GET

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Chroma Cloud REST API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'server heartbeat') and Jentic returns the matching Chroma Cloud REST API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Chroma Cloud REST API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using Chroma Cloud REST API through Jentic.

What authentication does the Chroma Cloud REST API use?

The Chroma Cloud REST API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I server heartbeat with the Chroma Cloud REST API?

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

What are the rate limits for the Chroma Cloud REST 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 server heartbeat through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'server heartbeat'. Jentic returns the matching Chroma Cloud REST API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the Chroma Cloud REST API have?

The Chroma Cloud REST API exposes 20 endpoints covering server, tenants, databases operations.

Trychroma Chroma Cloud REST API

Connect the Chroma Cloud REST API to your agent

Capabilities

Start building with Chroma Cloud REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs