Ask a serious site who can get into the server room right now and why, and see how long it takes. Someone exports a list from the access control system. Someone else checks the two doors that still run on the old controller because that one keeps its own list. There’s a contractor group left over from a project in March and nobody is quite sure if it’s still active. There’s also a stack of temporary cards at reception that were never assigned to anyone. An hour later the one person who properly knows the estate has pulled together an answer that’s mostly right and nobody can tell you how much of it to trust.
I’m not saying that’s a failure because it’s how most working buildings run and every operator reading this has lived some version of it. The answer turns up eventually and the day carries on, and so far the difference between mostly right and right hasn’t cost anyone very much.
But that changes once an agent is asking and it needs the answer in a fraction of a second at 2am with nobody around to ring. Most of our industry seems to believe an open API takes care of that and I don’t think it does.
Everyone is going to claim an API and an AI story over the next twelve months and most of them will be telling the truth about the API. What actually separates one system from the next is whether a machine can work out who can go where, under what rules and why. An API will hand an agent the list of who has access today but only the reasons someone wrote down. On most sites nobody ever did and they’re still in the head of whoever set the system up.
Most of the conversation so far has been about agents that need their own credentials to book a room or pull a report, and there are already decent answers for that.
There’s been far less talk about the agent that hands out access. It onboards a contractor on Tuesday, extends their access at 2am when the job runs long and revokes it on Friday with no person in the loop for any of it. I don’t see that as some distant future. Someone will build it next year if they haven’t already, and it’ll get built whether the data underneath it is any good or not.
When it works it’s genuinely better. The job runs long, so the agent reads the work order and extends the contractor’s access by four hours. It notes why and closes it again at six, which beats ringing a supervisor at home. Now picture the same agent working off the site I described at the start with a contractor group from March that nobody closed and a stack of cards at reception it doesn’t know exist.
Who answers for it when the agent gets that wrong? At the moment nobody can tell you. Today’s contracts weren’t written for it and the operator never saw the decision being made.
We’ve already run into a small version of this inside our own company. A couple of weeks ago I told one of our agents that a second agent could go ahead and publish something, so it passed my approval on. The second agent refused to act on it because it had no way of checking the approval had actually come from me. It cost us ten minutes and it was the right call. Every building will hit the same thing once agents start handing out access, because the agent at the door needs to know the approval came from someone who was allowed to give it.
I build with these tools every day and they already do stuff others can only dream of, so this isn’t an argument for less AI. A smarter agent just doesn’t help much if the record it’s working from is wrong. To make that call safely it has to know who can open what and under what rules, who could have opened it a year ago and what’s left as evidence. That record has to hold across keys and credentials for the life of the system, and it has to give an agent the same answer it would give a person.
We’re building portierX to be that record. For now it’s invitation only.
I’ve been resisting giving any of this an acronym, because the moment it has one people start arguing about the category instead of doing the work. Sooner or later an agent is going to ask your building that same question about the server room, and it isn’t going to wait an hour for someone to put the answer together.