Install Jentic One Beta

Connect the Ekho API to your agent

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

Browse dealer inventory and retrieve individual inventory units

Build carts from in-stock inventory or as build-to-order configurations

Retrieve orders with their vehicles and per-vehicle action items

Track preorders and cancel a preorder

List sales leads and add or remove dealer locations

GET STARTED

Start building with Ekho API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Ekho API for, with concrete tasks.

★ Agent-assisted vehicle ordering

A buying agent browses dealer inventory through Ekho, builds a cart from an in-stock unit or starts a build-to-order configuration, and then tracks the resulting order and its vehicles. Each operation is discovered through Jentic by intent, so the agent moves from inventory to cart to order without reading the reference docs.

Find an in-stock vehicle in inventory, create a cart from it, then retrieve the resulting order and its vehicles

Inventory and catalog browsing

An agent surfaces available vehicles by listing dealer inventory and drilling into a specific inventory unit or a catalog vehicle by its manufacturer, model, variant, and style. This lets a shopping assistant answer availability and specification questions against live dealer data.

List current inventory, then retrieve a specific inventory unit and its matching catalog vehicle details

Order and action-item tracking

Keep an order moving by reading its vehicles and the action items attached to each one, then completing action items as they are resolved. An agent can monitor outstanding steps on an ordered vehicle and mark them done so the order progresses.

Retrieve an order's vehicles, list the action items on one vehicle, and complete an action item that is ready

Webhook delivery and replay

Keep downstream systems in sync by registering event destinations, listing events, and replaying any event that failed to deliver. An agent can also rotate a destination's signing secret so webhook verification stays current.

Key Endpoints

27 endpoints — the ekho api runs vehicle commerce for dealers, covering inventory, carts, orders, and the vehicles on each order.

METHOD

PATH

DESCRIPTION

GET

/inventory

List dealer inventory

GET

/inventory/{item}

Retrieve an inventory unit

GET

/orders/{order}

Retrieve an order

GET

/orders/{order}/vehicles

List an order's vehicles

POST

/carts/inventory

Create a cart from inventory

POST

/carts/build-to-order

Create a build-to-order cart

GET

/preorders

List preorders

GET

/events

List events

GET

/inventory

List dealer inventory

GET

/inventory/{item}

Retrieve an inventory unit

GET

/orders/{order}

Retrieve an order

GET

/orders/{order}/vehicles

List an order's vehicles

POST

/carts/inventory

Create a cart from inventory

POST

/carts/build-to-order

Create a build-to-order cart

GET

/preorders

List preorders

GET

/events

List events

Why Jentic?

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

Setup

Wiring the Ekho API by hand means handling its scoped bearer token (shaped ekho_{env}_{hex}), choosing the production or staging host, and sequencing inventory, cart, and order calls yourself. Through Jentic you install once, import the Ekho API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Ekho puts the order id in the URL path (/orders/{order}), so a rule can pin your agent to one order and the operations you pick. You choose the operations it may call, so write actions like removing a location or deleting an event destination are not included unless you add them.

Credential isolation

Your Ekho token 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 'list dealer inventory' or 'create a build-to-order cart', and Jentic returns the matching Ekho operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Ekho API through Jentic.

What authentication does the Ekho API use?

The Ekho API authenticates with a scoped bearer token shaped ekho_{env}_{hex} per its OpenAPI spec. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Can I browse dealer inventory with the Ekho API?

Yes. The inventory operations list available units and retrieve a single inventory unit, and the catalog operation returns a specific vehicle by its manufacturer, model, variant, and style for specification details.

What are the rate limits for the Ekho API?

The OpenAPI spec does not state request rate limits. Check the Ekho documentation at https://api.ekho.com for current limits and any per-endpoint quotas.

Is there an Ekho MCP server?

You don't need an MCP server to give your agent the Ekho API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the inventory, cart, and order operations it needs.

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

Yes. Because Ekho carries the order id in the URL path, you can pin a rule to one order and allow only read operations, so the agent can track that order's vehicles and action items but cannot create carts, remove locations, or delete event destinations unless you add those operations. Every call the agent makes is logged.

How do I create a cart through Jentic?

Search Jentic for 'create a build-to-order cart', and it returns the matching Ekho cart operation with its input schema; your agent supplies the configuration and calls it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Ekho API

AI ReadinessAI-Aware (A-)70/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceOrder Managementbearer27 EndpointsREST

For Agents

Run dealer vehicle commerce: browse inventory and the catalog, build in-stock or build-to-order carts, retrieve orders with their vehicles and action items, track preorders and leads, and manage locations and webhook event destinations.

Use for: List the vehicles in dealer inventory, Retrieve a specific order and its vehicles, Create a cart from an in-stock vehicle, Start a build-to-order cart

Not supported: Does not handle payment capture, financing, or dealer accounting. Use for vehicle inventory, carts, and order management only.

The Ekho API runs vehicle commerce for dealers, covering inventory, carts, orders, and the vehicles on each order. An agent browses inventory and the vehicle catalog, builds carts from in-stock units or as build-to-order configurations, retrieves orders with their vehicles and per-vehicle action items, and tracks preorders and sales leads. It also manages dealer locations and lets you register event destinations and replay delivered webhook events.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

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

25%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: D+Signals: 4

49%

Description Coverage

Coverage of descriptions across API elements.

100%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

44%

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

88%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Ekho API to your agent

Capabilities

Start building with Ekho API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Ekho API

Jentic AI Readiness Score

Ekho 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