Why should you care?

Product teams ship one agent per domain — CrmCopilotAgent, HospitalAssistantAgent — so permissions and telemetry stay isolated.

See it live — copy this example

Paste into an ASP.NET Core 8+ / AgentNest project, then run with dotnet run (set your API keys in user-secrets).

// AgentNest.Agents/Crm/CrmCopilotAgent.cs
public sealed class CrmCopilotAgent(IChatClient chat, CrmPlugin crm)
{
    public async Task<string> SummarizeAccountAsync(Guid accountId, CancellationToken ct)
    {
        var facts = await crm.GetAccountFactsAsync(accountId, ct);
        var response = await chat.GetResponseAsync(
            [$"Summarize this CRM account in 3 bullets:\n{facts}"], cancellationToken: ct);
        return response.Text;
    }
}

What happened?

• CrmCopilotAgent injects IChatClient and CrmPlugin.
• It fetches grounded facts first, then asks the model to summarize — the agent boundary is the class, not the raw API call.

Practice next

1. Define ICrmCopilotAgent and register CrmCopilotAgent as scoped.
2. build CrmPlugin with read-only CRM repository calls.
3. Add a CrmController endpoint that calls SummarizeAccountAsync.
4. Return a typed AccountSummary DTO instead of raw string.
5. Add IMemoryCache for account facts with a 60-second TTL.

Remember

Agents are DI services combining models, tools, and policy. Ground agents with repository facts before generation. One agent class per domain simplifies AgentNest security reviews.

CRM account briefings

Account executives open AgentNest before calls and need a 10-second brief.

Outcome: CrmCopilotAgent serves grounded summaries with CRM audit IDs attached.