Application SKU catalog audit
audit_application_skus, discord://application/skus, and review_application_skus belong to the connector toolset and inspect only the verified current application's complete SKU catalog. The caller supplies no application ID. Each read re-verifies the pinned application and bot before issuing the exact List SKUs request. The audit adds no credential, configuration field, policy gate, write authority, Gateway connection, activity record, cache, or persistent file.
The strict projection returns exact SKU IDs, bounded transient untrusted names and slugs with Unicode scalar counts, normalized durable, consumable, subscription, and subscription-group types, availability, known guild and user subscription flags, a derived purchase-scope classification, catalog aggregates, and fixed findings. Unknown future types preserve only their numeric code; unknown fields and flag bits are counts only. The service rejects duplicate or malformed IDs, cross-application records, malformed Unicode or controls, invalid integers, excess fields, oversized payloads, and inventories above its defensive 100-record ceiling. Discord separately documents a maximum of 50 owner-created SKUs and generated subscription-group records in Managing SKUs; the wider local ceiling is headroom, not an asserted Discord API maximum.
Benefits, prices, media, store URLs, entitlement and subscription objects, purchaser IDs, beneficiary guild IDs, payment data, raw payloads, and unknown values are omitted. Availability is catalog evidence, not proof of entitlement, subscription, payment, revenue, or access, and the audit never guesses why a record is unavailable. The audit does not call entitlement or subscription endpoints and grants no SKU or entitlement mutation authority; separately configured entitlement lifecycle writes must re-audit the complete catalog themselves. The guided prompt calls the audit exactly once, treats names and slugs as untrusted data, explains incomplete future evidence and these limits, and stops without a write.
Canonical source: docs/reference.md
Documentation generated for guildcontrol@0.0.0. Canonical source and edit history remain in the public repository. GuildControl is an independent project and is not affiliated with or endorsed by Discord Inc. Discord is used only to identify the platform that GuildControl connects to.