Docs / Provider connections
Provider connection boundaries
Brandloop can integrate with generation, channel, billing, storage, support, and automation providers, but public buyers and agents should interact with Brandloop product workflows rather than raw provider credentials.
Generation providers
Generation providers power parts of the media workflow behind Brandloop. The public product boundary is Brandloop credits, generation jobs, reviewed outputs, and workspace assets.
Channel providers
Social and publishing connections should be described by current channel readiness and destination support. Do not claim universal direct publishing when a destination still requires staged rollout or review.
Billing and support providers
Billing and support tools can support the product, but public docs should avoid exposing provider secrets, internal account IDs, webhook secrets, or private operational runbooks.
Limitations and boundaries
- Provider connection docs do not grant direct provider access.
- Provider availability, billing readiness, and channel publishing status must be verified before specific launch claims.
- Private provider callbacks and credentials stay outside public crawler surfaces.
Common questions
- Should agents call Brandloop providers directly?
- No. Agents should use Brandloop public docs, API contracts, and scoped credentials rather than provider-level credentials.
- Does every provider connection mean the customer-facing feature is invoice-ready or fully live?
- No. Provider connectivity and customer-facing production readiness are separate evidence states.