City of Surrey APIs for AI Agents
Developer ToolsSource ControlMappingMixed ProvenanceNo authAgent Ready
City of Surrey API Catalog
2 APIs across 2 product groups. All share one credential.
Which City of Surrey API should I use?
| I want to... | Use | Why |
|---|---|---|
| Real-time road obstructions and traffic events | City of Surrey Open511 API | Open511 reports current road-event and obstruction data for the City of Surrey. |
| Traffic volumes and loop sensor counts | City of Surrey Traffic Loop Count API. | The Traffic Loop Count API gives loop locations and vehicle counts in 15-minute intervals. |
Install Jentic One Beta
Connect the City of Surrey APIs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the City of Surrey APIs, 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%2Fsurrey.ca" | 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%2Fsurrey.ca" | 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.
Once connected, ask your agent something like: “get city of surrey road events and traffic loop counts”.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring these APIs by hand means pointing at Surrey's separate data.surrey.ca and gis.surrey.ca hosts and parsing two different response shapes. Once Jentic One is installed, you or your agent can find and add either API from the Jentic directory and call it without hand-coding the hosts.
Permission scoping
Both APIs are read-only open data, so your own rules in Jentic One can scope the agent to just the road-event or loop-count operations it needs. There are no write operations to allow.
Credential isolation
Neither API requires a credential, so there is nothing to store. Your own Jentic One instance calls the open endpoints at execution time and no secret enters the agent's prompt, logs, or context.
FAQs
Specific to using City of Surrey APIs through Jentic.
What can an agent do across City of Surrey's APIs?
An agent can read live road obstruction and traffic events from the Open511 API and pull traffic loop locations and vehicle counts from the Traffic Loop Count API. Together these give a real-time and historical view of road conditions and volumes across the City of Surrey.
Do the two APIs cover the same data?
No. Open511 reports road-event and obstruction information, while the Traffic Loop Count API reports where traffic loops are located and how many vehicles passed in each 15-minute interval. They complement each other and can be cross-referenced by loop identifier.
Do I need separate credentials for each API?
No. Both APIs are open and require no authentication, so there is no key or token to obtain for either one.
How fresh is the data?
The Open511 API reports road events in real time. The Traffic Loop Count API records counts in 15-minute intervals, though the underlying data is currently loaded once per day. Check the response fields for timestamps before relying on freshness.
BOOK A DEMO
Start Connecting APIs to Your AI Agents
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
