> ## Documentation Index
> Fetch the complete documentation index at: https://docs.antigen.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How agents use Asset Map

Your organization has one live Asset Map. Every offensive security run can access it, whether it uses [tCell](/docs/runs/tcell) or a custom agent built with the Agent SDK.

The Asset Map lets agents analyze your infrastructure as a system. They can see how services, identities, deployments, and configuration connect, then use those relationships to investigate attack paths across your environment.

## One map for every run

As you connect more infrastructure, every future offensive security agent run against your organization is equipped with additional context.

This means you do not need to describe the same environment separately to each agent. The Asset Map remains the shared source of context across your runs.

## Find risk in overlooked services

Consider a team with many Railway projects. Someone who has since left the company deployed an internal tool, and the team no longer knows it exists. After connecting Railway to Antigen, the deployment appears in the Asset Map.

The service is live on the public internet. It has unprotected API routes and access to a database. Without the Asset Map, that service can be easy to miss. With it, an agent can see the public deployment, the exposed routes, and the database relationship together, then investigate whether the service is exploitable.