511on Ca Ontario 511 Transportation API
46
AI ReadinessFoundational (D)46/100
Agent-ready OpenAPI document · curated by JenticMaps GeolocationRouting DirectionsapiKey16 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Look up live Ontario highway events, road conditions, traffic cameras, and ferry schedules from the official 511 Ontario data feed. Useful for routing agents, fleet dispatch, and travel-planning assistants operating in Ontario.
Use for: Check whether there are any active incidents on Highway 401 right now, List all construction zones currently affecting Ontario highways, Retrieve the live camera feed URLs for the Toronto area, Find road surface conditions on the route between Ottawa and Sudbury
Not supported: Does not handle navigation routing, mapping tiles, or roads outside Ontario - use for live Ontario provincial highway data only.
Jentic publishes the only available OpenAPI specification for Ontario 511 Transportation API, keeping it validated and agent-ready. The Ontario 511 Transportation API exposes real-time provincial traffic and travel data published by the Ontario Ministry of Transportation, including incidents, construction zones, traffic camera feeds, road surface conditions, ferry schedules, carpool lots, transit hubs, service centres, truck inspection stations, and winter maintenance vehicles. The API returns JSON for sixteen GET endpoints scoped to Ontario highways and is intended for navigation apps, fleet operators, and travel planning tools that need authoritative road data. Authentication uses a per-developer API key requested through the Ontario 511 developer portal.
Install Jentic One Beta
Connect the Ontario 511 Transportation API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ontario 511 Transportation 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.
1
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%2F511on.ca%2F511on" | sh2
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%2F511on.ca%2F511on" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Ontario 511 Transportation API.
Retrieve current traffic events and incidents on Ontario highways with location and severity detail
List active construction projects with scheduled start and end dates
Pull traffic camera image URLs for any monitored Ontario highway segment
Check current road surface and weather conditions reported by maintenance patrols
Look up ferry departure schedules and operating status for provincial ferry crossings
Find carpool lots, service centres, and truck inspection stations along a planned route
Use Cases
Patterns agents use Ontario 511 Transportation API for, with concrete tasks.
★ Real-Time Trip Planning for Ontario Drivers
Surface live incident, construction, and road condition data inside a navigation app or driver portal so users avoid closures and slowdowns on Ontario highways. The API exposes events, construction, and roadconditions endpoints that return location-tagged records refreshed by the Ontario Ministry of Transportation, allowing apps to render warnings on a map without scraping public web pages. Integration is typically a half-day for a basic feed and two to three days for full filtering and caching.
Call /get/events and /get/roadconditions, filter records to Highway 401 between Toronto and Kingston, and return any active incidents or poor surface conditions with timestamps.
Fleet Dispatch and Routing Adjustments
Logistics and fleet operators running deliveries through Ontario use the construction, events, and truck inspection station endpoints to reroute vehicles around closures and confirm where commercial vehicle inspections are open. The API covers all provincial highways and is updated continuously, so dispatchers can flag problem corridors before drivers depart. Connecting the feed to an existing dispatch system takes a developer one to two days.
Fetch /get/construction and /get/truckinspectionstations, intersect with a planned route from Windsor to Toronto, and produce a list of zones to avoid plus the next open inspection station.
Public Information Dashboards and Travel Boards
Tourism boards, regional municipalities, and travel publishers embed Ontario 511 data on dashboards showing camera feeds, ferry status, and service centre locations. The cameras and ferries endpoints return image URLs and schedule data ready for direct display, eliminating the need for manual content updates. A typical dashboard build using cached responses takes two to four days.
Pull /get/cameras and /get/ferries, group cameras by region, and render a dashboard component listing the top ten cameras and the next ferry departure for each crossing.
Agent-Driven Ontario Travel Assistant via Jentic
An AI travel assistant connected through Jentic can answer driver questions about Ontario highway conditions in natural language by routing queries to the right 511 endpoint. Jentic returns the operation schema so the agent passes only the API key once and receives structured incident or condition records, with no need to maintain a hand-written client. Setup through Jentic is under thirty minutes versus a half-day of manual integration.
Search Jentic for 'Ontario highway traffic conditions', load the /get/events schema, and answer the user's question 'is there construction on the 401 today' with the live data.
Key Endpoints
16 endpoints — jentic publishes the only available openapi specification for ontario 511 transportation api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/get/events
List active traffic events and incidents
GET
/get/construction
List active highway construction zones
GET
/get/cameras
List traffic camera feeds with image URLs
GET
/get/roadconditions
Retrieve current road surface conditions
GET
/get/ferries
List ferry crossings and schedules
GET
/get/carpoollots
List carpool lot locations
GET
/get/truckinspectionstations
List commercial vehicle inspection stations
GET
/get/events
List active traffic events and incidents
GET
/get/construction
List active highway construction zones
GET
/get/cameras
List traffic camera feeds with image URLs
GET
/get/roadconditions
Retrieve current road surface conditions
GET
/get/ferries
List ferry crossings and schedules
GET
/get/carpoollots
List carpool lot locations
GET
/get/truckinspectionstations
List commercial vehicle inspection stations
Jentic AI Readiness Score
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.
O
Ontario 511 Transportation API
- Foundational (D)46/100
74
Foundational Compliance63
Developer Experience & Jentic Compatibility50
AI-Readiness & Agent Experience94
Agent Usability15
Security54
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
74
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 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).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
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.
50
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
48%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
15
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
15%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
54
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
54%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Ontario 511 Transportation API by hand means managing its API key, appending it as a query parameter, and parsing the v2 highway data feeds yourself. Through Jentic you install once, import the Ontario 511 Transportation API from the API Directory, store the key once, and your agent calls it.
Permission scoping
This API is read-only and selects data through query parameters rather than a resource id in the path, so limit the agent to the operations it needs, such as reading events, road conditions, or cameras, and leave out others unless you add them. You choose the allowed set, so only the operations you pick can run.
Credential isolation
Your Ontario 511 API key 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 'get Ontario highway incidents' or 'read Ontario road conditions', and Jentic returns the matching Ontario 511 operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Ontario 511 Transportation API through Jentic.
Why is there no official OpenAPI spec for Ontario 511 Transportation API?
The Ontario Ministry of Transportation publishes the 511 service with text-based developer documentation but does not ship a machine-readable OpenAPI specification. Jentic generates and maintains this spec so AI agents and developers can call the API through structured tooling. It is validated against the live endpoints and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Ontario 511 Transportation API use?
The API uses an API key passed as a query string parameter on every request. Keys are issued through the Ontario 511 developer portal. When called through Jentic the key is stored encrypted in your Jentic One instance and injected at execution time, so the raw key never enters agent context.
Can I get real-time traffic incidents on Highway 401 with the Ontario 511 Transportation API?
Yes. Call GET /get/events to retrieve all current incidents and filter the response by road name or geographic bounding box for Highway 401. The feed is refreshed continuously by the ministry and includes incident type, location, and severity.
What are the rate limits for the Ontario 511 Transportation API?
The Ontario 511 developer agreement requests that callers cache responses for at least sixty seconds and avoid polling more frequently than the published refresh intervals. There is no published numeric per-second cap; sustained abuse can result in the key being revoked. For production use, cache responses and poll on a one-to-five-minute interval.
How do I check road conditions on a route through Jentic?
After running pip install jentic and configuring JENTIC_AGENT_API_KEY, search Jentic for 'Ontario road conditions', load the /get/roadconditions schema, and execute. Jentic returns the structured records and the agent can intersect them with a planned route. The full search-load-execute flow takes a few seconds.
Does the Ontario 511 Transportation API cover roads outside Ontario?
No. The data is limited to provincial highways and ferry routes operated by or reported to the Ontario Ministry of Transportation. For other Canadian provinces or US states, use the equivalent regional 511 service such as 511ny.org or az511.com.
Can I limit what my agent is allowed to do with the Ontario 511 Transportation API?
Yes. Because you run Jentic One yourself, your own rules decide which of the read-only Ontario 511 operations the agent may call, so you can allow only what it needs, such as reading events or road conditions, and leave out cameras, ferries, or truck inspection stations. Every operation retrieves data through query parameters rather than modifying anything, so the agent can never write or delete provincial highway records. Only the operations you pick can run, and your Ontario 511 API key is stored encrypted and injected at execution time so it never enters the agent's context.
GET STARTED