01
Entry integration
The adapter sits inside the existing WordPress runtime so the site can expose Badger without rewriting the content stack.
- Fits existing plugin-driven deployments
- Preserves editorial workflow
- Adds the agent surface at the edge
Adapter Surface
WordPress Adapter
Thin integration for sites using WordPress as the current market-entry surface.
Current market-entry adapter for websites that need Badger without replacing the existing CMS.
Adapter map
Integration without duplicating the platform.
02
Published surfaces
The adapter should publish manifest, action, and policy surfaces in ways that stay legible to external systems and manageable to site operators.
- Agent-facing manifest and policy routes
- Explicit action endpoints
- Static or cache-friendly machine outputs
03
Platform boundary
Planning, policy, generation, and network intelligence remain in the Badger platform so the adapter stays thin and replaceable.
- No duplicated business logic
- Centralized orchestration
- Shared contract across adapters
Linked surfaces
Where this adapter meets the public contract.
Linked surface
/capabilities/agent-interface
Relevant route for understanding how this adapter exposes capabilities into the wider Badger public surface.
Linked surface
/agents/manifest.json
Relevant route for understanding how this adapter exposes capabilities into the wider Badger public surface.
Linked surface
/audit
Relevant route for understanding how this adapter exposes capabilities into the wider Badger public surface.
Next route