SITEMAP / DOCS / AGENTS

Quickstart

90 seconds from zero to a working customer-context call.

011. Get an API key

Sign in to https://platform.waypath.app, then Settings > API Keys > Issue Key. Pick the scopes you need (most agents want context:read + memory:write). Copy the wp_live_... secret. You will not see it again.

022. Pick your path

MCP (Claude Desktop, Cursor)

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

That registers four tools with your local Claude:

For Claude Desktop, the equivalent JSON config lives in ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "waypath": {
      "command": "npx",
      "args": ["-y", "@waypath/mcp"],
      "env": {
        "WAYPATH_API_KEY": "wp_live_..."
      }
    }
  }
}

Restart Claude Desktop. Ask "what do you know about jane@acme.com" and it will call get_customer_context automatically.

REST

curl https://api.waypath.app/v1/context?email=jane@acme.com \
  -H "X-API-Key: wp_live_..."

const res = await fetch(
  'https://api.waypath.app/v1/context?email=jane@acme.com',
  { headers: { 'X-API-Key': process.env.WAYPATH_API_KEY! } }
)
const ctx = await res.json()

import os, requests
ctx = requests.get(
    'https://api.waypath.app/v1/context',
    params={'email': 'jane@acme.com'},
    headers={'X-API-Key': os.environ['WAYPATH_API_KEY']},
).json()

CLI

Coming soon — @waypath/cli is not yet on the npm registry. Use the REST / TS / Python forms above until the package ships.

npm i -g @waypath/cli
wp init                          # paste your wp_live_... key
wp ctx jane@acme.com             # prints customer context

033. Write a decision back

After your agent acts, log it:

curl https://api.waypath.app/v1/memory \
  -H "X-API-Key: wp_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "customer": "cus_8af2",
    "type": "decision",
    "agent": "support_v2",
    "payload": { "action": "escalate_to_human", "reason": "customer_frustrated" },
    "idempotency_key": "esc-1284-v2"
  }'

That entry shows up on the customer's timeline and feeds the next get_customer_context call as a recent_decisions row.

04See also