v2.0.0

Major Changes

• #114 7110b25 Thanks @EmmaLouise2018! - Persona-based API architecture for Agentic Platform v2

  Complete rebuild of the Scope3 SDK with persona-based design for the Agentic Platform v2 API.

  New Features:

  • Unified Scope3Client with persona parameter: buyer or partner
  • Full CLI with scope3 command for all API operations
  • REST and MCP adapter support
  • Buyer resources: advertisers, campaigns (discovery/performance/audience), bundles, signals, reporting, sales agents, conversion events, creative sets
  • Partner resources: partners, agents (with OAuth flows)

  CLI Highlights:

  • scope3 config set apiKey <key> - persistent configuration
  • scope3 commands - list all available commands by persona
  • Table, JSON, and YAML output formats
  • Environment support: production and staging

  Breaking Changes:

  • Removed Scope3AgenticClient - use Scope3Client with persona parameter
  • Removed brand persona - brands are now integrated into advertisers via brandDomain
  • Campaign type bundle renamed to discovery
  • Reporting moved from advertiser sub-resource to top-level client.reporting
  • Removed auto-generated types from OpenAPI (now manually maintained)
  • Auth uses Authorization: Bearer header (was x-scope3-api-key)
  • Response envelope: { data, pagination, error } (was flat)
  • MCP uses single api_call tool (was per-resource tools)

  Migration Guide:

  // Before (v1):
  import { Scope3AgenticClient } from 'scope3';
  const client = new Scope3AgenticClient({ apiKey: '...' });
  
  // After (v2):
  import { Scope3Client } from 'scope3';
  
  // For buyers (advertisers, campaigns, bundles):
  const buyerClient = new Scope3Client({ apiKey: '...', persona: 'buyer' });
  
  // For partners (agent registration, OAuth):
  const partnerClient = new Scope3Client({ apiKey: '...', persona: 'partner' });