Biron Nexus API

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

★ Only Publicly Available OpenAPI DocumentAnalyticsBusiness Intelligencebasic2 EndpointsREST

For Agents

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

Quickstart

Get started with Biron Nexus API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"run a nexusql query against the biron semantic layer"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Biron Nexus API 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 API

Explore with Jentic

View OpenAPI Document

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 document for Biron Nexus API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Biron Nexus API 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 the Jentic vault — 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 though Jentic?

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

Credential isolation

Biron HTTP Basic credentials are stored encrypted in the Jentic vault. Jentic builds the Authorization header at execution time, so agent prompts and logs never contain the password.

Intent-based discovery

Agents search by intent (e.g. 'run a nexusql query' or 'list metrics in a biron workspace') and Jentic returns the matching operation with its input and response schema.

Time to first call

Direct Biron integration: half a day to set up Basic auth, model the workspace lookup, and wire the /sql call. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Snowflake API

The cloud data warehouse that Biron's semantic layer commonly sits on top of.

Use Snowflake directly when the agent needs raw warehouse data; use Biron when it needs a modelled metric.

Alternative

The Graph

Decentralised query layer for indexed data — different domain (on-chain) but same query-against-modelled-data shape.

Choose The Graph for blockchain data and Biron for warehouse-modelled business metrics.

Complementary

RapidAPI

Marketplace useful for surfacing alternative analytics and BI APIs.

Use RapidAPI when an agent needs to compare Biron with other modelled-metric providers.

FAQs

Specific to using Biron Nexus API 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 at https://app.jentic.com/sign-up.

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.