Japa reads from the sensors, gates, permits, LPR, meters, payment apps, EV chargers and calendars a campus already has, and writes back to signs, apps and alerts. You keep your vendors and your data. The agent gets the whole picture.
A few of the systems Japa reads from. The full catalog covers 100+ sources across sensors, payments, permits, enforcement, EV, facilities and events. Every connector is built and maintained by Japa; you add a key or an export and confirm the mapping once.
Choose a connector in the console, or upload an export. Japa knows the shape of each vendor's data and asks only for what it needs: usually a key or a file.
Vendor lots, zones and devices are matched to Japa's catalog of lots, levels and spaces. Suggested matches are shown; you confirm them once.
Data lands on the Map and in the agent's tools. A health panel shows last sync, errors and coverage so nothing silently goes stale.
Organization admins create keys from the console, scope them, meter them and revoke them. Consultants, signage vendors and campus apps read live occupancy without a ticket to Japa. Alert rules can post to any webhook.
{
"id": "0b1e…",
"name": "Lot 17",
"type": "surface",
"source": "sensors",
"occupancy": {
"occupied": 212,
"available": 128,
"offline": 2,
"capacity": 342,
"occupiedPercent": 62
},
"updatedAt": "2026-10-10T16:42:08Z"
}
If it has an export or an API, Japa builds the connector. Existing customers pay nothing for the standard catalog. Tell us the vendor and what you want the agent to do with it.