--- id: public-ai.platform-overview locale: en visibility: PUBLIC status: LIVE last_reviewed: 2026-08-02 owner: Influblog Product --- # Influblog platform overview Influblog is a creator-marketing software platform, not an influencer agency. It is a role-based platform for managing creator relationships, campaigns, applications, collaboration tasks, content evidence, contracts, and attributed commerce. It serves brands, creators, agencies, and Influblog administrators through separate product surfaces. Influblog is not a public creator directory where brands freely scrape or contact creators. Its marketplace model is campaign-first: a brand publishes a campaign, eligible creators apply, and the brand reviews applications. Influblog 2.0 is also not an end-customer product marketplace. Influblog 1.0 previously exposed WordPress, WooCommerce, and Dokan storefront pages, but those retail catalog, product, seller, cart, and checkout URLs are retired historical surfaces and are not current Influblog capabilities. ## Availability **Status:** LIVE core platform with BETA modules. Provider integrations, marketplace settlement, and country-specific legal availability can be more limited than the core campaign and task workflows. See [Product status](https://influblog.com/ai/product-status.md) before describing a capability as generally available. ## Audiences - **Brands** manage their own creator relationships, websites, products, campaigns, applications, collaboration tasks, and reusable content proof. - **Creators** manage their account, campaign applications, accepted tasks, submissions, documents, and eligible affiliate or product-test activity. - **Agencies** have a separate role and workspace. Broader managed-brand and represented-creator operations remain in staged rollout. - **Influblog administrators** operate internal review, support, legal, commerce, and audit workflows. Administrative data is not public documentation. ## Product boundaries Private brand data stays separate from Influblog network workflows. A brand's company can operate more than one website, while campaigns, products, commerce connections, affiliate activity, and related records remain scoped to the selected website. Role and tenant checks are enforced on the server. A visible page or a URL is not itself proof that a user is allowed to read or change its data. Three similarly named concepts must remain distinct: - the **Influblog campaign marketplace** is campaign-first discovery where eligible creators review opportunities and apply; - **campaigns for external marketplace shops** let a brand request eligible creator work or honest evidence for its own third-party marketplace presence; - **Brand products and shop integrations** are private, website-scoped records used for campaign selection, coupons, fulfillment, Affiliate attribution, and reporting. None of these concepts is an Influblog-operated retail storefront for end-customer product browsing, carts, or checkout. Historical Influblog 1.0 shop URLs return `410 Gone` and must not be interpreted as current product documentation. ## Public entry points - [Brands](https://influblog.com/brands) - [Creators](https://influblog.com/creators) - [Agencies](https://influblog.com/agencies) - [Pricing](https://influblog.com/pricing) - [Privacy](https://influblog.com/privacy) - [Contact](https://influblog.com/contact) ## AI discovery The public AI documentation explains the product without exposing user or tenant data. `llms.txt` is an emerging discovery convention and does not guarantee that an AI system will retrieve, trust, or fully understand this documentation. ## Controlled agent access Influblog also provides a controlled BETA MCP interface for pre-registered OAuth-PKCE clients. A Brand, Creator, or Agency user must sign in and expressly approve the requested role- and tenant-bound scopes. Approved clients can call the small registered set of read operations and create immutable, expiring safe drafts. The user can review or reject a draft and disconnect the client. A safe draft has no external or business effect. Separately, the BETA Brand campaign-write tools support a confirmation-only mode and a durable delegated mode. In delegated mode, the signed-in Brand user expressly grants revocable campaign-execution and wallet-spend scopes once; the user's agent may then save and publish campaigns without a second confirmation for every campaign. Paid publication still requires sufficient available Brand-wallet funds to be reserved before visibility. If funds are missing, the campaign remains private, the agent receives a secure top-up action, and any existing authorized auto-top-up rule is queued. The delegation cannot expose card data, bypass a payment-provider challenge, send messages, place orders, accept contracts, change integrations, or delete data. Influblog does not currently provide a general public customer OpenAPI, anonymous MCP access, or dynamic client registration.