canonical: https://jentic.com/apis/swaggerhub.dacardona1/automotora-api

# Dacardona1 Auto Dealer API

An auto dealer branch management API. The API exposes 2 endpoints.

## For AI agents

Programmatically access Auto Dealer API resources. Covers 2 operations.

## Scope

Does not handle payments, communications, or crm - use for auto dealer management only.

## Capabilities

- Access Auto Dealer API resources via REST API
- Manage auto dealer data programmatically
- Integrate Auto Dealer API into automated workflows
- Query and filter Auto Dealer API records by parameters
- Monitor Auto Dealer API operational status and events

## Use cases

### Auto Dealer Operations

Use the Auto Dealer API to perform dealer operations programmatically. The API provides 2 endpoints covering core functionality including adding a new branch, listing branches.

Example prompt: Execute a primary operation against the Auto Dealer API

### Data Retrieval and Monitoring

Query Auto Dealer API resources on a schedule to track changes, generate alerts, or feed downstream dashboards.

Example prompt: Poll the primary Auto Dealer API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call Auto Dealer API endpoints through Jentic without managing credentials directly.

Example prompt: Search Jentic for 'auto dealer API', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/sucursal` | Add a new branch |
| GET | `/sucursal` | List branches |

## Key resources

- **admins** — Secured Admin-only calls
- **developers** — Operations available to regular developers
- **Third Parties** — Operations related to third parties

## Why Jentic

- **Setup:** Wiring the Auto Dealer API by hand means resolving its SwaggerHub host, shaping the branch create and list calls, and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the Auto Dealer API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** The Auto Dealer API works against a /sucursal collection rather than per-resource paths, so scope by operation: limit the agent to what it needs, such as listing branches, and leave out branch creation unless you want it to add records. The agent only ever runs the operations you include.
- **Credential handling:** This API needs no credentials, so there is nothing for the agent to hold. If a call ever required a secret, your own Jentic One instance would store it once, encrypted, and inject it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list dealer branches' or 'add a branch', and Jentic returns the matching Auto Dealer API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Auto Dealer API use?

The Auto Dealer API uses none authentication. 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.

### What are the rate limits for the Auto Dealer 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 use auto dealer API through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use auto dealer API'. Jentic returns the matching Auto Dealer API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Auto Dealer API have?

The Auto Dealer API exposes 2 endpoints covering branch management operations.

### Does the Auto Dealer API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

### Can I limit what my agent is allowed to do with the Auto Dealer API?

Yes. Because you run Jentic One yourself, your own rules decide which of the Auto Dealer API's operations the agent may call. Since the API works against a shared /sucursal collection rather than per-resource paths, you scope by operation: allow the agent to list branches with GET /sucursal while leaving out the POST /sucursal call that creates a branch, so it can read records without adding new ones. The agent only ever runs the operations you include.