Install Jentic One Beta

Connect the Liquid Retail ZW API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Liquid Retail ZW 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%2Fliquidhome.tech%2Fliquidhome" | 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%2Fliquidhome.tech%2Fliquidhome" | 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 Liquid Retail ZW API.

Sign a customer in with username and password to get a bearer token

Read a customer's profile with currentBalance, billingCurrency, and services including quota, quotaUsage, and topUpExpiry

List bills with number, total, owing, dueDate, paidDate, and a pdfUrl for each invoice

Check data usage broken down into received, transmitted, and total

GET STARTED

Start building with Liquid Retail ZW API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Liquid Retail ZW API for, with concrete tasks.

★ Agent-run account check-ins through Jentic

A personal assistant agent can answer a Liquid Home customer's account questions: it reads the profile for the current balance and service quotas, lists bills to find what is owing and when it is due, and checks data usage. Through Jentic the agent finds each operation by intent and loads its schema, while the customer's sign-in credentials stay out of its context.

Get the profile and report currentBalance with billingCurrency, then list bills and return the number, owing amount, and dueDate of any bill without a paidDate.

Bill tracking and reminders

Each bill carries its number, total, amount owing, currency, bill date, due date, paid date, and a PDF link, so an agent can remind a customer before a due date, confirm when a bill is paid, and fetch the invoice PDF for records.

List bills, find the most recent by billDate, and return its total, owing, dueDate, and pdfUrl.

Data usage monitoring

The usage operation reports data received, transmitted, and total, and the profile's services show quota, quotaTotal, quotaUsage, and any top-up with its expiry, so an agent can warn a customer when they are close to their quota.

Fetch usage and the profile, then compare quotaUsage with quotaTotal for each service and flag any service that is close to its quotaTotal.

Key Endpoints

7 endpoints — the liquid retail zw api backs the liquid home customer app in zimbabwe: it signs a customer in, returns their profile with current balance, billing currency, and subscribed services with quota and top-up details, and lists their bills with totals, amounts owing, due and paid dates, and pdf links.

METHOD

PATH

DESCRIPTION

POST

/auth/sign-in

GET

/auth/profile

Get the customer profile

GET

/account/bills

List bills

GET

/usage

Get data usage

GET

/news

List news articles

POST

/auth/sign-in

GET

/auth/profile

Get the customer profile

GET

/account/bills

List bills

GET

/usage

Get data usage

GET

/news

List news articles

Why Jentic?

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

Setup

Wiring the Liquid Retail ZW API by hand means signing in with a username and password, holding the returned bearer token, and attaching it to each account call. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.

Permission scoping

The Liquid Retail ZW API has no resource ids in its paths: each call reads the signed-in customer's own account, so rules bound which operations your agent may call. You choose the operations it may call, so ones like reading the full profile are not included unless you add them.

Credential isolation

Your Liquid Home 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 'check my internet bill' or 'get data usage', and Jentic returns the matching Liquid Retail ZW operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Liquid Retail ZW API through Jentic.

What authentication does the Liquid Retail ZW API use?

Per its OpenAPI spec the Liquid Retail ZW API uses HTTP bearer authentication. The sign-in operation takes a username and password and returns a token, which you then send in the Authorization header. Through Jentic the credentials are stored encrypted by your own Jentic One instance and injected at request time.

Is there a Liquid Home MCP server?

You don't need an MCP server to give your agent the Liquid Retail ZW API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the profile, bills, and usage operations on demand.

Can I download my bills with the Liquid Retail ZW API?

Yes. The bills operation returns each bill's billKey, number, total, owing, currency, billDate, dueDate, paidDate, and a pdfUrl you can open to get the invoice document.

What are the rate limits for the Liquid Retail ZW API?

The OpenAPI spec does not specify rate limits. Check with Liquid Home at https://liquidhome.tech for current limits.

Can I limit what my agent is allowed to do with the Liquid Retail ZW API?

Yes. For example, allow only the bills and usage operations, so the agent can answer billing and data questions without reading the full profile, which holds the customer's birth date and mobile number. Every call it makes is logged.

How do I check my Liquid Home data usage through Jentic?

Search Jentic for 'check home internet data usage', load the usage operation, and call it; it returns received, transmitted, and total figures. Jentic injects the bearer token at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Liquidhome Tech Liquid Retail ZW API

AI ReadinessFoundational (C)54/100

See full scorecard

Community OpenAPI document · agent-readyPaymentsBilling Subscriptionsbearer7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Sign a Liquid Home Zimbabwe customer in, read their balance, services, and bills, and check data usage, news, banners, and legal links.

Use for: I need to check how much I owe on my Liquid Home account, Get my latest bill as a PDF, Check whether my last bill was paid, How much data have I used

Not supported: Does not take payments, change service plans, or buy top-ups. Use for reading a Liquid Home customer's profile, bills, and data usage only.

The Liquid Retail ZW API backs the Liquid Home customer app in Zimbabwe: it signs a customer in, returns their profile with current balance, billing currency, and subscribed services with quota and top-up details, and lists their bills with totals, amounts owing, due and paid dates, and PDF links. It also reports data usage as received, transmitted, and total figures, and serves the app's news articles, promotional banners, and legal documents.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

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

41%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

39%

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: FSignals: 4

17%

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.

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

60%

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: C-Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Liquid Retail ZW API to your agent

Capabilities

Start building with Liquid Retail ZW API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Liquidhome Tech Liquid Retail ZW API

Jentic AI Readiness Score

Liquid Retail ZW API

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