A Library of Agents — and a Way to Build Your Own

AI agents are quickly becoming one of the most valuable tools on an operator's stack. The kind of work that used to eat hours for onsite teams each week — recurring, high-volume, mechanical — can now be handled in a single kick-off. The operator says go, and the agent works through the batch on real operator data, inside the same platform the property is already run from.

OXP Studio's Agent Roster is where operators put that value to work. There's a growing library of pre-built agents operators can choose from, and — for the workflows an operator wants built to fit their own business — a way to describe an agent in plain English and have Entrata^® build it. Both paths live in the same workspace, run on the same platform, and use the same operator data.

What's New

• Agent Blueprints — a library that operators can choose from today. The Agent Blueprints tab gives operators a set of pre-built agents they can put to work without describing the agent from scratch. Entrata keeps adding to the library based on what teams across the operator base are asking for most, so the shelf grows over time rather than staying fixed.
• Agent Request — describe the agent, Entrata builds it. In the Agent Request tab, an operator describes the agent they want the way they'd describe it to a teammate — "I want an agent that scans all Month-to-Month leases and sends renewal offers," or "I want an agent that monitors lease expirations within 90 days, sends the resident a renewal offer based on publicly advertised market rent, and escalates to the property manager if no response in 7 days." Requests can include SOPs, process documents, or screen recordings, so the agent that comes back is built for how this operator actually runs the workflow, in the language this operator uses for it.
• One place to see everything. The “Your Submissions” tab shows every custom request an operator has made along with its corresponding status. Alongside “Your Agents Status" and “Your Agents Workflows”, OXP Studio provides one home for everything — from a blueprint that's ready to activate, to a custom request Entrata is building, to an agent already deployed and ready to kick off.
• Forward Deployed Engineers on both paths. Behind OXP Studio, Entrata's Forward Deployed Engineers work directly with operators — helping deploy blueprints against a portfolio and shaping the custom agents an operator requests. OXP Studio is where the work is created and kicked off; the engineers are the humans making sure it actually lands.

Why It Matters

Agents move work from "the team has to grind through it" to "the operator kicks it off and the agent does it." You stay in control of when it runs. The agent handles the volume — a batch of month-to-month renewals to invite, a list of accounts to follow up on, a set of records to work through — designed to complete in minutes the work that can take a team hours. 

OXP Studio makes that value accessible in two ways. If the agent an operator needs is already in the Blueprints library, they can pick it up and put it to work. If it isn't, they can describe it and Entrata will build it — for the way their business runs, in their language, using their data.

That combination is what working differently looks like in practice. The range of what agents can do for an operator stops being fixed by what's already on the shelf. If it's in the library, it can be activated. And whichever path an operator takes, the agent works when the operator says go.

Why This Works Inside Entrata

An agent is only useful if it works on real operational data — the leases, the residents, the units, the ledgers, the work orders, the calendars, the compliance context. That's the layer already sitting underneath every agent in OXP Studio, whether the agent started from a Blueprint or from a natural-language request.

An agent for month-to-month renewals works from real leases and terms. An agent for delinquency follow-up works from the real ledger. An agent for turns works from the real unit and work-order history. And because that context is already there, the agent gets built on top of it, not wired in around it. When the operator kicks it off, it works inside the same platform, with the same permissions and audit trail the property is already run from.

That's what Entrata Layered Intelligence^® looks like for the operator experience. Whether the agent comes from a library or from a description of a workflow, when the operator says go, it works because every other layer of the platform is already underneath it.

‍

‍

Learn more about OXP Studio and how Entrata is giving operators agents built for the way they work — from a growing library, and from their own natural-language requests — at entrata.com.