AZPC Architecture & Data Interfaces

Architecture

The World of Warcraft addon observes supported in-game events and writes structured local data. The Windows companion reads eligible addon output, manages the user-facing connection lifecycle, and synchronizes supported records. The Cloudflare Worker serves the application, validates requests, renders crawlable pages, and coordinates D1 persistence.

Public and private boundaries

Public item, realm, history, directory, mover, flip, guide, and documentation pages support market research. Account-specific trading events and portfolio analytics require authentication. Credentials, protected write routes, and operational security controls are intentionally excluded from public documentation.

Market and item identifiers

Market requests identify a supported realm and faction. Current realm slugs include dreamscythe and nightslayer; faction slugs include horde and alliance. Canonical item pages use the numeric World of Warcraft item ID plus a readable slug; integrations should treat the numeric ID as authoritative.

Read-interface conventions

Public read responses can include timestamps, copper-denominated prices, observation collections, readiness flags, confidence labels, and reasons when evidence is insufficient. Missing guidance must not be interpreted as a zero price.

Caching and responsible use

Public pages and read responses may be cached. Clients should avoid unnecessary repeated requests and must not bypass authentication, access controls, or rate limits.

Stability

AZPC's current interfaces primarily support the AZPC application. Until a separately versioned public API is announced, routes and fields can change. Contact AZPC before building a production dependency.

One source of truth

Market guidance and accounting logic should remain centralized so the website, addon, companion, and future clients do not calculate conflicting answers.

Market methodology · Public item directory · Contact AZPC