Integration
Connect Transport for Denver, US to UK Police
When something happens in Transport for Denver, US, your agent does the next thing in UK Police. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Transport for Denver, US and UK Police to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with Transport for Denver, US and UK Police
Triggers and actions 1 trigger · 23 actions
Trigger
New service alertFires when RTD publishes a new service alert, polling Denver RTD's GTFS-Realtime alerts feed.
Action
Get service alertsFetch the service alerts RTD is currently publishing (delays, detours, closures), from Denver RTD's GTFS-Realtime alerts feed.
Action
Get trip updatesFetch real-time trip progress and arrival/departure predictions for RTD scheduled trips, from Denver RTD's GTFS-Realtime trip-updates feed.
Action
Get vehicle positionsFetch the live position of every RTD vehicle currently in service, from Denver RTD's GTFS-Realtime vehicle-positions feed.
Action
Find crimes at location/crimes-at-location - crimes that occurred at a specific location (location_id or lat/lng), optional date
Action
Find crimes with no location/crimes-no-location - crimes for a category/force with no location, by month
Action
Find neighbourhood by location/locate-neighbourhood - locate the neighbourhood policing team responsible for a lat/lng point
Action
Find stop and searches at location/stops-at-location - stop and search incidents at a specific location_id, optional date
Action
Find stop and searches by area/stops-street/all - stop and search incidents within a 1 mile radius of a point or custom polygon, optional date
Action
Find stop and searches by force/stops-force - stop and search incidents for a specific force, by month
Action
Find stop and searches with no location/stops-no-location - stop and search incidents for a force with no location, by month
Action
Find street level crimes/crimes-street/all-crime - crimes within a 1 mile radius of a point or custom polygon, optional date
Action
Find street level outcomes/outcomes-at-location - outcomes (case results) within a 1 mile radius of a point or custom polygon, optional date
Action
Get force/forces/{force_id} - details for a specific police force
Action
Get last updated date/crime-last-updated - date the crime data was last updated
Action
Get neighbourhood/{force_id}/{neighbourhood_id} - details for a specific neighbourhood
Action
Get neighbourhood boundary/{force_id}/{neighbourhood_id}/boundary - list of lat/lng points defining a neighbourhood boundary
Action
Get outcomes for crime/outcomes-for-crime/{persistent_id} - outcomes for a specific crime by its persistent id
Action
List forces/forces - list all UK police forces (id + name)
Action
List force senior officers/forces/{force_id}/people - list senior officers for a specific force
Action
List neighbourhood events/{force_id}/{neighbourhood_id}/events - upcoming events for a neighbourhood
Action
List neighbourhood priorities/{force_id}/{neighbourhood_id}/priorities - policing priorities for a neighbourhood
Action
List neighbourhoods/{force_id}/neighbourhoods - list neighbourhoods for a force
Action
List neighbourhood team/{force_id}/{neighbourhood_id}/people - list of members of a neighbourhood policing team
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews