Getting started

  1. Connect your wallet

    Open the app and click Connect wallet. Waypoint works with MetaMask or any other DeFi wallet. Connecting is read-only — nothing is signed, nothing moves. If your wallet is on the wrong network, the app shows a Switch button and handles it, adding the network if your wallet doesn’t have it yet.

  2. Create a session

    Go to Sessions and click New session. Give it a name that matches the job — “Trading desk”, “Yield watcher”. The app shows the session’s credential once:

    wpt_sess_Zk4hT9v2mQ8xW1nR5pL7cJ3f

    Copy it and store it securely. We keep only a fingerprint (a hash) of it, so we can’t show it again — if you lose it, click Rotate credential to get a fresh one. Rotating kills the old credential instantly; the session’s allowances stay as they were.

    Whoever holds the credential holds the session — treat it accordingly.

  3. Give it an allowance

    Click Add allowance on the session. You choose:

    • What it can do — pick from the waypoints in the Directory. Only spending functions need a grant; quotes and balance checks are always free to read.
    • The budget — a hard cap, in dollars. The model can never spend past it. You can raise, lower, or remove it any time.
    • What it can receive — which tokens the model is allowed to end up holding for you. Anything it buys lands in your wallet, or the transaction reverts.
    • When it expires — optional. After the date, the allowance is voided without you doing anything.

    Then you sign one standard token approval in your wallet. Concretely, a $500 budget is this call, signed by you, at the USDC contract:

    USDC.approve(executor, 500_000000)   // USDC has 6 decimals; 500_000000 = $500

    That’s the whole ceremony: no funding step, no transfer, no new account. approve can only be signed by the wallet that holds the tokens — yours — which is why a model can never raise its own cap. Your money stays where it is until the moment a call actually spends it, and it can only be spent inside the box you just drew.

  4. Connect your AI

    Your model talks to Waypoint through its credential. There are two ways to connect it.

    If your AI supports MCP (Claude, Cursor, and most modern agent tools), add Waypoint to its connector config and restart it:

    {
      "mcpServers": {
        "waypoint": {
          "command": "node",
          "args": ["path/to/waypoint-mcp/dist/stdio.js"],
          "env": {
            "WAYPOINT_SESSION": "wpt_sess_your_credential",
            "WAYPOINT_API": "https://api.waypoint.world"
          }
        }
      }
    }

    The Waypoint tools appear on their own — scoped to exactly what that credential was granted. A session granted only “swap” sees swap and quote, plus the fixed meta-tools (waypoint_state, waypoint_request_budget, waypoint_request_grant). Nothing else exists for it to call.

    If it doesn’t support MCP, Waypoint is a plain web API. The model authenticates with its credential and asks what it may do:

    curl https://api.waypoint.world/session/state \
      -H "Authorization: Bearer wpt_sess_Zk4hT9v2mQ8xW1nR5pL7cJ3f"
    {
      "session":   { "name": "Trading desk", "verbs": ["read", "propose", "execute"] },
      "allowance": { "capUsd": "500.00", "spentUsd": "112.40", "remainingUsd": "387.60" },
      "routes": [{
        "route": "uniswap:swap",
        "functions": ["swap", "quote"],
        "tokens": { "in": "USDC", "out": ["WETH", "cbBTC"] },
        "expiry": "2026-12-31T00:00:00Z"
      }]
    }

    The response is the whole contract: what the session may do, with how much, until when. There is no separate configuration to keep in sync — the credential is the configuration.


Get on Waypoint

The sky is clear. Your model is trading.

Tuesday, Jul 21 San Francisco, CA ☀︎ 68°F