canonical: https://jentic.com/apis/lvlupauto.com/lvlupauto

# LVL Up Auto Headless API

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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
- Report vendor performance metrics and read floored peer benchmarks by size, state, or national cohort
- Find same-category vendor alternatives that fit better on a chosen metric

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Vendors** — Canonical catalog of dealership software vendors, each with a metric schema
- **Stack** — The rooftop's own vendor list with cost, contract end, auto-renew, and notice period
- **Scans** — Domain technology scans polled by scan_id
- **Benchmarks and performance** — Dealer-reported metric values and floored peer benchmarks by cohort

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 70 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 81 / 100
  - Developer Experience & Jentic Compatibility: 66 / 100
  - AI-Readiness & Agent Experience: 57 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 82 / 100
- **View full report:** https://jentic.com/apis/lvlupauto.com/lvlupauto/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **BuiltWith** — General website technology lookup across any industry
- **Clearbit** — Company firmographic enrichment by domain

## FAQ

### 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.