Topolo Feed

Public overview of Topolo Feed in the Topolo application suite.

publicverified 2026-08-01feedapplication

What It Is

Topolo Feed is part of the Topolo business application suite. It turns activity across your content feeds into analytics: impression and engagement summaries, device breakdowns, scheduled digests, and anomaly alerts when engagement moves unexpectedly.

Architecture

Topolo Feed runs on Topolo's platform and signs you in through Topolo Auth. Your feed analytics are scoped to your organization and workspaces.

Workspace Management

The shared Topolo workspace control reads and manages app-scoped workspace identity through Topolo Auth: authenticated users can list, create, rename, choose a default, and delete an eligible workspace. Workspace IDs and slugs remain stable and exactly one default is explicit. The selected platform workspace scopes this application's app-owned records; the app retains only domain-specific deletion guards for default or non-empty workspaces.

Runtime Surfaces

The workspace is live at https://feed.topolo.app.

API Reference

Topolo Feed exposes its capabilities as Topolo actions — connecting sources, syncing activity, and reading summary, engagement, and device analytics — available through the Topolo SDK, CLI, and MCP surfaces.

Alongside these it publishes privacy and device-credential actions: export or delete your organization's Feed data, and rotate a device's credential.

Auth and Permissions

Access requires a Topolo account. Sign in through Topolo Auth to reach your organization's feed analytics.

Data Ownership

Topolo Feed owns your feed sources and the analytics derived from their activity — impressions, engagement, device breakdowns, digests, and anomaly records — scoped to your organization.

Personal and device-identifying values are encrypted at rest and bound to your organization, so they are not readable outside it. You can export everything Feed holds for your organization, or delete it, through the privacy actions.

Mobile Experience

The checked-in mobile experience contract is approved in native_capability mode. Its fallback route is /dashboard/devices, its offline policy is read_through_cache, and it requires organization context.

Published permissions: feed:read.

  • /dashboard/devices uses /api/widget with the record.list template and feed.devices.list data source.
  • /dashboard/media uses /api/widget with the record.detail template and feed.media.detail data source.

The native clients consume this manifest as an explicit rendering contract. A web mode record intentionally opens the product web experience; native_capability publishes the listed native routes and actions. Do not infer unlisted native behavior.

Deployments

Topolo Feed is available in production at https://feed.topolo.app.

Failure Modes

If a feed source cannot be reached, its latest sync is skipped and analytics reflect the last successful sync rather than showing stale data as current.

Debugging

If analytics look wrong, confirm the feed source is connected and syncing from the workspace settings.

Use It

Open Topolo Device Platform for the human product surface. The system handbook records its current hosts, ownership, Auth scopes, storage, deployment, failure modes, and machine artifact.

Discover the credential-scoped automation surface before making an API call:

topolo services --query topolo-device-platform --json
topolo actions --service topolo-device-platform --json
topolo actions capabilities --service topolo-device-platform --json

Choose an action, inspect it with topolo actions get <action-id> --json, then validate and plan a published example. The Agent Actions reference exposes the same public schemas, effects, examples, verification, and recovery guidance.

Example workflow:

  1. Confirm the active identity and organization with topolo whoami --json.
  2. Discover Topolo Device Platform and select one published action rather than guessing a route.
  3. Inspect its input/output schemas and published example.
  4. Validate and plan the exact payload; obtain confirmation for a mutation.
  5. Execute and perform every published verification step.

Change Log / Verification

  • Reconciled this page against apps/TopoloFeed origin/staging e157a439a3f2 on 2026-08-01 after reading a2ac292 (feat: close Feed enterprise privacy and device auth). Added the customer-facing privacy and device-credential actions to API Reference and the at-rest protection statement to Data Ownership.

  • Verified the native_capability mobile experience contract and its 2 published route(s) against apps/TopoloFeed origin/staging d6b87c5d8495 on 2026-07-27.

  • Reconciled this page against apps/TopoloFeed origin/staging d57457e4594f on 2026-07-24 after reviewing every docs-relevant commit since its previous verification watermark. Dependency-only currency commits were checked by the fleet production-dependency gate and did not change this page's product contract.

  • Consolidated Feed under the canonical Topolo Device Platform system identity on 2026-07-22.

  • Published overview on 2026-07-20.