Marketing Agent

On-brand marketing for every listing without writing it from scratch.

A ready-to-build governance package for Real Estate. Your runtime enforces it; Agent Bob does not run the agent.

Build this package Have it set up for you

Purpose

You want every listing marketed consistently across email and social posts. This agent drafts marketing copy from approved listing data and your brand assets. The listing agent approves all copy before it is published or sent.

It will

Read approved listing data and brand assets — no direct posting to MLS, paid ad spend, or contact list access without explicit authorization

It won't

Make unverified claims about property condition or investment returns, contact buyers or sellers directly, publish content that has not received listing agent sign-off, use buyer or seller PII in marketing without consent

It asks a person first

Flag any generated copy referencing price changes or sold status for immediate agent review before release
Listing agent must approve all marketing copy, social posts, and email content before publication or send

Tools

File reading
Document writing

File reading: Read documents you provide.
Document writing: Create or edit Word / Google Docs / Notion pages.

✋ You approve once at the start of each run

Budget defaults

Per task: $0.25
Per month: $30
Actions a day: 30

The runtime pauses the agent at a limit. You can change every number in the builder.

Memory and autonomy

Session only. Nothing is kept once the session ends.

Acts within limits: low-risk steps on its own, everything gated still stops for a person.

What you get

The 8-file governed package your runtime loads and enforces. On the paid tier the trust manifest is signed, so your runtime can verify nothing was changed after you approved it.

HANDOFF.md What your runtime has to enforce, file by file
agent-blueprint.json The agent's purpose, tools and settings
policy.json Hard limits: autonomy, budget, memory, tools, loop bounds
trust-manifest.json The integrity manifest your runtime can verify
routing.rules.json Which tools need approval before use
run-report-template.json What every run reports back
approval-gates.md The moments that must pause for a person
deployment-checklist.md What to check before it goes live

This is a governance specification, not a running agent. The rules in these files do not enforce themselves: your runtime has to implement them.

Start from this package

Bob pre-fills the builder with it and drafts the rest. You confirm every step.

Build this package Have it set up for you