Install Jentic One Beta

Connect the LVL Up Auto Headless API to your agent

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

Search the dealership vendor catalog by keyword, category, domain, or AI capability

Batch-resolve messy vendor names such as 'CDK Global, Inc.' to canonical catalog ids

Scan a dealer or competitor domain and poll the scan for detected vendors

Record stack vendors with monthly_cost, contract_end, and notice_period_days, then list renewals coming due

GET STARTED

Start building with LVL Up Auto Headless API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LVL Up Auto Headless API for, with concrete tasks.

★ AI agent auditing a dealership's vendor stack

An operations agent at a dealership group needs a clean inventory of the software each rooftop pays for. Through Jentic it searches for 'resolve vendor names', loads the LVL Up Auto resolve operation, and submits names exported from accounting, then adds each resolved vendor to the stack with its cost and contract end date. The bearer token is injected at call time and scopes every call to that rooftop.

Call POST /api/v1/vendors/resolve with names ['VinSol', 'vAuto'], then POST /api/v1/stack/vendors for each match with vendor_id, category, monthly_cost, and contract_end

Renewal deadline tracking

Auto-renewing software contracts are easy to miss when notice periods are short. The LVL Up Auto renewals endpoint lists upcoming contract renewals and their notice deadlines within a window set by the within_days parameter, using the contract_end, auto_renews, and notice_period_days recorded on each stack vendor. A scheduled check can flag a contract before its notice window closes.

Call GET /api/v1/renewals with within_days=60 and list each vendor whose notice deadline falls in the next two weeks

Competitor technology scanning

A dealer principal wants to know which website, chat, and inventory tools a nearby rival uses. LVL Up Auto runs a domain technology scan on request and returns results by scan id once processing finishes, and competitor rooftops can be declared by name and domain for ongoing comparison. This turns guesswork about a rival's stack into a detected vendor list.

Call POST /api/v1/scan with domain 'rivalauto.com', then poll GET /api/v1/scan/{scan_id} until it completes and summarise the detected vendors

Vendor performance benchmarking

Deciding whether to keep a vendor needs more than a gut feeling. A dealer reports metric values such as avg_response_time_min per vendor and period, then reads peer benchmarks by size, state, or national cohort; benchmarks are floored so no cohort smaller than five is shown. The alternatives endpoint then suggests same-category vendors that perform better on a chosen metric.

Call GET /api/v1/benchmarks with vendor_id, metric_key avg_response_time_min, and cohort state, then GET /api/v1/alternatives for the same metric_key

Key Endpoints

18 endpoints — the lvl up auto headless api maps and benchmarks the software vendor stack of a car dealership rooftop.

METHOD

PATH

DESCRIPTION

GET

/api/v1/vendors

Search the vendor catalog

POST

/api/v1/vendors/resolve

Batch-resolve vendor names

GET

/api/v1/stack

List the dealer's vendor stack

POST

/api/v1/stack/vendors

Add a vendor to the stack

POST

/api/v1/scan

Run a domain technology scan

GET

/api/v1/renewals

List upcoming renewals and notice deadlines

GET

/api/v1/benchmarks

Read floored peer benchmarks

GET

/api/v1/alternatives

Find same-category vendor alternatives

GET

/api/v1/vendors

Search the vendor catalog

POST

/api/v1/vendors/resolve

Batch-resolve vendor names

GET

/api/v1/stack

List the dealer's vendor stack

POST

/api/v1/stack/vendors

Add a vendor to the stack

POST

/api/v1/scan

Run a domain technology scan

GET

/api/v1/renewals

List upcoming renewals and notice deadlines

GET

/api/v1/benchmarks

Read floored peer benchmarks

GET

/api/v1/alternatives

Find same-category vendor alternatives

Why Jentic?

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

Setup

Wiring LVL Up Auto by hand means issuing a personal access token, sending it as a bearer header, and polling scans until they finish. Through Jentic you install once, import LVL Up Auto from the API Directory, store the token once, and your agent calls it.

Permission scoping

The token already confines calls to one rooftop, and stack vendors and scans carry their id in the URL path (/api/v1/stack/vendors/{id}, /api/v1/scan/{scan_id}), so a rule can pin your agent to one stack vendor or scan. You choose the operations it may call, so destructive ones like removing a stack vendor are not included unless you add them.

Credential isolation

Your LVL Up Auto 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 'scan a dealer website' or 'list upcoming renewals', and Jentic returns the matching LVL Up Auto operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using LVL Up Auto Headless API through Jentic.

What authentication does the LVL Up Auto Headless API use?

The LVL Up Auto Headless API authenticates with a personal access token sent as an HTTP bearer token in the Authorization header, per its OpenAPI spec, and every request is scoped to the token's single rooftop. Token-management endpoints use a browser session and are not part of this spec. Through Jentic the token is stored by your own instance and attached at call time.

Can I scan a dealership website with the LVL Up Auto API?

Yes. POST /api/v1/scan starts a domain technology scan for a domain such as exampledealer.com, and GET /api/v1/scan/{scan_id} polls it until the detected vendors are ready. Declared competitors from POST /api/v1/competitors give you rival rooftops to scan.

What are the rate limits for the LVL Up Auto Headless API?

The OpenAPI spec does not specify rate limits. Check the LVL Up Auto site at https://lvlupauto.com for current limits before scripting large resolve or scan batches.

Is there an LVL Up Auto MCP server?

You don't need an MCP server to give your agent LVL Up Auto. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the vendor, stack, and benchmark operations it needs, discovered on demand rather than loaded into its context up front.

How do I check upcoming renewals through Jentic?

Search Jentic for 'list upcoming contract renewals', load the GET /api/v1/renewals operation, and run it with within_days set to your window. 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 LVL Up Auto API?

Yes. For example, a rule that allows only GET /api/v1/stack, GET /api/v1/renewals, and GET /api/v1/benchmarks lets the agent review your stack, renewals, and benchmarks while it cannot remove a stack vendor or report performance values. Every call it makes is logged.

LVL Up Auto Headless API

AI ReadinessAI-Aware (B+)70/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentCompany Datahttp (bearer)18 EndpointsREST

For Agents

Search a catalog of dealership software vendors, scan dealer domains for their tech stack, track contracts and renewals, and compare vendor performance against peer benchmarks with LVL Up Auto.

Use for: Search for CRM vendors used by car dealerships, I need to resolve a list of vendor names from an invoice export, Scan a competitor dealership's website for its technology stack, List all contracts renewing in the next 60 days

Not supported: Does not sell vehicles, manage inventory listings, or process vendor invoices or payments. Use for dealership vendor catalog search, stack tracking, scans, and benchmarks only.

The LVL Up Auto Headless API maps and benchmarks the software vendor stack of a car dealership rooftop. It searches a canonical catalog of dealership vendors, batch-resolves messy vendor names to catalog ids, and scans a dealer domain to detect the technology running on it. A dealer can record each vendor in its stack with cost and contract terms, list upcoming renewals and notice deadlines, declare competitor rooftops, report performance metrics, and read peer benchmarks floored at a minimum cohort of five. Every request is scoped to the single rooftop tied to the personal access token.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

25%

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

13%

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

72%

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.

55%

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

82%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LVL Up Auto Headless API to your agent

Capabilities

Start building with LVL Up Auto Headless API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

LVL Up Auto Headless API

Jentic AI Readiness Score

LVL Up Auto Headless 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