What does this touch?
Returns the architecture characteristics detected in a plain-language description, the versioned Control Packs that apply, and the material decisions still open.
For agents and tools
Let your coding agent ask before it builds.
Point an MCP-capable coding agent at this service and it can check what a change touches, find the decisions only you can make, and compile a directive — inside the session where the work is happening. No account, no key, and nothing to install.
Model Context Protocol
One URL, no install
The endpoint speaks JSON-RPC 2.0 over HTTP, so any MCP client can use it without running code locally.
https://agentdirective.org/mcpMost clients take a remote MCP server as a URL in their configuration. A GET on that address describes the endpoint and lists its tools.
Turn answers into a contract
Compiles the canonical directive bundle from the user's answers and returns the files to write into the project.
Check reported status
Runs the bounded, metadata-only review over a directive and its reported implementation status.
Read the library
Returns the versioned Control Packs with their applicability logic, questions, requirements, and evidence references.
The one thing an agent is not allowed to do
An agent using this service may extract characteristics, match packs, and compile a directive. It may not decide. Thresholds, approval boundaries, retention periods, and destinations are for the person to answer.
analyze returns open decisions as questions with no value attached, and compile rejects any decision marked confirmed that carries no real value or whose source is not the user. A value the agent chose itself cannot become a confirmed boundary.
This is a guard rail rather than proof: an agent could still misreport where a value came from. Every confirmed value records its provenance in the compiled directive, and the generated instructions require the agent to restate the boundaries to you before implementing — so an invented value is put in front of the person best placed to catch it.
HTTP API
Or call it directly
Read-only methodology routes plus stateless compile and review. Cross-origin requests are allowed, so a browser tool can call these too.
| Route | Method | Returns |
|---|---|---|
/api/methodology | GET | Methodology, pack-library, and schema versions. |
/api/packs | GET | Every Control Pack with applicability logic, questions, requirements, and external control mappings. |
/api/failure-patterns | GET | Real-world-grounded failure patterns, each labelled by evidence kind and cited to a public source. |
/api/vocabulary | GET | Recognized platform names and the review areas they may indicate. |
/api/benchmark | GET | The detection-and-pack-agreement dataset and its latest results snapshot. |
/api/transparency | GET | The published metrics snapshot, with definitions and privacy thresholds. |
/api/changelog | GET | Dated record of product changes. |
/api/compile | POST | Compiles a directive bundle from a description, characteristics, and decisions. |
/api/review | POST | Bounded metadata review of a directive and reported status. |
/api/health | GET | Service and runtime status. |
What is stored when you call these
Nothing you send is retained.
compile and review are stateless: the description, decisions, and uploaded metadata are used to produce the response and then discarded. The service records only aggregate counters — how many compiles and reviews happened — never their contents. See /transparency for what is published and /review for the sanitized-metadata boundary.Before you rely on it
Current limits, stated plainly
- Every Control Pack is still in reviewNone has completed the technical and evidence review the project's own governance requires before release. Treat the library as pre-release methodology content.
- Detection is deterministic, not cleverCharacteristics come from a versioned phrase dictionary and a small context-rule layer, not a model. It is a starting point a person corrects, and an empty result is a legitimate outcome rather than a safety conclusion.
- A compiled directive is design guidanceIt is not a security guarantee, a certification, or verification that anything was implemented.
- Versions may changeSchemas and packs are versioned and every response carries its version, but this is a v0.1 interface and shapes can still change. Pin to the versions you read.