INRIX is a Kirkland, Washington-based transportation analytics company that turns anonymized GPS probe data from connected vehicles, mobile devices and fleets into real-time and historical road intelligence for automakers, cities, departments of transportation, retailers and app developers. Its developer surface is organized around the INRIX IQ platform and documented at docs.inrix.com, spanning Traffic APIs (segment speed, safety alerts/incidents, traffic tiles, routing, drive time polygons, traffic cameras, dangerous slowdowns, fuel stations and TPEG Connect), Parking APIs (INRIX Parking Services 3.0, formerly ParkMe: lots, blocks, occupancy and probability, destinations and reservations), Analytics APIs (trade area trips, trip trends, visits, dangerous roads and Roadway Analytics), Signals intersection analytics, a Data Download Service for map and XD network releases, and data-upload streams for GPS, XFCD and parking events. All access is brokered through the INRIX User Accounts System (UAS), which exchanges an appId and a SHA-1 hashToken for a bearer access token used across every product API.
INRIX publishes 29 API contracts indexed on the APIs.io network, including Accounts API, Application API, Auth API, and 26 more. Tagged areas include Transportation, Traffic, Mobility, Parking, and Geospatial.
The INRIX catalog on APIs.io includes 1 Spectral governance ruleset.
INRIX’s developer surface includes authentication, documentation, API reference, getting-started guide, developer console, signup flow, support, and 42 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/inrix/"><img src="https://apis.io/badge/inrix/card.svg" alt="INRIX on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship Ask about this →
Idempotency+9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
Rate-Limit Signaling+7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented) Ask about this →
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Real-time, historical and predicted speed, travel time and reference speed for INRIX XD and TMC road segments, queried by bounding box, radius, point, segment set or corridor.
Roadway incident, construction, flow, event and hazard alerts within a bounding box, radius or along a route, with TMC and OpenLR location referencing and TPEG-style event codes.
Aggregated, anonymized trip origin-destination counts into and out of a defined trade area or location polygon, for retail site selection and location analytics.
Asynchronous report and bulk speed-data downloader for INRIX Roadway Analytics: submit a report request, poll its status and retrieve the generated dataset.
Queries and downloads static INRIX data deliverables organized by product, dataset and file - beginning with map releases (XD added/removed/replaced, TMC changes, OpenLR diction...
Inbound data streams for partners contributing probe data to INRIX: batched JSON POSTs of GPS points, extended floating car data (XFCD) readings, and parking events, consumed as...
The long-standing INRIX Connected Services gateway (Inrix.ashx), which serves routing, drive time polygons, traffic cameras, road speed at points, segment sets and speed buckets...
Delivers INRIX traffic, incident, parking, weather and fuel content in TISA TPEG format over HTTP POST sessions, with incremental deltas, configurable content radii, compression...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
aid: inrix
name: INRIX
description: 'INRIX is a Kirkland, Washington-based transportation analytics company that turns anonymized GPS probe data
from connected vehicles, mobile devices and fleets into real-time and historical road intelligence for automakers, cities,
departments of transportation, retailers and app developers. Its developer surface is organized around the INRIX IQ platform
and documented at docs.inrix.com, spanning Traffic APIs (segment speed, safety alerts/incidents, traffic tiles, routing,
drive time polygons, traffic cameras, dangerous slowdowns, fuel stations and TPEG Connect), Parking APIs (INRIX Parking
Services 3.0, formerly ParkMe: lots, blocks, occupancy and probability, destinations and reservations), Analytics APIs (trade
area trips, trip trends, visits, dangerous roads and Roadway Analytics), Signals intersection analytics, a Data Download
Service for map and XD network releases, and data-upload streams for GPS, XFCD and parking events. All access is brokered
through the INRIX User Accounts System (UAS), which exchanges an appId and a SHA-1 hashToken for a bearer access token used
across every product API.'
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source:
- authentication
- security
- sandbox
generated: '2026-11-13'
method: derived
image: https://docs.inrix.com/images/inrix.png
url: https://raw.githubusercontent.com/api-evangelist/inrix/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-01'
modified: '2026-10-06'
tags:
- Transportation
- Traffic
- Mobility
- Parking
- Geospatial
- Location Data
- Analytics
- Automotive
- Smart Cities
- Routing
- Connected Vehicles
- Road Network
- Data
- Fleet Management
- Intelligent Transportation Systems
tags_raw:
- Transportation
- Traffic
- Mobility
- Parking
- Geospatial
- Location Data
- Analytics
- Automotive
- Smart Cities
- Routing
- Connected Vehicles
- Road Network
- Data
- Fleet
- Intelligent Transportation Systems
apis:
- name: INRIX Segment Speed API
description: Real-time, historical and predicted speed, travel time and reference speed for INRIX XD and TMC road segments,
queried by bounding box, radius, point, segment set or corridor.
humanURL: https://docs.inrix.com/traffic/segmentspeed/
baseURL: https://segment-api.inrix.com
tags:
- Traffic
- Speed
- Road Segments
- Real-Time
- XD
tags_raw:
- Traffic
- Speed
- Road Segments
- Real Time
- XD
- name: INRIX Safety Alerts (Incidents) API
description: Roadway incident, construction, flow, event and hazard alerts within a bounding box, radius or along a route,
with TMC and OpenLR location referencing and TPEG-style event codes.
humanURL: https://docs.inrix.com/traffic/incidents/
baseURL: https://incident-api.inrix.com
tags:
- Incidents
- Safety
- Alerts
- Traffic
- Event
tags_raw:
- Incidents
- Safety
- Alerts
- Traffic
- Events
- name: INRIX Traffic Tiles API
description: Pre-rendered raster traffic tiles for map overlays, addressed by quadkey and rendered from live INRIX speed
data.
humanURL: https://docs.inrix.com/traffic/tiles/
baseURL: https://tile-api.inrix.com
tags:
- Tiles
- Maps
- Traffic
- Raster
- Visualization
- name: INRIX Fuel Stations API
description: Fuel station locations, brands, amenities and current fuel prices by grade, searchable by bounding box, radius
or station identifier.
humanURL: https://docs.inrix.com/traffic/fuel/
baseURL: https://fuel-api.inrix.com
tags:
- Fuel
- Prices
- Points of Interest
- Geospatial
- Automotive
- name: INRIX Dangerous Slowdowns API
description: Detects and reports sudden, unexpected slowdowns on the road network so vehicles and drivers can be warned
ahead of a hazard.
humanURL: https://docs.inrix.com/traffic/dangerousslowdowns/
baseURL: https://dsd.api.inrix.com
tags:
- Safety
- Traffic
- Alerts
- Connected Vehicles
- Hazards
- name: INRIX Dangerous Roads API
description: Ranked collision and safety risk scoring for road segments, used to identify the most dangerous roads and intersections
in a geography.
humanURL: https://docs.inrix.com/analytics/dangerousroads/
baseURL: https://dangerousroads-api.inrix.com
tags:
- Safety
- Analytics
- Collisions
- Road Network
- Risk Management
tags_raw:
- Safety
- Analytics
- Collisions
- Road Network
- Risk
- name: INRIX Trade Area Trips API
description: Aggregated, anonymized trip origin-destination counts into and out of a defined trade area or location polygon,
for retail site selection and location analytics.
humanURL: https://docs.inrix.com/analytics/tradeareatrips/
baseURL: https://trade-areas-api.inrix.com
tags:
- Analytics
- Trips
- Trade Area
- Retail
- Location Intelligence
- name: INRIX Trip Trends Reports API
description: Trip volume and travel-behaviour trend reports over time for a geography, including seasonal adjustment and
data-quality metadata.
humanURL: https://docs.inrix.com/analytics/triptrends/
baseURL: https://triptrends-api.inrix.com
tags:
- Analytics
- Trips
- Reports
- Trends
- Mobility
- name: INRIX Roadway Analytics Data Downloader API
description: 'Asynchronous report and bulk speed-data downloader for INRIX Roadway Analytics: submit a report request, poll
its status and retrieve the generated dataset.'
humanURL: https://docs.inrix.com/ra/speedsdatadownloader/
baseURL: https://roadway-analytics-api.inrix.com
tags:
- Analytics
- Bulk Data
- Reports
- Roadway
- Downloads
tags_raw:
- Analytics
- Bulk Data
- Reports
- Roadway
- Download
- name: INRIX Data Download Service
description: Queries and downloads static INRIX data deliverables organized by product, dataset and file - beginning with
map releases (XD added/removed/replaced, TMC changes, OpenLR dictionaries, shapefiles and GeoJSON conflations).
humanURL: https://docs.inrix.com/datadownload/datadownload/
baseURL: https://mapdata.inrix.io
tags:
- Bulk Data
- Maps
- Downloads
- Reference Data
- XD
- name: INRIX Data Upload Service (GPS, XFCD and Parking Event Streams)
description: 'Inbound data streams for partners contributing probe data to INRIX: batched JSON POSTs of GPS points, extended
floating car data (XFCD) readings, and parking events, consumed asynchronously with sub-second acknowledgement.'
humanURL: https://docs.inrix.com/sendingdata/gpsdatastream/
baseURL: https://appsvc-ingest.inrix.io
tags:
- Data Ingest
- Streams
- GPS
- XFCD
- Probe Data
- name: INRIX Gateway Map Version API
description: Reports the current INRIX map and XD network version in use, so consumers can align segment identifiers with
the correct map release.
humanURL: https://docs.inrix.com/reference/mapversion/
baseURL: https://gateway-api.inrix.com
tags:
- Reference Data
- Versioning
- Maps
- XD
- Metadata
- name: INRIX Connected Services Gateway API
description: The long-standing INRIX Connected Services gateway (Inrix.ashx), which serves routing, drive time polygons,
traffic cameras, road speed at points, segment sets and speed buckets through Action-style requests against a regionally
issued server path.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://na-api2.inrix.com
tags:
- Routing
- Traffic
- Camera
- Drive Time
- Gateways
tags_raw:
- Routing
- Traffic
- Cameras
- Drive Time
- Gateway
- name: INRIX TPEG Connect
description: Delivers INRIX traffic, incident, parking, weather and fuel content in TISA TPEG format over HTTP POST sessions,
with incremental deltas, configurable content radii, compression and encryption for embedded automotive head units.
humanURL: https://docs.inrix.com/traffic/tpeg/
baseURL: https://na-tts.inrix.com
tags:
- TPEG
- Automotive
- Streaming
- Traffic
- Standards
- name: INRIX Visits Analytics API
description: Anonymized visit counts and dwell analytics for points of interest and custom polygons, derived from INRIX
device and vehicle movement data.
humanURL: https://docs.inrix.com/analytics/analyticsvisits/
baseURL: https://analytics-visits.inrix.com
tags:
- Analytics
- Visits
- Location Intelligence
- Retail
- Foot Traffic
- aid: inrix:inrix-accounts-api
name: INRIX Accounts API
description: The accounts API from INRIX — 1 operation(s) for accounts.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- Account
tags_raw:
- accounts
properties:
- type: OpenAPI
url: openapi/inrix-accounts-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-application-api
name: INRIX Application API
description: The Application API from INRIX — 9 operation(s) for application.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- Application
properties:
- type: OpenAPI
url: openapi/inrix-application-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-auth-api
name: INRIX Auth API
description: The Auth API from INRIX — 6 operation(s) for auth.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- Authentication
tags_raw:
- Auth
properties:
- type: OpenAPI
url: openapi/inrix-auth-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-developer-api
name: INRIX Developer API
description: The Developer API from INRIX — 2 operation(s) for developer.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- Developers
tags_raw:
- Developer
properties:
- type: OpenAPI
url: openapi/inrix-developer-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-device-api
name: INRIX Device API
description: The Device API from INRIX — 3 operation(s) for device.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- Device
properties:
- type: OpenAPI
url: openapi/inrix-device-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-metadata-api
name: INRIX Metadata API
description: The Metadata API from INRIX — 1 operation(s) for metadata.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- Metadata
properties:
- type: OpenAPI
url: openapi/inrix-metadata-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-metrics-api
name: INRIX Metrics API
description: The Metrics API from INRIX — 2 operation(s) for metrics.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- Metrics
properties:
- type: OpenAPI
url: openapi/inrix-metrics-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-namespace-management-api
name: INRIX Namespace Management API
description: APIs for managing intersection namespace subscriptions
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- Namespace Management
properties:
- type: OpenAPI
url: openapi/inrix-namespace-management-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-user-api
name: INRIX User API
description: The User API from INRIX — 18 operation(s) for user.
humanURL: https://docs.inrix.com/authentication/getting_authorized/
baseURL: https://uas-api.inrix.com
tags:
- User
properties:
- type: OpenAPI
url: openapi/inrix-user-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-caniparkhere-api
name: INRIX Caniparkhere API
description: The Caniparkhere API from INRIX — 1 operation(s) for caniparkhere.
humanURL: https://docs.inrix.com/traffic/segmentspeed/
baseURL: https://segment-api.inrix.com
tags:
- Caniparkhere
properties:
- type: OpenAPI
url: openapi/inrix-caniparkhere-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-openspots-api
name: INRIX Openspots API
description: The Openspots API from INRIX — 2 operation(s) for openspots.
humanURL: https://docs.inrix.com/traffic/segmentspeed/
baseURL: https://segment-api.inrix.com
tags:
- Openspots
properties:
- type: OpenAPI
url: openapi/inrix-openspots-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-application-management-api
name: INRIX Application Management API
description: The Application Management API from INRIX — 9 operation(s) for application management.
humanURL: https://docs.inrix.com/traffic/segmentspeed/
baseURL: https://segment-api.inrix.com
tags:
- Application Management
properties:
- type: OpenAPI
url: openapi/inrix-application-management-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-email-template-api
name: INRIX Email Template API
description: The Email Template API from INRIX — 2 operation(s) for email template.
humanURL: https://docs.inrix.com/traffic/segmentspeed/
baseURL: https://segment-api.inrix.com
tags:
- EmailTemplate
tags_raw:
- Email Template
properties:
- type: OpenAPI
url: openapi/inrix-email-template-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- aid: inrix:inrix-user-group-api
name: INRIX User Group API
description: The User Group API from INRIX — 8 operation(s) for user group.
humanURL: https://docs.inrix.com/traffic/segmentspeed/
baseURL: https://segment-api.inrix.com
tags:
- UserGroup
tags_raw:
- User Group
properties:
- type: OpenAPI
url: openapi/inrix-user-group-api-openapi.yml
- type: Swagger
url: https://uas-api.inrix.com/swagger/docs/v1
- type: Console
url: https://uas-api.inrix.com/swagger
- type: Swagger
url: https://parking-api.inrix.com/api/swagger.json
- type: APIReference
url: https://parking-api.inrix.com/doc/v3/bulk/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- url: https://inrix.com/feed/
type: BlogRSS
- type: CapabilityMap
url: capabilities/inrix-capability-edges.yml
name: INRIX Business Capability Map
- type: Overlay
url: overlays/inrix-user-accounts-overlay.yaml
- type: AgentSkill
url: skills/inrix-authenticate-and-call.md
- type: AgentSkill
url: skills/inrix-manage-applications-and-users.md
- type: Overlay
url: overlays/inrix-parkme-overlay.yaml
- type: Overlay
url: overlays/inrix-signals-analytics-overlay.yaml
- type: AgentSkill
url: skills/inrix-query-signals-intersection-metrics.md
- type: X-MCPServerCandidate
url: mcp/inrix-mcp.yml
note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: DomainSecurity
url: security/inrix-domain-security.yml
- type: Authentication
url: authentication/inrix-authentication.yml
- type: Website
url: https://inrix.com/
- type: DeveloperPortal
url: https://inrix.com/developers/
- type: Documentation
url: https://docs.inrix.com/
- type: APIReference
url: https://docs.inrix.com/traffic/general_info/
- type: GettingStarted
url: https://docs.inrix.com/authentication/getting_authorized/
- type: Authentication
url: https://docs.inrix.com/authentication/getting_authorized/
- type: Console
url: https://iq.inrix.com/
- type: SignUp
url: https://iq.inrix.com/
- type: Login
url: https://iq.inrix.com/?l=1
- type: Support
url: mailto:support@inrix.com
- type: Blog
url: https://inrix.com/blog/
- type: GitHubOrganization
url: https://github.com/INRIX
- type: StatusPage
url: https://status.inrix.com/
- type: ChangeLog
url: https://docs.inrix.com/parking/change_log/
- type: TermsOfService
url: https://inrix.com/site-terms/
- type: PrivacyPolicy
url: https://inrix.com/site-privacy-policy/
- type: Glossary
url: https://docs.inrix.com/reference/glossary/
- type: ErrorCodes
url: https://docs.inrix.com/reference/errorstatusids/
- type: SDK
url: https://docs.inrix.com/sdk/general/
- type: Pricing
url: https://inrix.com/contact/
- type: ErrorCatalog
url: errors/inrix-error-codes.yml
name: INRIX statusId registry (360 codes)
- type: ErrorCatalog
url: errors/inrix-problem-types.yml
name: Error responses derived from the INRIX contracts
- type: Conventions
url: conventions/inrix-conventions.yml
name: INRIX API conventions
- type: Lifecycle
url: lifecycle/inrix-lifecycle.yml
name: INRIX versioning, environments and status
- type: ChangeLog
url: changelog/inrix-changelog.yml
name: INRIX parking and SDK release notes
- type: Sandbox
url: sandbox/inrix-sandbox.yml
name: INRIX beta, sandbox and qa environments
- type: Packages
url: packages/inrix-packages.yml
name: INRIX client libraries
- type: SDKs
url: packages/inrix-packages.yml
name: INRIX mobile client SDKs
- type: Conformance
url: conformance/inrix-conformance.yml
name: Standards conformance
- type: Compliance
url: conformance/inrix-conformance.yml
name: EU-U.S. Data Privacy Framework certification
- type: DataModel
url: data-model/inrix-data-model.yml
name: INRIX entity graph
- type: AgentSkill
url: skills/_index.yml
name: INRIX agent skills
- type: LLMsTxt
url: llms/inrix-llms.txt
name: llms.txt for INRIX
- type: UsageTerms
url: terms/inrix-terms-of-service.yml
- type: DataProcessing
url: privacy/inrix-privacy-policy.yml
- type: Eligibility
url: eligibility/inrix-eligibility.yml
- type: AIPreferences
url: ai-preferences/inrix-ai-preferences.yml
- type: DataLicense
url: data-license/inrix-data-license.yml
x-enrichment:
date: '2026-08-01'
status: enriched
artifacts_added: 24
pass: local-v1
INRIX API — frequently asked questions
Does INRIX have an API?
Yes. APIs.io lists 29 APIs from INRIX, including INRIX Segment Speed API, INRIX Safety Alerts (Incidents) API and INRIX Traffic Tiles API, and 26 more.
Is there an OpenAPI specification for the INRIX API?
Yes. APIs.io indexes 14 OpenAPI specifications for INRIX, each linked for download from this page.
How do I authenticate with the INRIX API?
INRIX uses bearer-token authentication (http/apiKey/oauth2 · 3 schemes). The details are profiled on APIs.io as INRIX Authentication.
Is the INRIX API ready for AI agents?
INRIX has a Kin Score of 51.8 out of 100 (developing) and an Agent Readiness score of 18.2 (agent-aware), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.