Install Jentic One Beta

Connect the Biron Nexus API to your agent

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

Execute a NexusQL query against the configured semantic layer via POST /sql and receive a tabular result set

Read workspace metadata including available metrics and dimensions via GET /workspaces/{code}

Pull modelled KPIs without writing SQL against raw warehouse tables

Discover the canonical name of a metric before composing a downstream report

GET STARTED

Start building with Biron Nexus API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Biron Nexus API for, with concrete tasks.

★ Programmatic KPI retrieval for status reports

Operations teams pull weekly KPIs from the modelled semantic layer rather than querying raw warehouse tables. POST /sql accepts a NexusQL query and returns a tabular result that maps cleanly into a status-report template. Because the semantic layer enforces consistent metric definitions, two reports built by different teams converge on the same numbers.

POST /sql with a NexusQL query for weekly_active_users grouped by week for the last 12 weeks and render the result table

Workspace discovery before query composition

Analysts who switch between several Biron workspaces need to confirm the available metrics before they write a NexusQL query. GET /workspaces/{code} returns the workspace definition including the list of metrics and dimensions Biron has modelled. The two-step pattern (discover then query) avoids failed /sql calls caused by referencing a metric that has not been published.

Call GET /workspaces/revenue-ops, list the metric names, and return them to the analyst as a picklist

Agent integration via Jentic for self-serve analytics

An AI agent answering 'what was our revenue last quarter' resolves the question through Jentic. Jentic returns the Biron Nexus /sql operation along with the workspace schema, so the agent can compose a valid NexusQL query, execute it, and surface the result in chat. The HTTP Basic credentials remain in your Jentic One instance - the agent never holds them.

Search Jentic for 'run a nexusql query against biron', load the /sql schema, compose a query for revenue grouped by quarter, and return the result

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/sql

Execute a NexusQL query against the configured workspace

GET

/workspaces/{code}

Return workspace metadata including modelled metrics and dimensions

POST

/sql

Execute a NexusQL query against the configured workspace

GET

/workspaces/{code}

Return workspace metadata including modelled metrics and dimensions

Why Jentic?

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

Setup

Wiring the Biron Nexus API by hand means building the HTTP Basic Authorization header, targeting the nexus.biron-analytics.com host, and handling query errors yourself. Through Jentic you install once, import Biron Nexus from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Biron Nexus sends the query in the request body for /sql, so limit the agent to the operations it needs, such as running a NexusQL query or reading workspace metadata with /workspaces/{code}. You choose the operations it may call, so nothing beyond that set runs unless you add it.

Credential isolation

Your Biron Basic credentials are stored once, encrypted, by your own Jentic One instance, which builds the Authorization header and injects it at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'run a NexusQL query' or 'read a Biron workspace', and Jentic returns the matching operation with its input and response schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Biron Nexus API through Jentic.

Why is there no official OpenAPI spec for Biron Nexus API?

Biron does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Biron Nexus 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 Biron Nexus API use?

Biron Nexus uses HTTP Basic authentication. Clients send a username and password pair in the Authorization header on every request. Through Jentic the credential is held encrypted in the vault and injected at execution, so agents never see the password.

Can I list the metrics in a Biron workspace before querying?

Yes. GET /workspaces/{code} returns the workspace definition including the list of modelled metrics and dimensions. Call it once to populate a picklist, then issue POST /sql with a NexusQL query that references those names.

What are the rate limits for the Biron Nexus API?

Biron does not publish a numeric per-second rate limit in its specification. Treat /sql as a synchronous query against the underlying warehouse - long-running NexusQL queries occupy compute, so concurrency is bounded by the workspace's warehouse capacity rather than by an HTTP throttle.

How do I run a NexusQL query through Jentic?

Run pip install jentic, search Jentic for 'run a nexusql query against biron', load the /sql operation schema, and execute with a NexusQL string in the body. Jentic injects the Basic credentials and returns the tabular result.

Does the Biron Nexus API return raw warehouse data?

No. /sql executes NexusQL against the modelled semantic layer, not against raw warehouse tables. Use the workspace endpoint to discover the modelled metric and dimension names that NexusQL accepts.

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

Yes. Because you run Jentic One yourself, your own rules decide which Biron Nexus operations the agent may call, so you can allow only running a NexusQL query via POST /sql, only reading workspace metadata via GET /workspaces/{code}, or both. Anything outside the operation set you grant never runs unless you add it. Your HTTP Basic credentials stay in your own Jentic One instance and are injected at execution, so the agent scopes what it can reach without ever holding the password.

Biron Analytics Biron Nexus API

Name: Biron Nexus API
Brand: Biron Nexus API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticAnalyticsBusiness Intelligencebasic2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Run NexusQL queries against a Biron semantic layer and read workspace metadata to discover available metrics. Two endpoints, HTTP Basic authentication.

Use for: Run a NexusQL query that returns weekly active users for the last 12 weeks, List the metrics available in the workspace with code revenue-ops, Get the schema of a Biron workspace before composing a query, Retrieve the daily revenue figure modelled in our Biron semantic layer

Not supported: Does not provision warehouses, run ETL jobs, or manage user permissions - use for executing NexusQL queries and reading workspace metadata only.

Jentic publishes the only available OpenAPI specification for Biron Nexus API, keeping it validated and agent-ready. Biron is a data platform that ships an ETL stack and a semantic layer on top of the customer's warehouse. The Nexus API is the programmatic surface to that semantic layer: clients submit NexusQL queries, which Biron compiles against the modelled metrics and dimensions, and the API returns tabular result sets. A second endpoint reads workspace metadata so callers know which datasets and metrics are available before composing a query.

Jentic One on Github View OpenAPI Document