# History: everything that happened with the customer, for the AI agent to search | Niadra

> The agent searches the customer’s entire history with any LLM, through the SDK, the API or MCP. Every result comes back with date, channel, outcome and source, and respects the agent’s permissions.

URL: https://niadra.com/en/produtos/historico

History

# Everything that ever happened with the customer, for the agent to search.

The context covers what matters now. When the conversation needs more, the agent searches the customer’s entire history with any LLM: it searches by meaning and by keyword, pages through the timeline and opens a specific conversation. Every result comes back with a date, channel, outcome and source, and respects that agent’s permissions.

[Talk to us](/en/enterprise)[Read the docs(opens docs.niadra.com)](https://docs.niadra.com/en/concepts/history)

## How it works

History searchexample

The customer says

“Last time you gave me a credit.”

The agent searches

```
niadra.search(
  subject=ctx.subject,
  query="credit for missed technician visit",
)
```

Niadra answers

-   Mar 12, 2026 · PhoneTechnician did not show up. $40 credit applied to the April bill. settled
-   Mar 14, 2026 · WhatsAppThe customer confirmed the credit and the new visit. settled
-   Nov 3, 2025 · AppVisit rescheduled at the customer’s request. no credit

Second missed visit in 12 months. Last time, a $40 credit.

-   Three operations: search, page through the timeline and open a conversation
-   “How many times has this happened” is a count, not a guess
-   The same permissions and verification level as the context
-   Through the SDK, the API or as an MCP tool, with the model you already use
-   The customer’s identifier is bound into the tool, out of the model’s reach: a malicious message cannot switch customers
-   Every search leaves a record: who asked, what they asked and what came back

## What the agent can ask

-   Has this happened before? How many times?
-   What was promised last time, and by whom?
-   How was the last complaint settled?
-   Has she ever asked to cancel?
-   Has anyone handled this already? What was done?

### Seven MCP tools

The same functions as the SDK, for agents that speak MCP. Each description teaches the model when to use it.

-   get\_customer\_context
-   track\_event
-   record\_action
-   resolve\_identity
-   search\_customer\_history
-   get\_customer\_timeline
-   open\_history\_item

## One memory, nine products

Connect

What goes into the memory

-   [SystemsThe events your systems already emit, tied to the right customer.](/en/produtos/sistemas)

SDK, API and MCP

Any agent connects to the memory with three calls, in Python, TypeScript, HTTP or MCP.

[See the documentation(opens docs.niadra.com)](https://docs.niadra.com/en)

Remember

What the memory knows

-   [MemoryWhat was said and done, with a date, a source and evidence.](/en/produtos/memoria)
-   [IdentityPeople, companies and partners, recognized on any channel.](/en/produtos/identidade)
-   [PatternsWhat repeats, with the proof behind each signal.](/en/produtos/padroes)

Deliver

What each agent receives

-   [ContextWhat each agent needs to know before it starts.](/en/produtos/contexto)
-   HistoryYou are hereEverything that ever happened, for the agent to search.
-   [AlertsA signed webhook when one of your rules fires.](/en/produtos/avisos)

Govern

What your team controls

-   [MeasurementWhether each agent used the context it received.](/en/produtos/medicao)
-   [ConsoleWho read what, review, export and erasure.](/en/produtos/console)