> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs-beta.getzep.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs-beta.getzep.com/_mcp/server.

# Solutions built with Zep

> Use Zep for enterprise context graphs, agent memory, and customer or account context.

Zep is the unified context layer for enterprise data. It combines business data, documents, and conversations into shared, governed context.

The three solution categories use the same [Context Lake](/context-lake) and Context Graph lifecycle. The correct solution depends on the subject of the context and the agents that can retrieve it.

#### [Enterprise context graphs](/enterprise-context-graphs)

Unify knowledge about projects, products, operations, and business domains for agents across your organization.

#### [Agent memory](/agent-memory-solution)

Give an agent context from past conversations, user activity, and changing preferences.

#### [Customer and account context](/customer-account-context)

Combine account records, conversations, and events so an agent can understand each customer's situation.

## Choose how the agent retrieves context

Each solution supports one-call grounding and an agent with Zep tools. For one-call grounding, a user graph uses `thread.get_user_context`, and a shared Context Graph uses [`graph.search`](/searching-the-graph#auto-search) with `scope="auto"`. For complex questions and tasks, the agent uses Zep through tools. See [Build an Agent with Zep](/build-an-agent-with-zep).

## Use more than one solution

One task can require context from multiple graph scopes. For example, a customer support agent can use account events, a user's previous conversations, and an enterprise support policy.

Keep each data set in the graph that matches its subject and access boundary. Retrieve only the context that the caller can access. Then combine the selected results in the application.

Use [Get started with Zep](/use-cases) for a graph-scope comparison. Use [Architecture patterns](/architecture-patterns) for ingestion and retrieval decisions.