Install Jentic One Beta

Connect the Bouncie API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bouncie 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%2Fapi.bouncie.dev%2Fbouncie" | 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%2Fapi.bouncie.dev%2Fbouncie" | 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 Bouncie API.

List connected vehicles and the authenticated user

Retrieve trips with location and driving data

Create, update, and delete webhook subscriptions

Manage application and user geozones

Create, update, and delete saved locations

GET STARTED

Start building with Bouncie API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Bouncie API for, with concrete tasks.

★ Vehicle Trip Monitoring

A fleet or personal-tracking agent reads trips for connected vehicles to summarize mileage and driving behavior. It lists the vehicles, then retrieves their trips with location and driving data. Through Jentic the agent finds the trips operation and calls it with its OAuth token managed for it.

List connected vehicles and retrieve their recent trips with location data

Geozone Entry and Exit Alerts

A safety agent sets up geozones and is notified when a vehicle enters or leaves them. It creates the geozones and a webhook subscription so events are pushed as they happen. This backs curfew or worksite alerts without polling.

Create a geozone and a webhook so the agent is notified on entry and exit events

Event-Driven Vehicle Automations

An automation agent subscribes to Bouncie webhooks to react to vehicle events in real time. It creates, updates, and removes webhook subscriptions as its automations change. Pushed events let downstream systems respond without repeated calls.

Create a webhook subscription for vehicle events and update it as automations change

Location and Schedule Management

An agent maintains saved locations and schedules tied to a vehicle account. It creates, updates, and deletes locations and schedules to keep configurations current. This supports reminders and place-based logic in a connected-car app.

Create a saved location and a schedule, then update them as the account changes

Key Endpoints

23 endpoints — the bouncie api provides connected-vehicle telematics for cars fitted with a bouncie device.

METHOD

PATH

DESCRIPTION

GET

/v1/vehicles

List connected vehicles

GET

/v1/trips

Retrieve trips with location and driving data

GET

/v1/user

Get the authenticated user

POST

/v1/webhooks

Create a webhook subscription

GET

/v1/application-geozones/

List application geozones

POST

/v1/locations/

Create a saved location

GET

/v1/schedules/

List schedules

GET

/v1/vehicles

List connected vehicles

GET

/v1/trips

Retrieve trips with location and driving data

GET

/v1/user

Get the authenticated user

POST

/v1/webhooks

Create a webhook subscription

GET

/v1/application-geozones/

List application geozones

POST

/v1/locations/

Create a saved location

GET

/v1/schedules/

List schedules

Why Jentic?

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

Setup

Wiring Bouncie by hand means running its OAuth 2.0 flow against api.bouncie.dev, refreshing the token, and threading it through every trips and webhook call yourself. Through Jentic you install once, import Bouncie from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Bouncie mixes read and write operations, so a rule limits your agent to the operations it needs, such as listing vehicles and reading trips. You choose which operations it may call, so creating webhooks, geozones, or schedules is included only when you add it.

Credential isolation

Your Bouncie OAuth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'retrieve vehicle trips' or 'create a geozone', and Jentic returns the matching Bouncie operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Bouncie API through Jentic.

What authentication does the Bouncie API use?

The Bouncie API authenticates with OAuth 2.0, and the resulting access token is sent in the Authorization header. Through Jentic, that token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.

What vehicle data can the Bouncie API return?

The Bouncie API lists connected vehicles and returns trips with location and driving data. An agent can list the vehicles on an account and then retrieve their trips to summarize mileage, routes, and driving behavior.

Can I receive real-time vehicle events from the Bouncie API?

Yes. The Bouncie API supports webhook subscriptions, so an agent can create a webhook and receive vehicle events, including geozone entry and exit, as they happen. Subscriptions can be updated or removed as your automations change.

What are the rate limits for the Bouncie API?

The OpenAPI spec does not specify rate limits for the Bouncie API. Check the Bouncie developer documentation at https://docs.bouncie.dev for current limits, and back off when you receive a 429 response.

How do I read vehicle trips through Jentic?

Search Jentic for 'retrieve vehicle trips', import Bouncie from the API Directory, and store your OAuth credentials once. Jentic returns the trips operation with its parameters so your agent can call it directly. 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 Bouncie API?

Yes. You write a rule that allows only the operations the agent needs, such as listing vehicles and reading trips, so writing webhooks, geozones, or schedules stays out of reach unless you add it. Because Jentic One is self-hosted, those rules and the audit log of every call stay on your own infrastructure.

Is there a Bouncie API MCP server?

You do not need an MCP server to give your agent the Bouncie API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent can read trips and manage webhooks and geozones. That also keeps your agent's context free of an extra server's tool definitions.

Bouncie API

AI ReadinessFoundational (C)56/100

See full scorecard

Official vendor OpenAPI document · agent-readyIOTSensor Dataoauth223 EndpointsREST

For Agents

List connected vehicles, read trips with GPS and driving data, manage webhooks and geozones, and configure locations and schedules for Bouncie devices.

Use for: I want to list the connected vehicles, Retrieve recent trips for my vehicles, Create a webhook to receive vehicle events, Set up a geozone for a vehicle

Not supported: Covers Bouncie connected-vehicle data and its geozone, webhook, location, and schedule configuration. Does not control the vehicle or cover cars without a Bouncie device.

The Bouncie API provides connected-vehicle telematics for cars fitted with a Bouncie device. It lists vehicles and the authenticated user and returns trips with location and driving data. Beyond reading vehicle data, it manages webhook subscriptions for real-time events, application and user geozones, saved locations, and schedules. Read and write operations let an agent both monitor a vehicle and configure the alerts and automations around it.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

93%

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

21%

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

42%

Example Density

How richly the API is illustrated with examples.

96%

Example Validity

Percentage of examples that conform to their schemas.

42%

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

62%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

58%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

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 Bouncie API to your agent

Capabilities

Start building with Bouncie API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Bouncie API

Jentic AI Readiness Score

Bouncie 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