Skip to main content

Getting Started with the Reward Agent

Connect your AI assistant to the Reward Agent in minutes. No installation required — the agent runs on Cloudflare Workers.

Prerequisites​

  • AI assistant that supports MCP over HTTP (Claude Desktop, Cursor, etc.)
  • For authenticated tools: a Resonance Partner Portal account

Connect via MCP​

Claude Desktop​

Add to your Claude Desktop MCP configuration:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Linux: ~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "resonance-agent": {
      "url": "https://agent.rsnc.network/mcp"
    }
  }
}

Cursor​

Add to your Cursor MCP settings (Settings → MCP → Add Server):

{
  "name": "resonance-agent",
  "url": "https://agent.rsnc.network/mcp"
}

Claude Code​

Add to your Claude Code MCP settings:

{
  "mcpServers": {
    "resonance-agent": {
      "type": "url",
      "url": "https://agent.rsnc.network/mcp"
    }
  }
}

Verify Connection​

After configuring, restart your AI assistant and try:

"What Resonance tools do you have available?"

The AI should list the 45 available tools. You can also test with a simple query:

"Show me network info from Resonance"

This calls rsnc_agent_network_info — a public tool that requires no authentication.

Public vs. Authenticated Tools​

27 public tools work immediately with no setup — browsing brands, viewing analytics, comparing programs, routing purchases, finding deals, perk intelligence, network flows, trending data, and AI-powered suggestions.

18 authenticated tools require an agent API key for operations like processing rewards, checking user balances, managing programs, stacking deals, tracking goals, and user behavioral profiling.

Get an Agent API Key​

To use authenticated tools, you need an API key:

  1. Log in to partners.rsnc.network
  2. Go to Settings → API Keys
  3. Generate an agent API key
  4. Note your Key ID and Secret

Passing Authentication​

Authenticated requests require three headers:

HeaderValue
X-RSNC-Agent-KeyYour agent key ID
X-RSNC-TimestampUnix timestamp (seconds)
X-RSNC-SignatureHMAC-SHA256 signature

See Authentication for the full signing process.

info

Most AI assistants handle authentication automatically when configured. You typically only need to implement HMAC signing if you're building a custom MCP client.

Quick Test: Browse Brands​

Try asking your AI:

"List all retail brands on the Resonance network"

This calls rsnc_agent_list_brands with a category filter — no auth required.

Quick Test: Check Brand Details​

"Tell me about the reward program for brand 0x..."

This calls rsnc_agent_brand_info to show events, reward amounts, and available perks.

Alternative Access: REST API​

If you prefer standard HTTP over MCP, use the REST API directly:

curl https://agent.rsnc.network/api/v1/network/info

See REST API Reference for all 45 endpoints.

Alternative Access: CLI​

Install the CLI for terminal-based access:

npm install -g @resonance/cli
rsnc network info
rsnc brand info 0xYourBrandId

See CLI Reference for all commands.

Next Steps​

Last updated on