JCDecaux Bike API

Name: JCDecaux Bike API
Brand: JCDecaux Bike API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces SearchapiKey3 EndpointsREST

For Agents

Read live JCDecaux bike-share data: list contracts (cities), list all stations for a contract, and fetch real-time availability for any station by number.

Install Jentic One Beta

Connect the JCDecaux Bike API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the JCDecaux Bike 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 JCDecaux Bike API.

List every JCDecaux bike-share contract (city/region) available worldwide via /contracts

Retrieve real-time bike and stand availability for all stations in a contract via /stations

Fetch a single station's live status, coordinates, and stand counts by station number

GET STARTED

Start building with JCDecaux Bike API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for JCDecaux Bike API, keeping it validated and agent-ready. The JCDecaux Bike API exposes real-time data for the JCDecaux self-service bicycle network, covering contracts (cities and regions), individual stations, and live availability of bikes and stands. Each station response includes geographic coordinates, total stand count, available bikes, available empty stands, banking-enabled status, and a last-update timestamp, so applications can render maps, plan routes, or alert users when a station is full or empty. Authentication uses a single apiKey query parameter issued from the JCDecaux developer portal.

Use Cases

Patterns agents use JCDecaux Bike API for, with concrete tasks.

★ City Bike Availability Map

Power a public-facing map that shows every JCDecaux station in a city with live bike and empty-stand counts. The /stations endpoint returns coordinates, status, and stand totals in one call, refreshed roughly every minute by JCDecaux. A typical city covers 100-1,500 stations, so a single polled request keeps the map current without any per-station calls.

Call GET /stations with contract=Paris and return only stations where available_bikes > 0 sorted by distance from a given lat/long.

Trip Planning and Last-Mile Routing

A journey-planner can call /stations/{station_number} immediately before suggesting a station to confirm there are bikes to pick up at the origin and empty stands to drop at the destination. Because availability changes minute-to-minute, this just-in-time check prevents routing users to stations that have just emptied or filled.

Given an origin and destination station number, call GET /stations/{station_number} for both and return a route only if origin has available_bikes >= 1 and destination has available_bike_stands >= 1.

Coverage and Expansion Analytics

Researchers and city planners can query /contracts to enumerate every JCDecaux deployment globally, then drill into /stations per contract to compute fleet size, density, and banking-station ratios. This is useful for benchmarking shared-mobility coverage across cities without scraping public dashboards.

Call GET /contracts, then for each contract name call GET /stations?contract={name} and report the total station count and the percentage with banking=true.

AI Agent Integration via Jentic

An AI travel or commute assistant uses Jentic to discover JCDecaux operations by intent. The agent calls Jentic search with 'find available bike stations' and Jentic returns the JCDecaux operation schema with the apiKey parameter and contract filter, so the agent can execute the call without reading developer-portal docs. The API key stays in the Jentic vault.

Search Jentic for 'find nearest bike share station with available bikes', load the JCDecaux getStations schema, and execute it with contract=Dublin to return the top 5 stations by available_bikes.

Key Endpoints

3 endpoints — jentic publishes the only available openapi specification for jcdecaux bike api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/contracts

List all JCDecaux bike-share contracts (cities)

GET

/stations

List all stations or filter by contract

GET

/stations/{station_number}

Get live status for a single station

GET

/contracts

List all JCDecaux bike-share contracts (cities)

GET

/stations

List all stations or filter by contract

GET

/stations/{station_number}

Get live status for a single station

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

JCDecaux apiKey is stored encrypted in the Jentic vault. At execution time Jentic injects it into the apiKey query parameter so the raw key never enters the agent's context or logs.

Intent-based discovery

Agents call Jentic search with intents like 'find available bike share stations' and Jentic returns the JCDecaux getStations operation with its parameter schema, so the agent calls the right endpoint without reading developer-portal documentation.

Time to first call

Direct JCDecaux integration: a few hours to register, read docs, and wire calls. Through Jentic: under 15 minutes — search, load schema, execute.

FAQs

Specific to using JCDecaux Bike API through Jentic.

Why is there no official OpenAPI spec for JCDecaux Bike API?

JCDecaux does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call JCDecaux Bike API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the JCDecaux Bike API use?

The API uses a single apiKey passed as a query parameter named apiKey on every request. Keys are issued from the JCDecaux developer portal at developer.jcdecaux.com. When called through Jentic, the key is held in the Jentic vault and injected at execution time, so it never enters the agent's prompt context.

Can I get live bike counts for a specific station with the JCDecaux Bike API?

Yes. Call GET /stations/{station_number} with the station_number path parameter and a contract query parameter to get the station's available_bikes, available_bike_stands, status (OPEN/CLOSED), and last_update timestamp. JCDecaux refreshes these counts roughly once per minute.

What are the rate limits for the JCDecaux Bike API?

JCDecaux does not publish a fixed rate limit in the spec, but the developer portal asks integrators to cache responses and avoid polling individual stations more than once per minute. For city-wide updates, prefer one GET /stations?contract=... call over many per-station calls.

How do I find every available JCDecaux bike-share city through Jentic?

Run pip install jentic, then search for 'list JCDecaux contracts'. Jentic returns the getContracts operation; load it and execute with no parameters beyond the apiKey to receive the full list of contract names, commercial names, and country codes.

Is the JCDecaux Bike API free?

Yes — JCDecaux issues free developer keys for the open-data Bike API. Higher-volume or commercial use cases should contact JCDecaux directly through developer.jcdecaux.com.