Persona ships with native capabilities that are already connected to its brain.
This is one of the biggest practical differences between Persona and a generic agent stack. You do not start from an empty shell and then spend months recreating product surfaces around it.
What “built-in” means
Built-in means the capability is part of the product model itself.
That matters because Persona can use those surfaces with continuity from the start:
- the same memory model
- the same identity
- the same execution boundaries
- the same runtime-level context
Instead of wiring an AI to disconnected tools, you are extending one runtime that already knows how to operate across multiple surfaces.
In practice, those capabilities live inside the owning space and are exposed through the apps and product surfaces you connect around that Persona.
Core surfaces
The built-in capability set can include:
- chat
- agenda
- notifications
- whiteboard
- document library
- KV datastore
- billing
Depending on the deployment, Persona can also extend into:
- custom product surfaces
- external business systems
- embedded world interfaces
- virtual world NPC environments
Why this changes integration work
With a normal AI integration, teams often end up building all the useful product surfaces themselves:
- a place to store state
- a place to keep documents
- a way to schedule or revisit work
- a way to preserve context across sessions
- a way to connect the surfaces back to the agent
Persona removes a large part of that work because those surfaces already exist as part of the product shape.
Examples
KV datastore
Use it for product state, shared references, lightweight operational memory, or app-specific keys that should stay connected to Persona.
Document library
Use it when Persona needs to work with knowledge artifacts, attached materials, generated documents, or reusable project content.
Agenda
Use it for scheduled follow-ups, planned work, reminders, and continuity over time.
Chat
Use it when direct interaction is part of the experience, but keep in mind that chat is only one of the surfaces Persona can inhabit.
Whiteboard
Use it when the runtime needs a visual thinking or collaboration surface instead of forcing every action into text.
Billing
Use it when the product needs commercial continuity as well as runtime continuity.
Billing lets the product charge end customers through native top-up and subscription models instead of making the team bolt on a separate payments stack around Persona.
If billing is central to the deployment, read Customer Billing next.
Built-in first, custom second
The simplest integrations usually start by using the native surfaces first and then extending Persona into external systems where the product actually needs it.
That keeps the first deployment much cleaner than trying to build every surface from scratch around a bare model.