Planning AI. Sprint estimation, task breakdown, risk analysis. Learns your velocity.
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.
| 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).
curl -X POST https://api.dingdawg.com/v1/developers/signup \
-H "Content-Type: application/json" \
-d '{"email":"you@example.com","name":"Your Name","role":"consumer"}'
# -> {"api_key": "dd_...", ...} store it — shown once
export DINGDAWG_API_KEY=dd_your_key
npx dingdawg-compliance quick-check
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)
See CONTRIBUTING.md for contribution guidelines.
See SECURITY.md for our responsible disclosure policy.
MIT License. See LICENSE for details.
Innovative Systems Global. The name is not aspirational. It is a statement of fact.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y dingdawg-planning-agentMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-dingdawg-dingdawg-planning-agent": {
"command": "npx",
"args": [
"-y",
"dingdawg-planning-agent"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencedingdawg-planning-agentnpmio.github.dingdawg/dingdawg-planning-agent works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.