People, companies and partners, recognized on any channel and system.
Every identifier comes in with its source and its weight: phone, email, ID number, app login and the customer’s ID in each system. Niadra merges what belongs to the same person only on a strong signal, and every merge can be undone. The customer can also be a company: an account is the company that buys from you, and a partner is an organization that takes part without being a customer, such as the carrier. Each person is linked to the organization by their role.
How it works
Each identifier carries a weight
exampleEvery piece of information stays linked to the identifier it came from. If two people are merged by mistake, Niadra splits them without losing the history of either.
People linked to organizations
example- Ana ReedbuyerA supermarket chainaccountsince Mar 2025 · from the CRM
- Luis MatadriverA carrierpartnersince Jan 2026 · from the transport system
- Luis MatadriverAnother carrierpartneruntil Dec 2025 · stated on a call
Companies never merge on their own: only through the company’s registration or a system ID. An email domain is a hint, never proof.
- Five verification levels: the context changes with how much the conversation has proven who the person is
- A phone number is a hint, not proof: it may have a new owner
- Test and sample values never merge anyone
- Each system’s ID becomes an identifier, with the system’s name attached
- One person can be linked to several organizations at once, each link with a role and a validity period
One memory, nine products
Any agent connects to the memory with three calls, in Python, TypeScript, HTTP or MCP.
See the documentation- MemoryWhat was said and done, with a date, a source and evidence.
- IdentityYou are herePeople, companies and partners, recognized on any channel.
- PatternsWhat repeats, with the proof behind each signal.