Agent Mesh · Pillar 1

UTCP tool reference

Jarvis exposes kernel capabilities as UTCP tools (GET /utcp discovery, POST /tools/invoke). Only tools that are implementable today are advertised — empty billboards are a trust bug.

provider jarvis v0.1.0 7 tools auth: Bearer

Auth

Every call requires a Bearer token (JARVIS_BEARER_TOKEN). Missing/wrong → HTTP 403.
Optional capability grants: JARVIS_UTCP_CAPABILITIES=policy:check,run:create (empty = full owner grant).
Missing capability on invoke → HTTP 403 with reason "capability denied".
Audit actor is a token fingerprint (tok_<prefix>_<sha256[0..4]>), never the raw secret.
Loopback bind only in v0 (127.0.0.1).

Discover manifest

curl -sS \
  -H "Authorization: Bearer $JARVIS_BEARER_TOKEN" \
  http://127.0.0.1:7777/utcp

policy

jarvis.policy.check policy:check

Evaluate command policy for an argv vector

run

jarvis.run.create run:create

Execute a command after policy evaluation
jarvis.run.tail run:tail

Fetch a run row by id (status, exit code, bounded stdout/stderr)

handoff

jarvis.handoff.post agent:handoff

Post a SPEC-017 handoff from one agent to another
jarvis.handoff.inbox agent:handoff

List pending handoffs addressed to an agent

skill

jarvis.skill.list skill:list

List SPEC-011 skills from project and agent-home catalogs
jarvis.skill.invoke skill:invoke

Invoke a skill on this host (script run or materialize SKILL.md)

Also: MCP fallback via POST /mcp and mnemos utcp register-mcp (P12-004). Native mesh path stays UTCP.