Binated API

Name: Binated API
Brand: Binated API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness Intelligencebearer12 EndpointsREST

For Agents

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

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://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 Binated API.

List, retrieve, and delete configured data sources for governance

Create dashboards on top of registered sources via POST /dashboards

GET STARTED

Start building with Binated API

Explore with Jentic

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 the Jentic vault, 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

Why Jentic?

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

Credential isolation

Binated JWT bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — the raw JWT never enters the agent's context or logs.

Intent-based discovery

Agents search by intent (e.g., 'run a Binated query') and Jentic returns the matching Binated operation with its input schema, so the agent can call POST /datasources/{sourceId}/query without browsing third-party docs.

Time to first call

Direct Binated integration: 1-3 days for source registration, querying, and dashboard provisioning. Through Jentic: under 1 hour — search, load schema, execute.

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 at https://app.jentic.com/sign-up.

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 the MAXsystem vault 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.

Binated API

Connect the Binated API to your agent

Capabilities

Start building with Binated API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs