Skip to Content
AgentsOverview

Agents

Waypath is the customer memory layer for AI agents. One read primitive, three write primitives. REST + MCP.

Most agent code looks the same: pull customer state, take an action, write what happened back. Waypath is the API on either side of that loop. Your agent never has to crawl five SaaS tools to figure out who it is talking to.

The four primitives

VerbEndpointPurposeP50
GET/v1/context/:id or /v1/context?email=Token-budgeted customer state.120ms
GET/v1/account/:idB2B account roll-up. Contacts, opps, blockers, trajectory.180ms
POST/v1/memoryTyped write. decision, action, or observation. Idempotent.60ms
POST/v1/eventsMarketing event ingest. Identity resolves email then phone then externalId.80ms

Two ways in

MCP. One command and Claude Desktop can call all four primitives:

claude mcp add --transport http waypath https://mcp.waypath.app -s user

REST. Same surface, any language. Send X-API-Key: wp_live_... and hit https://api.waypath.app.

What the agent sees

{ "customer": "Jane Doe . Acme (250-1000)", "customer_id": "cus_8af2", "lifecycle_stage": "opportunity", "sentiment_trajectory": { "30d": "declining", "trigger": "support_ticket_unresolved" }, "intent_signals": ["viewed_pricing_3x", "downloaded_whitepaper"], "open_loops": ["awaiting_security_review"], "blockers": ["procurement_review_q2"], "recent_decisions": [ { "agent": "support_v2", "action": "escalate_to_human", "outcome": "ticket_resolved", "ts": "2026-04-12T14:22:11Z" } ] }

That is one HTTP call. The same payload comes back through MCP via get_customer_context({ email }).

Where to start

Internal agent ecosystem

The same primitives back Waypath’s own multi-buddy system, an orchestrator plus four specialists that drive the dashboard.


SYNC · OK© 2026 WAYPATHBUILD · D-03SOC2 · IN PROGRESSWAYPATH.APP