Why should you care?

Analytics agent on a GPU worker must talk to CRM agent on API nodes without shared memory.

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.Messaging/AgentMessageBus.cs
public sealed record AgentEnvelope(string From, string To, string Intent, JsonDocument Payload);

public interface IAgentMessageBus
{
    Task PublishAsync(AgentEnvelope message, CancellationToken ct);
    IAsyncEnumerable<AgentEnvelope> SubscribeAsync(string agentName, CancellationToken ct);
}

What happened?

• AgentEnvelope carries intent and JSON payload between agents.
• SubscribeAsync lets HospitalTriageAgent listen without polling SQL.

Practice next

1. Define AgentEnvelope contract in AgentNest.Messaging.
2. build ServiceBusAgentMessageBus for production.
3. Use in-memory bus for local dotnet run.
4. Add reply-to field for request/response pattern.
5. Dead-letter envelopes failing schema validation.

Remember

Agents communicate via envelopes on a message bus. Keep payloads small and tenant-scoped. Use in-process handoffs inside one API; bus across services.

Cross-node hospital triage

Triage agent runs on edge; narrative agent on central API.

Outcome: Service Bus envelopes move FactBundle JSON with correlation IDs.