POST /v1/resolve-location · /permission-check/by-location
A robot doesn't know it's at "the hospital" — it knows its GPS coordinates. It streams them to Ground API,
which resolves the geofence to a property and returns the verdict. Off every registered geofence, it's public space and GateOS imposes nothing.
Latitude
Longitude
Jump to a site
Enter coordinates (or jump to a site) and resolve.
Pending Approvals
robots waiting on a human decision
No pending approvals — run a check that returns REQUIRES APPROVAL and it lands here.
API Access
local dev keys — never ship these
Your Keys
Every API call carries one of these as Authorization: Bearer <key>.
The owner key manages policy and sees the audit trail; a
vendor key can act only as that company's robots. This dashboard is already
signed in with the owner key. These dev keys exist only on your machine.
Role
Company
Key
Call the API yourself (PowerShell)
Robot Integration
the builder's view — register · enroll · call
Onboard a Robot Company
POST /register · /robots · /permission-check
This is what a robot company does to integrate: sign up, receive a secret API key (shown once), enroll its robots, then call the
API authenticated by that key. A company can act only as its own robots — that's the whole security model.
Step through a real integration: sign up → get a key → enroll a robot → call the API as that company.