Platform · 18 AI agents · one Marketing Operator

Eighteen agents. Five agents own the marketing loop.

Eighteen AI agents in one workspace. Five own marketing responsibilities buyers meet.

The rest run evidence, packaging, publishing adapters, and the control plane. Agents automate repeatable work; humans retain decision authority. 10× article throughput: 100–120/mo with one operator + 18 AI agents vs 10–12/mo from a 6-person freelance team.


Operated through

  • ChatGPT
  • Claude
  • Perplexity
  • Gemini
  • Grok
  • DeepSeek
  • Kimi
  • Google AIO
  • Copilot

Product architecture

Three layers. Different authority at each layer.

Client-facing agents own repeatable responsibilities.

They prepare observations, content, publishing work, website changes, and visual assets inside explicit human gates.

Supporting products make the work usable.

Parsing Stack gathers bounded evidence. Content Package Studio converts accepted work into a delivery that can be opened and verified.

The control plane governs the run.

Routing, rule compilation, proof, files, memory, handoff, and token policy stay operational machinery—not extra products in the shop window.


Solution · the Marketing Agents platform

Five agents own the marketing responsibilities — inside a workspace of eighteen agents.

One Marketing Operator coordinates five agents across visibility analysis, content production and quality gates, canonical publishing and distribution, technical website readiness and verification and repeatable visual asset delivery. Humans retain strategy, claims, approvals, and exceptions. The full workspace runs eighteen agents — marketing, support, control plane, and ops.

Agent 01 · measures · owns visibility analysis

Hermes Visibility

Comparable AI-visibility observations and governed opportunities.

Hermes preserves comparable observations and keeps mentions distinct from citations. AI Visibility Intelligence normalizes the evidence, ranks opportunities, and prepares the next governed handoff.

Open Hermes Visibility →

Agent 02 · produces · owns content production and quality gates

ContentOS

governed content packets with visible evidence.

ContentOS carries the prompt map, source boundary, draft, metadata, schema, checks, repair history, and human approval state together. Publishing authority stays in a separate product layer.

Open ContentOS →

Agent 03 · publishes · owns canonical publishing and distribution

Content Publisher

canonical-first publishing and bounded distribution.

Content Publisher preflights the destination, runs guarded publication, proves the live route, and keeps every approved channel adaptation connected by a visible source link.

Open Content Publisher →

Agent 04 · optimizes · owns technical website readiness and verification

Website Agentic Optimization

project-bound website changes with live proof.

The workflow can repair discovery, metadata, schema, links, layout, and performance within an approved scope. Passing CI remains human-review-required, and technical proof does not become a claim of causal attribution.

Open Website Agentic Optimization →

Agent 05 · designs · owns repeatable visual asset delivery

Visual Asset Studio

placement-specific visual assets with pixel proof.

Visual Asset Studio renders against an exact placement and verifies the final pixels before handoff. It does not invent a brand system or campaign concept when the brief is incomplete.

Open Visual Asset Studio →

13 more workspace agents run evidence gathering, client packaging, the control plane, and ops adapters. See the full platform →


Supporting products · evidence and delivery

The agent loop needs clean inputs and verifiable outputs.

Gather evidence

Parsing Stack

Fetch bounded source material, SERP evidence, and structured facts with source-quality and uncertainty checks. It gathers evidence; it does not decide what the evidence means or publish from it.

Open Parsing Stack →

Package client delivery

Content Package Studio

Turn an accepted article and quality receipt into a branded PDF package, schema deliverable, manifest, and verified client delivery. It packages accepted work; it is not a writer, CMS publisher, or generic design tool.

Open Content Package Studio →

Workspace control plane

The machinery behind bounded autonomy.

Workspace control plane

Route work, compile rules, bound tools, run proof, preserve artifacts and decisions, and write operational handoffs. Internal machinery, not a separately priced product line; Agent Governance currently runs in shadow.

  1. Route the request. Classify the job, project authority, and choose the smallest safe module set.
  2. Compile the rules. Resolve project instructions and keep shadow governance visible rather than implying enforcement.
  3. Prove the result. Run task-relevant tests, inspect built output, and preserve auditable artifacts.
  4. Carry context forward. Store decisions, files, and the exact continuation state for the next operator session.

Platform questions

Eighteen agents. Five marketing responsibilities buyers meet.

What is the Humanswith.ai platform?

It is an operated workspace with 18 AI agents and one Marketing Operator. Five agents own buyer-facing marketing responsibilities; support agents gather evidence and package accepted work; control-plane and ops agents route, constrain, prove, remember, and adapt each run.

Which products are client-facing Marketing Agents?

Hermes with AI Visibility Intelligence, ContentOS, Content Publisher, Website Agentic Optimization, and Visual Asset Studio. Each has a named responsibility and a human approval boundary.

What are the supporting products?

Parsing Stack gathers bounded source evidence. Content Package Studio turns accepted work into a verified client delivery. They support the operating loop without pretending to be autonomous marketing roles.

Does the platform replace a marketing team?

No. It automates repeatable work while people retain strategy, claim approval, prioritization, publishing authority, and final judgment. 10× article throughput: 100–120/mo with one operator + 18 AI agents vs 10–12/mo from a 6-person freelance team.

Are all 18 workspace agents separately sold products?

No. Buyers meet five Marketing Agents as product deep-dives. The other thirteen — support, control plane, Medium Publisher, MailOps, and project-bound Regula SEO when installed — are part of the same workspace install, not separate subscriptions.

How does work move through the platform?

The operator approves the goal and sources, the workspace prepares and checks the work, a human approves the output, the publisher ships the canonical asset, and the proof loop verifies the live result.


Start with the responsibility. Then choose the operating scope.

The current entry point is an operated pilot.

We define the first responsibility, evidence boundary, approval path, and handoff to your employee before recurring work begins.