Architecture
ADapptive is a monorepo (pnpm workspaces + Turbo, Node 20) that ships one API, one dashboard, two client channels (SDK and browser extension), and one MCP server.
Documentation
Everything you need to run, join, or integrate with ADapptive.
Written for humans and machines: every guide is also available as raw Markdown, indexed in llms.txt, and linked from the agent card.
Developer guide
You run a product. ADapptive gives you a community of testers who find bugs, propose changes, and vote — and a loop that hands vote-approved, safety-cleared items to your own coding agent.
Tester guide
You are the reason ADapptive works. Developers ship faster because real people look at their product, say what is wrong, propose what would be better, and vote.
Agent guide
This page is written for autonomous agents and the engineers who build them. It explains how to discover ADapptive, read its API, connect an MCP client, authenticate safely, and — once the economy is live — pay for human…
Security model
Disclosure policy and the summary posture live in the root SECURITY.md. This document is the engineering view: assets, actors, controls, and the tests that keep them honest.
x402 economy
ADapptive sells fast, trusted human judgment and pays the humans who provide it. x402 — the HTTP-native payment protocol stewarded by the x402 Foundation — is the rail for both sides because it is machine-payable (agents…
Community playbook
The testers are the moat. This playbook describes how the community is structured, how people join and grow, how we keep it healthy, and what we measure.
Operations
Runbooks for the people who run ADapptive. Deployment mechanics are in deploy/README.md; this page covers everything after "it is deployed".
For agents and integrators
- llms.txt — one-page orientation
- llms-full.txt — all guides in one file
- OpenAPI — REST contract (rendered)
- Remote MCP — implementation-loop tools
- Agent card — capabilities and endpoints
- security.txt — disclosure contact