Site intelligence for WordPress agencies using Codex
Darwin turns approved client context into positioning, page structure, copy direction, technical requirements, and cited guidance. Your builder gets a clear assignment. You keep control of every change.
$99/month · 10 client workspaces · Customer-site read-only
Example intelligence handoff
Position
The detail-first renovation partner for occupied homes.
Primary audience
Page architecture
Target: WordPressEvidence
3 cited sources
Assumptions
2 marked
Confidence
High
Where AI builds go sideways
The hard part is deciding who the page is for, what it needs to say, which claims are approved, and what ready means before the first prompt.
The useful details are split across kickoff calls, notes, brand files, old pages, and whoever remembers the last revision.
When positioning, page goals, and constraints are vague, a fast first draft still creates rounds of re-prompting and copy rewrites.
Without one cited quality bar, SEO, accessibility, conversion, design, and factual checks vary from project to project.
Darwin turns those loose decisions into one approved build target before your agency starts producing pages.
Inside Darwin Brain
The customer-facing brain is a separate, allowlisted product corpus. It does not expose Darwin's raw internal registry, tenant data, or admin tools. The pilot draws only from the guidance that makes a website clearer, safer, and easier to build.
Evidence-backed recommendations include a source and review date. Assumptions and inference-only safeguards are labeled, with confidence.
Logical structure, descriptive metadata, and crawlable navigation that search systems can understand.
Sources: Google Search Central
Keyboard access, visible focus, useful labels, instructions, and form errors that people can act on.
Sources: World Wide Web Consortium · W3C Web Accessibility Initiative
One clear primary action, verb-led labels, and shorter forms that ask only for what the task needs.
Sources: U.S. Web Design System · W3C Web Accessibility Initiative
Responsive layouts, predictable navigation, consistent components, readable contrast, and logical order.
Sources: U.S. Web Design System · World Wide Web Consortium
Server-side input validation and context-aware output encoding for submitted or third-party content.
Sources: OWASP Foundation
Approved evidence for objective claims, plus checks for misleading implications before publication.
Sources: Federal Trade Commission
How the pieces connect
Darwin sits between the context your agency approves and the builder that implements the work. It adds a clear assignment without taking control of the website.
Customer-facing guidance path
Approved context in. A cited website brief out.
Darwin Brain
Isolated workspace · Read-only context
Implementation-ready brief
Cited guidance + publish checklist
Codex
Private pilot
WordPress
Planned
Base44
Compatible
GoDaddy Airo
Artifact only
The division of labor
Darwin does not replace Codex, WordPress, hosting, or your agency process. It gives the builder a clearer assignment and gives your team the evidence behind the guidance.
A human approves the business facts and brand direction for one isolated client workspace.
Darwin creates the positioning, page plan, copy and design direction, technical requirements, and a checklist with cited recommendations and labeled safeguards.
Codex builds from the brief. Your team controls every edit and every publishing decision.
During the pilot, publish-readiness feedback is manual and checklist-based. Automated site review is not yet available.
Initial Codex MCP tools
Model Context Protocol, or MCP, lets Codex call Darwin inside the build workflow. The pilot exposes one tool to build the brief and one to find supporting guidance.
darwin_build_briefCreates an implementation-ready website brief from approved business context, goals, and the builder target.
darwin_find_guidanceAnswers a focused site question with bounded guidance, sources, freshness, assumptions, and confidence.
Darwin cannot search another client, expose raw memory or vectors, change a site, deploy code, publish content, or write back to client context.
Platform support
The production pilot runs as a hosted MCP for Codex. Every other platform is labeled by what has actually been verified. Compatible does not mean Darwin can publish to that platform.
Hosted Darwin MCP with manual onboarding and revocable bearer credentials. External OAuth onboarding is not yet available.
Codex will connect to Darwin and WordPress.com as separate MCP servers. There is no native Darwin integration yet.
Draft-only connector work starts after paid pilot validation. There is no current site editing or publishing.
Base44 documents custom remote MCP support. Darwin onboarding has not been verified end to end.
Darwin does not connect to, edit, or publish Airo sites.
Planned through WordPress Abilities after the connector beta is validated.
Pilot questions
The first release is intentionally narrow: better direction for Codex, approved context for each workspace, and no production control.
It is the direction around the build: approved audience and positioning, page architecture, copy and design guidance, technical requirements, cited evidence, marked assumptions, and a publish checklist. Darwin gives that assignment to the builder you already use.
The production pilot connects Darwin to Codex through a hosted Model Context Protocol endpoint. Codex can use Darwin's brief and guidance tools while your WordPress, hosting, and deployment workflow stays in place. A WordPress.com dual-MCP demo and self-hosted connector remain planned.
No. The initial pilot is read-only and does not host sites, edit WordPress, deploy code, publish pages, change prices, or write back to client context. Your agency controls every production action.
Not yet. The pilot produces a provenance-marked publish checklist with cited recommendations and labeled safeguards, plus manually assisted feedback. The darwin_review_site tool remains gated behind paid-use validation.
One monthly pilot covers up to 10 active client workspaces, manual Codex MCP onboarding, cited implementation-ready website briefs, approved read-only brand context, and direct pilot support.
Account and workspace scope come from the authenticated credential, not from a workspace ID supplied in a prompt. Approved brand context is isolated and read-only, credentials are revocable, and raw memory or vector data is not exposed as a customer tool.
First 10 agency accounts
No automatic publishing. No production-site takeover. No long-term contract.
Apply for a pilot spot
We will help your agency connect Codex, approve the client context, and produce a brief you can use in your current WordPress workflow. Best fit: WordPress-heavy agencies already using Codex or another MCP-capable builder.