dingdawg-marketing-agent

Name: dingdawg-marketing-agent
Author: dingdawg

Local

github.com/dingdawgBusiness & Marketing1Updated 12w ago

Repository

About dingdawg-marketing-agent

dingdawg-marketing-agent is a marketing-focused package in the DingDawg governed-agent ecosystem. The supplied README describes shared services for governed execution, compliance classification, regulation lookup, trust scores, and signed audit receipts, but does not detail marketing-specific tools.

Key features

01Governed agent execution
02Compliance classification
03Regulation lookup
04Agent trust scores and live stream
05Cryptographically signed audit receipts

Use cases

01Route agent calls through governance checks
02Classify compliance requirements
03Look up regulations
04Review trust scores and audit records

MCP support

The README does not describe MCP exposure or an MCP-specific interface.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config

{
  "mcpServers": {
    "dingdawg-dingdawg-marketing-agent": {
      "command": "npx",
      "args": [
        "-y",
        "dingdawg-marketing-agent"
      ],
      "env": {
        "DINGDAWG_API_KEY": "<DINGDAWG_API_KEY>"
      }
    }
  }
}

Run commandnpx -y dingdawg-marketing-agent

Environment variables to set

DINGDAWG_API_KEYSecretAPI key for paid tier access — get free at dingdawg.com

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages

npmdingdawg-marketing-agent2.0.6stdio

Tools

Saved tool list · updated 2w ago

Parameter	Type	Required	Description
tone	string	No	Desired tone (professional, casual, persuasive, etc.)
topic	string	Yes	Topic or subject for the content
audience	string	No	Target audience
keywords	string	No	Target keywords (comma-separated)
content_type	enum	Yes	Type of content to generateblog_post \| social_media \| email \| ad_copy

Details

From the project README

DingDawg Agent 1

Governance receipts for AI agents.

Every action a governed agent takes generates a cryptographically-signed receipt: what it decided, why, which model, which version, at what time. Built toward EU AI Act Art. 12, Colorado AI Act (SB 24-205), and NIST AI RMF requirements.

The receipt is what turns a policy document into evidence.

What's live today

Capability	Endpoint
Developer signup — issues a scoped API key	`POST /v1/developers/signup`
Governed execution — routes agent calls through metering + audit	`POST /v1/govern/execute`
Compliance classification	`POST /api/v1/compliance/classify`
Regulation lookup	`GET /api/v1/compliance/regulations`
Agent trust score + live stream	`GET /api/v1/agents/{id}/trust`, `WS .../trust/stream`
Billing (Stripe)	`POST /api/v1/payments/create-checkout-session`

Backed by 10 governed-agent npm packages (compliance, legal, healthcare, finance, devops, marketing, sales, support, code-review, planning).

Quickstart

curl -X POST https://api.dingdawg.com/v1/developers/signup \
  -H "Content-Type: application/json" \
  -d '{"email":"[email protected]","name":"Your Name","role":"consumer"}'
# -> {"api_key": "dd_...", ...}  store it — shown once

export DINGDAWG_API_KEY=dd_your_key
npx dingdawg-compliance quick-check

Architecture

Client (npm package / your agent) --auth: DINGDAWG_API_KEY-->
  api.dingdawg.com (FastAPI, Railway)
    -> Tier isolation + rate limiting
    -> Governance gate (score, log, decide)
    -> Audit trail (signed receipt)
    -> Stripe metering / billing
  -> Response (governed, scored, receipted)

Documentation

Contributing

See CONTRIBUTING.md for contribution guidelines.

Security

See SECURITY.md for our responsible disclosure policy.

License

MIT License. See LICENSE for details.

Innovative Systems Global. The name is not aspirational. It is a statement of fact.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

Read the getting-started guide

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.