Give your agents
relationship context.

Start with a real workspace.

WoN exposes the Relationship Protocol through REST and MCP. For the current release, SalePiper provides the browser console for sign-in, setup, access management and approving agent connections.

1. Open SalePiper and sign in with Intergraph.
2. Choose Set up SalePiper to install its program and create your contact and deal collections.
3. Add a couple of contacts and a deal so your agent has useful, authorized context to work with.

Your personal workspace is created when you sign in. A workspace owner can also manage team membership and collection access. Adding a represented agent or a membership record does not itself grant access.

Connect through MCP.

Use an MCP client that supports OAuth authorization-code flow with PKCE. Add WoN as a remote server using this URL:

Complete the client’s authorization flow. WoN directs you to the approval screen in SalePiper, where you select a workspace, collections and scopes. Start with read-only access, then approve additional capabilities only when needed.

The implementation exposes standard discovery documents, dynamic public-client registration, PKCE S256, rotating refresh tokens and revocation. Access tokens last 15 minutes; approved connections expire after 30 days.

Discover before you change.

A useful first interaction is to ask your connected agent:

List the workspaces and collections available to this connection.
Search the records I have approved for you to read.
Show the available commands for a deal, without changing it.

The corresponding MCP tools include workspace_list, collection_list, record_search and command_list. The tool descriptions and schemas are available through MCP discovery.

Use the same operations over REST.

For an OAuth client or integration holding an approved WoN access token, call POST /v1/operations. This example is read-only. Replace both placeholders with values from your authorized connection and workspace.

curl https://api.wealthofnetworks.com/v1/operations \
  -H 'Authorization: Bearer YOUR_WON_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  --data '{
    "operation": "record.search",
    "arguments": {
      "workspace_id": "YOUR_WORKSPACE_UUID",
      "namespace": "salepiper",
      "limit": 20
    }
  }'

The OAuth issuer is https://api.wealthofnetworks.com and the resource is https://api.wealthofnetworks.com/mcp. An integration must use the approved OAuth flow; the example does not create or bypass a grant.

For protocol details, see authorization server discovery and protected resource discovery.

Make changes deliberately.

A write-capable agent should inspect the target record and discover the allowed commands before attempting a transition. Updates require expected_revision; mutations also require an idempotency_key.

Use command.execute to move a record through its declared lifecycle. A direct record patch cannot bypass lifecycle rules. An agent’s connection scopes and current collection permissions must both permit the operation.

When an operation emits a work request, it records an intent. WoN does not execute outreach, dispatch arbitrary tools, or independently verify that a sale or delivery happened.

Define your own application.

Start from the SalePiper or community program package. Define your types, participant roles, schemas, lifecycles and commands, then draft and activate a version through the console or an explicitly authorized connection.

Programs are declarative JSON packages, not uploaded executable code. Versions are immutable. Submit a higher version to change a definition; existing records keep their original version.

See the full technical reference for the schema subset, operation requirements, limits, paging and error behavior.

Know the current boundaries.

The initial implementation supports authorized records, bounded rules, versioned programs, durable history and changes through REST and MCP. It does not provide automatic contact merging, arbitrary graph traversal, cross-workspace references, hosted agent execution, CRM vendor adapters, or automatic migrations of existing records between program versions.

The native store is PostgreSQL. The protocol’s meaning is independent of that implementation choice.