Install Jentic One Beta

Connect the DISCO Reporting API to your agent

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

List the datasets available to the authenticated DISCO organization

Retrieve the data usage changes dataset to see how usage has shifted over a period

Inspect the metadata that describes the schema and refresh cadence of the data usage changes dataset

List the metrics catalogue available to the authenticated organization

GET STARTED

Start building with DISCO Reporting API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DISCO Reporting API for, with concrete tasks.

★ Legal Ops Spend Tracking

Track DISCO consumption to manage legal operations budgets and chargebacks to matters. The agent pulls the data usage changes dataset on a schedule and writes it into a finance-friendly format so legal ops can attribute costs back to specific matters and clients. This avoids manual exports from the DISCO dashboard and gives finance a real-time view of platform spend.

Call GET /datasets/data-usage-changes for the current period and write the rows to the finance reporting warehouse with matter attribution.

Storage Growth Forecasting

Forecast DISCO review database storage growth to plan retention and budget. The agent retrieves the review database size metric on a schedule, persists the time series, and runs simple regression to predict next-quarter storage cost. This shifts ediscovery storage planning from reactive surprise to proactive forecasting tied to matter lifecycle.

Call GET /metrics/metric-reviewdb-size weekly, append to the time series, and run a 4-week moving average to project next quarter's storage.

Schema-Aware Reporting Pipeline

Build a reporting pipeline that adapts when DISCO updates its dataset schemas by inspecting metadata before each pull. The agent calls the metadata endpoints first, compares them against the previous run's schema fingerprint, and only triggers downstream transforms when columns have changed. This avoids brittle ETL jobs that break silently when DISCO ships schema updates.

Call GET /datasets/data-usage-changes/metadata, hash the column list, and short-circuit the pipeline if the hash matches the previous run.

AI Agent Legal Reporting

An AI agent supporting legal operations can answer questions like 'what was DISCO usage in May' or 'how fast is review storage growing' through Jentic. The agent searches for the right DISCO Reporting operation, loads its schema, and executes against the two header API keys stored in the vault. Sensitive matter context never leaves the vault because the agent only sees the metric values it requested.

Search Jentic for 'pull DISCO data usage changes', load the dataset operation, and execute it scoped to the user's organization.

Key Endpoints

6 endpoints — the disco reporting api exposes datasets and metrics from cs disco's ediscovery platform so legal operations teams can pull usage and consumption data into their own reporting stack.

METHOD

PATH

DESCRIPTION

GET

/datasets

List available datasets

GET

/datasets/data-usage-changes

Retrieve the data usage changes dataset

GET

/datasets/data-usage-changes/metadata

Inspect the data usage changes schema

GET

/metrics

List available metrics

GET

/metrics/metric-reviewdb-size

Retrieve review database size metric

GET

/metrics/metric-reviewdb-size/metadata

Inspect review database size metric schema

GET

/datasets

List available datasets

GET

/datasets/data-usage-changes

Retrieve the data usage changes dataset

GET

/datasets/data-usage-changes/metadata

Inspect the data usage changes schema

GET

/metrics

List available metrics

GET

/metrics/metric-reviewdb-size

Retrieve review database size metric

GET

/metrics/metric-reviewdb-size/metadata

Inspect review database size metric schema

Why Jentic?

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

Setup

Wiring the DISCO Reporting API by hand means setting both the disco-api-key and organization-id headers on every call, targeting the api.csdisco.com host, and handling retries yourself. Through Jentic you install once, import the DISCO Reporting API from the API Directory, store the key and organization id once, and your agent calls it.

Permission scoping

The DISCO Reporting surface is read-only, with datasets and metrics selected by header and route rather than by an id in the URL path, so limit the agent to the operations it needs, such as reading data-usage changes or the review database size. You choose which of those reporting operations are in scope.

Credential isolation

Your DISCO disco-api-key and organization-id are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'pull DISCO data usage' or 'get DISCO review database size', and Jentic returns the matching DISCO Reporting operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using DISCO Reporting API through Jentic.

What authentication does the DISCO Reporting API use?

DISCO uses two header API keys: disco-api-key identifies the user and organization-id scopes the request to a specific tenant. Both must be present on every call. Through Jentic both values are stored in the vault and added at execution time.

Can I pull data usage data with the DISCO Reporting API?

Yes. Call GET /datasets/data-usage-changes to retrieve the dataset, and GET /datasets/data-usage-changes/metadata to inspect the schema and refresh cadence before parsing the dataset response.

What are the rate limits for the DISCO Reporting API?

DISCO does not publish a precise per-second rate limit for the Reporting API; expected use is scheduled reporting rather than real-time polling. Run pulls on a daily or hourly cadence and treat 429 responses as a back-off signal.

How do I track DISCO review database growth through Jentic?

Search Jentic for 'pull DISCO review database size' and execute the loaded GET /metrics/metric-reviewdb-size operation. Jentic injects the disco-api-key and organization-id headers from the vault and returns the metric values for charting.

Is the DISCO Reporting API free?

API access is part of the customer's existing DISCO contract; there is no separate per-call fee. Contact CS DISCO for terms specific to your plan; details are available at https://csdisco.com.

How do I list every metric the API exposes?

Call GET /metrics to retrieve the catalogue of metrics, then call the corresponding /metrics/{metric}/metadata endpoint for each entry to discover its schema before pulling values.

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

Yes. Jentic One runs self-hosted, so your own rules decide which DISCO Reporting operations and credentials the agent can use. Because this surface is read-only and selects datasets and metrics by route, you can scope the agent to just the operations it needs, such as GET /datasets/data-usage-changes or GET /metrics/metric-reviewdb-size, and withhold the rest. The disco-api-key and organization-id are held by your own instance and added at execution time rather than exposed to the agent.

Csdisco DISCO Reporting API

Name: DISCO Reporting API
Brand: DISCO Reporting API
Availability: InStock

Community OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey6 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Pull DISCO ediscovery usage datasets and review database size metrics for finance and operations reporting.

Use for: I need to retrieve the data usage changes dataset for my DISCO organization, Get the review database size metric for the current matter, List every dataset available to my DISCO account, List every metric the DISCO Reporting API exposes

Not supported: Does not handle document review, legal hold management, or production exports - use for retrieving DISCO usage datasets and metrics only.

The DISCO Reporting API exposes datasets and metrics from CS DISCO's ediscovery platform so legal operations teams can pull usage and consumption data into their own reporting stack. The catalogued slice covers data usage change datasets and review database size metrics, each with a metadata endpoint that describes the available fields. Authentication uses two header API keys: disco-api-key for the user identity and organization-id for tenant scoping.

Jentic One on Github View OpenAPI Document