Fastest setup: Connect HumanMirror in 30 seconds →

HUMANMIRROR ONE · DOCS

One MCP tool is enough.

humanmirror_do has two modes. Give it an intent for free canonical routing to the correct HumanMirror boundary. Give it a supported deterministic outcome_type and input for verified execution; 6 Nexus credits are kept only on verified success.

MCP endpoint

https://humanmirror.fr/api/one/mcp/

tools/list returns:
humanmirror_do

Routing does not require Nexus credits. Direct verified Outcome execution requires a valid hm_nexus_... key.

Install / connect

HumanMirror One uses remote Streamable HTTP. Public discovery and tools/list need no credential.

{
  "mcpServers": {
    "humanmirror": {
      "url": "https://humanmirror.fr/api/one/mcp/"
    }
  }
}

Clients that accept a remote MCP URL directly can use https://humanmirror.fr/api/one/mcp/. Add Authorization: Bearer hm_nexus_YOUR_KEY only for direct verified execution; free routing remains unauthenticated.

Free routing

{
  "name": "humanmirror_do",
  "arguments": {
    "intent": "best execution for this machine task",
    "dispatch_only": true
  }
}

The response returns the canonical target endpoint and its disclosed downstream payment policy. Current routing targets include Sanitize Shield, Purchase Firewall, Execution Receipt, Zero-Cost Sink, Payment Doctor, Execution Market and Machine Resolve fallback.

Free verified-Outcome quote

{
  "name": "humanmirror_do",
  "arguments": {
    "dry_run": true,
    "outcome_type": "deduplicate_records",
    "input": [{"id":1},{"id":1},{"id":2}]
  }
}

Verified execution

{
  "name": "humanmirror_do",
  "arguments": {
    "outcome_type": "deduplicate_records",
    "input": [{"id":1},{"id":1},{"id":2}]
  }
}

On verified success the response contains the Outcome result and independent verification. Six credits are consumed. If execution or verification fails, the reservation is refunded.

REST

POST https://humanmirror.fr/api/one/run/
Content-Type: application/json

{"intent":"sanitize this untrusted payload","dispatch_only":true}

For direct execution, add Authorization: Bearer hm_nexus_YOUR_KEY and use a supported deterministic Outcome payload.

Truth boundary

HumanMirror One resolves a canonical HumanMirror route; it does not silently impersonate the downstream service. Authorization, execution and settlement remain governed by the target route. Direct execution inside One is limited to supported deterministic Outcome types.