Skip to main content

​
Core Concepts

Before integrating with Conto, it’s helpful to understand the key concepts and terminology.

​
Agents

An Agent represents an AI agent registered with Conto. Each agent has:
  • Name - Human-readable identifier
  • Type - The agent framework (OpenAI, Claude, LangChain, Custom)
  • Public Key - Unique cryptographic identifier
  • Status - Active, Paused, Suspended, or Revoked
  • SDK Keys - API keys for authentication
// Example agent configuration
{
  name: "Customer Support Agent",
  agentType: "OPENAI_ASSISTANT",
  publicKey: "0x1234...",
  status: "ACTIVE"
}

​
Wallets

A Wallet holds stablecoins for agent payments. Wallets can be linked to multiple agents with different spend limits.
PropertyDescription
addressWallet address
balanceCurrent stablecoin balance
statusActive, Frozen, or Closed
When you link an agent to a wallet, you configure:
  • Spend Limits - Per-transaction, daily, weekly, monthly limits
  • Time Windows - Allowed hours and days for transactions
  • Delegation Type - Full, Limited, or View-Only access
// Example agent-wallet link
{
  spendLimitPerTx: 500,      // Max $500 per transaction
  spendLimitDaily: 2000,     // Max $2,000 per day
  spendLimitMonthly: 20000,  // Max $20,000 per month
  allowedHoursStart: 9,      // 9 AM
  allowedHoursEnd: 17,       // 5 PM
  allowedDays: ["Mon", "Tue", "Wed", "Thu", "Fri"]
}

​
Policies

A Policy is a set of rules that determine whether a payment should be approved, denied, or require manual approval.

​
Policy Types

Spend Limit

Control maximum amounts per transaction, day, week, or month

Time Window

Restrict transactions to specific hours and days

Counterparty

Control which recipients are allowed based on trust

Geographic

Block transactions to sanctioned countries (OFAC compliance)

Category

Allow or block specific spending categories

Approval Threshold

Require manual approval above certain amounts

​
Policy Priority

Policies are evaluated in priority order (highest first). This allows you to:
  1. Create override policies (priority 90+) for critical rules
  2. Set default policies (priority 50) for normal operations
  3. Add catch-all policies (priority 10) for fallbacks

​
Transactions

A Transaction represents a stablecoin payment from a wallet to a recipient.

​
Transaction Lifecycle

​
Transaction Properties

PropertyDescription
txHashBlockchain transaction hash
amountPayment amount
statusCurrent transaction status
policyResultPolicy evaluation result
purposeReason for payment
categorySpending category

​
Counterparties

A Counterparty is a recipient of payments (vendor, exchange, protocol, etc.).

​
Trust Levels

LevelScore RangeDescription
TRUSTED0.75 - 1.0High confidence, minimal restrictions
VERIFIED0.5 - 0.75Established relationship, standard monitoring
UNKNOWN0.2 - 0.5New or limited history, requires scrutiny
BLOCKED0.0 - 0.2High risk, all transactions blocked

​
Trust Score Factors

Trust scores are calculated based on:
  • History (30%) - Transaction count and volume
  • Reliability (30%) - Success rate, failed transactions
  • Activity (20%) - Account age, recency, consistency
  • Verification (20%) - Manual verification, network data

​
Network Intelligence

Conto’s Network Intelligence provides anonymized cross-organization trust data:
  • See if other organizations have flagged an address
  • Benefit from collective fraud detection
  • Contribute to network safety (opt-in)
Network Intelligence data is anonymized. Organizations share aggregate trust signals, not transaction details.

​
SDK Keys vs API Keys

Conto uses two types of authentication:
Key TypeFormatPurpose
SDK Keyconto_agent_xxx...Agent payment operations
API Keyconto_xxx...Full platform API access
  • SDK Keys are scoped to a specific agent and can only perform payment operations
  • API Keys are scoped to an organization and can access all API endpoints

​
Next Steps

Quick Start

Set up your first agent

Policy Guide

Configure spending policies