Authentication

Learn how to securely authenticate OpenClaw AI agents and applications with the ClawPay platform.

Overview

ClawPay provides on-chain banking infrastructure for autonomous AI agents. Authentication is handled through the Model Context Protocol (MCP) interface for secure, permission-based financial operations.

MCP Authentication

Configure your OpenClaw agent from the agent dashboardarrow-up-right.

Agent Key Types

Type
Prefix
Usage
Permissions

Agent Key

ak_live_ or ak_test_

AI agent operations

Autonomous banking operations

Service Key

sk_live_ or sk_test_

Backend services

Full platform access

Observer Key

ok_live_ or ok_test_

Monitoring agents

Read-only access

Environments

  • Mainnet: *_live_* keys interact with real assets on Solana mainnet

  • Devnet: *_test_* keys use test SOL and tokens on Solana devnet

MCP Server Configuration

Configure your OpenClaw AI agent to connect to ClawPay's MCP server:

Claude Desktop Configuration

Add to your claude_desktop_config.json:

Programmatic MCP Connection

Direct API Authentication

For non-MCP integrations:

Security Best Practices

1. Keep Agent Keys Secret

Never expose agent keys in:

  • Agent prompt configurations

  • Public repositories

  • Log files or error messages

  • Agent memory/context that might be shared

2. Rotate Agent Keys Regularly

3. Use Permission Scopes

Agent Authorization Policies

Transaction Limits

Multi-Agent Authorization

Rate Limiting

Tier
Rate Limit
On-Chain Ops/min
MCP Calls/min

Starter

60 API req/min

10 tx/min

120 calls/min

Pro

600 API req/min

60 tx/min

1200 calls/min

Enterprise

Custom

Custom

Unlimited

On-Chain Transaction Signatures

All blockchain transactions require proper signing for agent autonomy.

Agent Wallet Configuration

Transaction Verification

Agent Session Management

Encryption & Security

All sensitive data and agent credentials are encrypted:

  • Agent keys: AES-256-GCM encryption at rest

  • Wallet private keys: Hardware security modules (HSMs)

  • Agent memory/state: Encrypted and isolated per agent

  • Transaction metadata: Zero-knowledge proofs on-chain

  • MCP communications: TLS 1.3 with certificate pinning

Compliance & Regulatory

ClawPay neobank is compliant with:

  • SOC 2 Type II: Annual security audits

  • GDPR: EU data protection and agent data handling

  • CCPA: California privacy rights

  • Bank Secrecy Act (BSA): AML/KYC for agent-initiated transactions

  • FinCEN: Virtual currency reporting requirements

Security Audits

View our latest security and smart contract audit reports:

Reporting Security Issues

Found a vulnerability in ClawPay or our MCP server? Please report it responsibly:

Do not disclose security issues publicly until we've had a chance to address them. We aim to respond within 24 hours and patch critical issues within 7 days.

Next Steps

Last updated