Install Jentic One Beta

Connect the Ultimeter API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ultimeter 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%2Fultimeter.app%2Fultimeter" | 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%2Fultimeter.app%2Fultimeter" | 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 Ultimeter API.

Create a new Ultimeter

Returns a list of published Ultimeters

Update an Ultimeter

Query and filter Ultimeter API records by parameters

Monitor Ultimeter API operational status and events

GET STARTED

Start building with Ultimeter API

Explore with Jentic One

View OpenAPI Document

Automated Meters Management

Automate meters operations by combining multiple Ultimeter API endpoints. Agents can returns a list of published ultimeters and then returns a single published ultimeter in a single workflow.

Call GET /meters to returns a list of published ultimeters, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Ultimeter API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'create a new ultimeter', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

4 endpoints — introduction this page contains the documentation on how to use ultimeter through api calls.

METHOD

PATH

DESCRIPTION

POST

/meters

Create a new Ultimeter

GET

/meters

Returns a list of published Ultimeters

GET

/meters/{id}

Returns a single published Ultimeter

PUT

/meters/{id}

Update an Ultimeter

POST

/meters

Create a new Ultimeter

GET

/meters

Returns a list of published Ultimeters

GET

/meters/{id}

Returns a single published Ultimeter

PUT

/meters/{id}

Update an Ultimeter

Why Jentic?

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

Setup

Wiring the Ultimeter API by hand means sending HTTP basic credentials on every call, resolving your WordPress server host for the /wp-json path, and matching each meter operation to its request shape yourself. Through Jentic you install once, import the Ultimeter API from the API Directory, store the basic credential once, and your agent calls it.

Permission scoping

Ultimeter puts the meter id in the URL path (/meters/{id}), so a rule can pin your agent to one meter: it can read and update that meter and nothing else. You choose the operations it may call, so creating new meters is not included unless you add it.

Credential isolation

Your Ultimeter basic credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a new meter' or 'read a meter', and Jentic returns the matching Ultimeter operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Ultimeter API through Jentic.

What authentication does the Ultimeter API use?

The Ultimeter API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create a new ultimeter with the Ultimeter API?

Yes. Use the POST /meters endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Ultimeter API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create a new ultimeter through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new ultimeter'. Jentic returns the matching Ultimeter API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Ultimeter API have?

The Ultimeter API exposes 4 endpoints covering meters operations.

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

Yes. Because you run Jentic One yourself and set its rules, you decide which Ultimeter operations your agent may call and which basic credential it uses. Since the Ultimeter API puts the meter id in the URL path (/meters/{id}), you can pin the agent to a single meter so it only reads (GET /meters/{id}) and updates (PUT /meters/{id}) that one record. Creating meters with POST /meters or listing all meters with GET /meters stays off unless you explicitly grant those operations.

Ultimeter App Ultimeter API

AI ReadinessNon-Ready (F)34/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact Managementbasic4 EndpointsREST

For Agents

Programmatically create a new ultimeter, returns a list of published ultimeters. Covers 4 operations with basic authentication.

Use for: I need to a new ultimeter, I want to returns a list of published ultimeters, Search for returns a single published ultimeter, Find all an ultimeter

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

Introduction This page contains the documentation on how to use Ultimeter through API calls. > Note: This documentation is not complete, so for missing parts you may choose to get in contact with us [here](mailto:support@bouncingsprout.com) The Ultimeter API is built on HTTP. Our API is RESTful. It has predictable resource URLs. It returns HTTP response codes to indicate errors. It also accepts an. The API exposes 4 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

84%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

12%

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

16%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

25%

OperationId Quality

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

67%

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

10%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Ultimeter API to your agent

Capabilities

Start building with Ultimeter API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Ultimeter App Ultimeter API

Jentic AI Readiness Score

Ultimeter 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