Skip to Content
SDKTrigger Payload Guide

Trigger Payload Guide

Trigger payload quality controls policy matching, reviewer clarity, and callback reconciliation.

Minimal trigger example

import { Beav3r } from '@beav3r/sdk'
 
const client = new Beav3r({
  baseUrl: 'https://staging.server.beav3r.ai',
  apiKey: process.env.BEAV3R_API_KEY!,
  agentId: 'treasury_payout_agent',
  defaultExpirySeconds: 180
})
 
await client.guard({
  actionType: 'payments.send_usdt',
  payload: {
    amount: 4200,
    asset: 'USDT',
    network: 'base',
    recipient: '0x1111111111111111111111111111111111111111',
    summary: 'Merchant payout exceeds approval threshold',
    presentation: {
      title: 'Send USDT',
      subtitle: 'Treasury payout agent',
      contextLabel: 'Flow',
      contextValue: 'Merchant payout',
      technicalType: 'payments.send_usdt',
      fullCommand: 'send 4200 USDT on base to 0x1111111111111111111111111111111111111111'
    }
  },
  attributes: {
    amount: 4200,
    merchant_name: 'Treasury Ops',
    display_category: 'merchant payout'
  }
})

Use https://server.beav3r.ai in production.

Field guidance

  • agentId: stable caller identity (treasury_payout_agent).
  • actionType: stable technical action for policy matching (payments.send_usdt).
  • payload: full action data and reviewer context.
  • attributes: flat scalar fields optimized for policy conditions.

Policy vs rendering

Policy primarily matches on:

  • actionType
  • attributes
  • selected scalar fields in payload

Review rendering primarily uses:

  • agentId
  • payload.presentation.*
  • selected factual fields from payload

Use SDK API Reference for method signatures and Callbacks from the SDK for callback behavior.

First Onchain ScriptCallbacks from the SDK