Install Jentic One Beta

Connect the Biza HaaS Data Adapter API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Biza HaaS Data Adapter 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%2Fbiza.io%2Fbiza" | 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%2Fbiza.io%2Fbiza" | 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 Biza HaaS Data Adapter API.

Retrieve a banking customer's accounts and transactions

List a customer's registered payees and payments

Read a customer's energy accounts and balances

Pull energy invoices, billing, and payment schedules

Look up energy account concessions for a customer

GET STARTED

Start building with Biza HaaS Data Adapter API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Biza HaaS Data Adapter API for, with concrete tasks.

★ AI agent CDR data access

An AI agent in a lending or budgeting workflow can read a consented customer's banking data on demand. Through Jentic the agent searches by intent and the API key and OAuth token never enter its prompt context, turning Biza's Consumer Data Right adapter into a programmable data feed.

Use Jentic to search 'get a customer's bank accounts', call GET /banking/customer/{principalId}/account, then GET /banking/customer/{principalId}/account/{accountId}/transaction to read recent transactions.

Energy account monitoring

A retail-energy assistant tracks a customer's balance and invoices across their energy accounts. The agent reads the outstanding balance and the latest invoices for a principal, surfacing bills and payment status without a manual portal login.

For a principal, call GET /energy/{principalId}/balance and GET /energy/{principalId}/invoice to report the outstanding balance and latest invoices.

Payee and payment review

A reconciliation agent compares a customer's registered payees against their recent payments to flag anomalies. Both lists come from the banking data adapter scoped to a single principal, keeping the review grounded in consented CDR data.

Call GET /banking/customer/{principalId}/payee and GET /banking/customer/{principalId}/payment to reconcile a customer's payees against recent payments.

Principal lifecycle management

Before data can be read, a customer principal must exist and carry the right attributes. An agent registers the principal, sets its attributes, and can list closed principals to keep the consented population current.

Register a principal via POST /user/principal, set attributes with POST /user/attribute, and list closed principals via GET /status/closed-principals.

Key Endpoints

23 endpoints — the biza haas data adapter api exposes consumer data right banking and energy data for a customer principal.

METHOD

PATH

DESCRIPTION

GET

/banking/customer/{principalId}/account

List a customer's bank accounts

GET

/banking/customer/{principalId}/account/{accountId}/transaction

List transactions on a bank account

GET

/banking/customer/{principalId}/payee

List registered payees

GET

/energy/{principalId}/account

List a customer's energy accounts

GET

/energy/{principalId}/balance

Read an energy account balance

GET

/energy/{principalId}/invoice

List energy invoices

GET

/customer/{principalId}

Get a customer by principal id

POST

/user/principal

GET

/banking/customer/{principalId}/account

List a customer's bank accounts

GET

/banking/customer/{principalId}/account/{accountId}/transaction

List transactions on a bank account

GET

/banking/customer/{principalId}/payee

List registered payees

GET

/energy/{principalId}/account

List a customer's energy accounts

GET

/energy/{principalId}/balance

Read an energy account balance

GET

/energy/{principalId}/invoice

List energy invoices

GET

/customer/{principalId}

Get a customer by principal id

POST

/user/principal

Why Jentic?

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

Setup

Wiring the Biza HaaS Data Adapter API by hand means carrying its API-Key header and exchanging an OAuth 2.0 client-credentials token for the biza:haas.adapter:read scope, then encoding the banking and energy calls yourself. Through Jentic you install once, import it from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The API puts the customer principal id in the URL path (/banking/customer/{principalId}/account, /energy/{principalId}/balance), so a rule can pin your agent to one customer. You choose the operations it may call, so principal registration or notification sends are not included unless you add them.

Credential isolation

Your Biza API key and OAuth credentials 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 'get a customer's bank accounts' or 'read an energy balance', and Jentic returns the matching Biza operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Biza HaaS Data Adapter API through Jentic.

Is there a Biza HaaS Data Adapter API MCP server?

You don't need an MCP server to give your agent Biza. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent calls the banking and energy read operations. That keeps your agent's context free of an extra server's tool definitions.

What authentication does the Biza HaaS Data Adapter API use?

It authenticates two ways per its OpenAPI spec: an API key in the API-Key header and an OAuth 2.0 client-credentials token carrying the biza:haas.adapter:read scope. Through Jentic both are stored encrypted by your own instance and injected at call time.

Can I read a customer's bank transactions with the Biza HaaS Data Adapter API?

Yes. GET /banking/customer/{principalId}/account lists a customer's accounts, and GET /banking/customer/{principalId}/account/{accountId}/transaction returns the transactions on a given account, both scoped to one consented principal.

Can I access energy account data through this API?

Yes. GET /energy/{principalId}/account lists a customer's energy accounts, and GET /energy/{principalId}/balance and GET /energy/{principalId}/invoice return the current balance and invoices for that principal.

How do I read a customer's accounts through Jentic?

Search Jentic for 'get a customer's bank accounts', load the input schema, and execute GET /banking/customer/{principalId}/account. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Biza HaaS Data Adapter API?

Yes. Write a rule that allows only the banking read operations under one principal id, so the agent can list that customer's accounts and transactions and touch nothing else, and every call it makes is logged. Energy and principal-management operations stay out unless you add them.

Biza HaaS Data Adapter API

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Community OpenAPI document · agent-readyFinanceBankingapiKey, oauth223 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Read a customer principal's Consumer Data Right banking and energy data through Biza's data holder adapter: bank accounts, transactions, payees, energy balances, invoices, and billing.

Use for: Get the bank accounts for a customer principal, List transactions on a customer's bank account, Retrieve a customer's energy account balance, Pull the latest energy invoices for a principal

Not supported: Does not initiate payments, open accounts, or switch energy providers. Use for reading Consumer Data Right banking and energy data for a customer principal only.

The Biza HaaS Data Adapter API exposes Consumer Data Right banking and energy data for a customer principal. It reads a customer's bank accounts, transactions, payees, and payments, and pulls their energy accounts, balances, invoices, billing, and concessions. It also registers and manages the customer principal that ties those data requests to a consented consumer.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

46%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: CSignals: 4

75%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B+Signals: 1

68%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Biza HaaS Data Adapter API to your agent

Capabilities

Start building with Biza HaaS Data Adapter API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Biza HaaS Data Adapter API

Jentic AI Readiness Score

HaaS Data Adapter API Secure (OpenAPI Client)

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness