T Topolo Docs
application public active Verified 2026-05-14

Agent

Agent and automation workspace for threads, workflows, approvals, operator execution, and reusable source-backed person profiles for writing and speaking style.

Documentation Map

What It Is

Agent and automation workspace for threads, workflows, approvals, operator execution, and reusable source-backed person profiles for writing and speaking style.

Architecture

Owners: ai-platform

Source repos:

Dependencies: topolo-auth, applications-packages, topolo-developers, topolo-p2p, topolo-nexus, topolo-voice

Repo shape

No repo surface entries were detected from the registered repo paths.

Runtime Surfaces

Hosts:

https://agent.topolo.app https://topolo-agent.pages.dev https://agent.stg.topolo.us https://agent-api.stg.topolo.us https://topolo-agent-staging.pages.dev https://topolo-agent-stg.topolo-staging.workers.dev

No wrangler surface was discovered under the registered repo paths.

API Reference

Coverage: curated

Source: PlatformApplications/TopoloDocs/src/content/public/applications/agent.mdx

Source exists in repo: no

Canonical Agent coverage now lives in the docs application. The backend worker now requires Topolo Auth validation for operator bearer tokens and no longer carries an Agent-local HS256/JWT secret verification path. Browser preboot, shared browser auth, backend Auth validation, widget output, seed validation, and downstream connector headers resolve concrete service ids from Auth service slugs such as `topolo-agent` at runtime instead of carrying concrete service ids in source, Worker vars, build commands, or browser assets. The production Pages `/login` entry renders the shared branded first-party login surface and submits email/password credentials to Auth through the shared client; OAuth and other brokered flows still use hosted Auth. The connector catalog uses the Developers-owned mobile app catalog connector for Android and iOS artifact metadata. Agent exposes `GET /api/widget` for TopoloOne live workspace with active-flow, pending-task, pending-approval, and run-today stats. Agent also exposes `POST /api/public/chat` for the public Lois website-chat assistant embedded by TopoloOne; that route owns persona selection, Turnstile-backed session clearance, source links, rate limiting, and action/deeplink metadata. Agent owns authenticated `/api/person-profiles` routes backed by `person_profiles`, `person_profile_sources`, and `person_profile_style_snapshots` so products can reuse source-backed writing style, speaking style, persona rules, usage policies, authorization evidence references, and Voice profile links without turning every profile into an executable agent. The browser workspace now includes a standalone Person Profiles surface for profile editing, source capture, style reads, and draft preview generation, and the backend exposes `POST /api/person-profiles/:id/preview` for authenticated source-backed previews. Person-profile access is restricted to the subject user and organization admins, not normal peer users. Cross-organization agent actions must enter through TopoloP2P and wait for the P2P policy decision before execution. Staging runs in the separate Topolo Staging Cloudflare account with staging Auth, Nexus, D1, R2, Queue, and Vectorize bindings, and browser/backend fallback URLs resolve to the staging custom domains before production.

App API page: /reference/apps/topolo-agent

This system currently relies on a curated or README-derived contract surface instead of a source-controlled OpenAPI spec.

Auth and Permissions

Depends on Topolo Auth: yes

Service IDs:

srv_luiWkJLNbOMG

API key scopes

agents.read

View configured agents and their settings

Resource pattern: none

agents.write

Create and update agent definitions

Resource pattern: none

approvals.write

Approve or reject gated Agent actions

Resource pattern: none

knowledge.read

View agent knowledge sources and indexed documents

Resource pattern: none

knowledge.write

Manage agent knowledge sources and indexed documents

Resource pattern: none

reports.read

View reports, artifacts, and work feed output

Resource pattern: none

runs.invoke

Invoke agent runs and inspect their output

Resource pattern: none

workflows.read

View workflow plans and runs

Resource pattern: none

workflows.write

Create and run workflow plans

Resource pattern: none

workspace.read

View the Agent operating workspace

Resource pattern: none

workspace.write

Update workspace state and org memory

Resource pattern: none

Service permissions

agents:read, agents:write, approvals:write, knowledge:read, knowledge:write, reports:read, runs:invoke, workflows:read, workflows:write, workspace:read, workspace:write

Data Ownership

No storage bindings were derived from wrangler configuration.

Queues / Cron / Workflows

Queue bindings:

No queue bindings were detected.

Cron triggers

No cron triggers were detected.

Workflow signals

No explicit queue/workflow script or cron signal was discovered.

Environment Variables and Bindings

Environment variables:

No environment variables were derived from wrangler configuration.

All wrangler bindings

No bindings were derived from wrangler configuration.

Deployments

Deployment environments: default only or not declared

Routes: workers.dev or Pages-only delivery

Observability enabled: no explicit setting found

Failure Modes

  • No wrangler.toml surface was discovered under the registered repo paths.
  • The registered contract source is missing: PlatformApplications/TopoloDocs/src/content/public/applications/agent.mdx
  • Neither OpenAPI nor README-derived interface detail was found.

Debugging Runbooks

Start with these entrypoints:

  • PlatformApplications/TopoloDocs/src/content/public/applications/agent.mdx

Change Log / Verification

Lifecycle: active

Last verified: 2026-05-14

Any code change to this system is expected to update the canonical docs in PlatformApplications/TopoloDocs and refresh the verification date.