Guides
Site memory cookbook
Patterns for structuring site memory across common verticals.
Site memory cookbook
Five patterns to copy. Each is the smallest snapshot that makes agents fast on a real site.
1. E-commerce store
2. SaaS dashboard
3. Travel booking
4. Per-page live context
Use provideForPage for state that changes between renders. Site-level memory stays static; per-page memory moves with the route.
5. Publishing the well-known endpoint
Agentronics serves the well-known JSON via the gateway, but most enterprises expose it on their own domain so unsupported agents can fetch it without involving us.
Mount the handler at /.well-known/agent-context.json. Agents that find it can reason about your site in under a second.
When to choose what
- Static, evergreen context →
provideSiteMemoryonce at boot. - Dynamic per-route state →
provideForPageon route change. - Gateway-authored content →
await client.syncSiteMemory()on init. - Cross-platform agents that may not have an SDK → publish the well-known endpoint.