Skip to main contentEntities are specific instances of objects — a particular customer, a specific order, an individual product. Entity definitions tell the agent how to identify and resolve them, especially when the same entity appears across multiple data sources.
What entities solve
Your data often refers to the same real-world thing in different places with different identifiers. A customer might be account_id in your database, an email address in your CRM, and a company name in your documents.
Entities define how to resolve these references so the agent treats them as a single thing.
Entity resolution
When you define an entity, you specify:
- The object it belongs to — e.g. Customer
- Identifiers — the fields that uniquely identify it across sources (account ID, email, domain, etc.)
- Resolution rules — how to match when identifiers differ (e.g. fuzzy match on company name)
This means when someone asks “Tell me about Acme Corp,” the agent can pull data from every source that mentions Acme — even if each source uses a different identifier. 
