Install Jentic One Beta

Connect the Binated API to your agent

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

List, retrieve, and delete configured data sources for governance

Create dashboards on top of registered sources via POST /dashboards

Update dashboards in place with PATCH /dashboards/{dashboardId}

Generate point-in-time reports via POST /reports and retrieve them by ID

GET STARTED

Start building with Binated API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Binated API for, with concrete tasks.

★ Programmatic Dashboard Provisioning

Analytics teams onboarding new customers want each tenant to receive a starter dashboard built from their data source. The Binated API supports this with POST /datasources to register the source and POST /dashboards to create the dashboard, plus PATCH /dashboards/{dashboardId} to apply tenant-specific overrides. Setup is typically two days for the provisioning script.

Register a Postgres source via POST /datasources, then create a dashboard via POST /dashboards bound to that source ID and confirm via GET /dashboards/{dashboardId}.

Scheduled Report Generation

Operations and finance teams need point-in-time reports delivered on a schedule. The Binated API exposes POST /reports to generate and GET /reports/{reportId} to retrieve, which a cron-driven job can call once per period and forward to email or storage. Setup is half a day per report definition.

Generate a monthly revenue report via POST /reports with a fixed query against the configured source, then retrieve it via GET /reports/{reportId} and forward the result by email.

Embedded Analytics Query Layer

Product teams embedding analytics in their own UI need to run user-scoped queries against the data sources they have registered with Binated. POST /datasources/{sourceId}/query is the supported entry point, returning query results that the embedding application then renders. This separates query execution from rendering and keeps source credentials in Binated. Setup is typically two to three days for a first embed.

Send a SQL-shaped query against data source ID 42 via POST /datasources/{sourceId}/query and return the result rows for rendering in a customer-facing chart.

AI Agent Analyst via Jentic

An AI assistant for analytics teams can register sources, run queries, and produce reports from natural-language requests routed through Jentic. The bearer JWT is held in your Jentic One instance, so the assistant never sees the raw token. Search-load-execute through Jentic gets the assistant live in under an hour, versus several days for a direct integration.

Search Jentic for 'run a Binated query', load the POST /datasources/{sourceId}/query schema, and execute it against the configured source with the supplied query.

Key Endpoints

12 endpoints — jentic publishes the only available openapi specification for binated api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/datasources

POST

/datasources/{sourceId}/query

Run a query against a data source

GET

/datasources

List configured data sources

POST

/dashboards

Create a dashboard

PATCH

/dashboards/{dashboardId}

Update a dashboard

POST

/reports

Generate a report

GET

/reports/{reportId}

Retrieve a report by ID

POST

/datasources

POST

/datasources/{sourceId}/query

Run a query against a data source

GET

/datasources

List configured data sources

POST

/dashboards

Create a dashboard

PATCH

/dashboards/{dashboardId}

Update a dashboard

POST

/reports

Generate a report

GET

/reports/{reportId}

Retrieve a report by ID

Why Jentic?

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

Setup

Wiring the Binated API by hand means implementing its bearer-token auth, pointing at the api.binated.com/v1 host, and writing your own retry handling around data-source and dashboard calls. Through Jentic you install once, import Binated from the API Directory, store the token once, and your agent calls it.

Permission scoping

Binated puts the source id in the URL path (/datasources/{sourceId}/query), so a rule can pin your agent to one data source: it can query and read that source and nothing else. You choose the operations it may call, so dashboard edits like PATCH /dashboards/{dashboardId} are not included unless you add them.

Credential isolation

Your Binated bearer token 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 'run a Binated query' or 'create a dashboard', and Jentic returns the matching Binated operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Binated API through Jentic.

Why is there no official OpenAPI spec for Binated API?

Binated does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Binated API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Binated API use?

The Binated API uses HTTP bearer authentication with a JWT token. You supply the token as Authorization: Bearer <jwt>. When called via Jentic, the JWT is held in your Jentic One instance so the raw token never reaches the agent's context.

Can I run a query against a registered data source through the Binated API?

Yes. POST /datasources/{sourceId}/query runs a query against the named data source and returns the result. Sources are registered first via POST /datasources, then queried by their assigned source ID.

What are the rate limits for the Binated API?

The current spec does not declare explicit numeric rate limits. Treat 429 responses as the signal to back off, and call the Jentic SDK, which retries on 429 with exponential back-off so high-volume query jobs do not have to handle this manually.

How do I generate a Binated report through Jentic?

Search Jentic for 'generate a Binated report', which surfaces POST /reports. Load the schema, supply the report definition, and execute. Then retrieve the result via GET /reports/{reportId}. The Python flow is: pip install jentic, then await client.search, await client.load, await client.execute.

Can I update an existing dashboard?

Yes. PATCH /dashboards/{dashboardId} applies a partial update to a dashboard, leaving fields not present in the request unchanged. This is the supported pattern for tenant-specific overrides on a shared dashboard template.

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

Yes. Because you self-host Jentic One, your own rules decide which Binated operations and credentials the agent may use. Since the source ID sits in the path (POST /datasources/{sourceId}/query), you can pin the agent to a single data source so it can query and read that source and nothing else. You also choose the operations it may call, so dashboard edits like PATCH /dashboards/{dashboardId} and report generation via POST /reports are excluded unless you add them.

Binated API

Name: Binated API
Brand: Binated API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticAnalyticsBusiness Intelligencebearer12 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Connect data sources, run queries, and build dashboards and reports through the Binated business-intelligence platform.

Use for: I want to register a new data source in Binated, Run a query against a connected data source, List all dashboards I have access to, Generate a new report from a data source

Not supported: Does not handle ETL pipeline scheduling, user-permission management, or data-warehouse provisioning - use for registering data sources, querying them, and managing Binated dashboards and reports only.

Jentic publishes the only available OpenAPI specification for Binated API, keeping it validated and agent-ready. The Binated API is the programmatic interface to the Binated business-intelligence and data-analytics platform, exposing 12 endpoints to register data sources, query them, and manage dashboards and reports. It supports the standard BI loop: connect a source, run queries against it, build dashboards from the results, and generate point-in-time reports. Authentication is by HTTP bearer token in JWT format.

Jentic One on Github View OpenAPI Document

Connect the Binated API to your agent

Capabilities

Start building with Binated API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Binated API