Audifact

io.audifact由 audifact.io 發布官方發布者v0.1.1更新於 Nov 2, 2026

Signed, append-only receipts of an AI agent's decisions and outcomes, with public proof links.

已驗證Streamable HTTP可網頁執行安全與監控AI 與機器學習

概覽

AI 產生的概覽

Audifact 為 AI 助理提供託管的僅追加帳本,用來記錄帶簽章的決策與結果回執,並取得公開證明連結。

可以做什麼
  • 將帶簽章的決策事件寫入帳本,預設由 Audifact 代管簽章金鑰
  • 依事件雜湊記錄與先前決策關聯的結果事件
  • 取得單一事件的公開證明內容,包含信任標籤、鏈結有效性與錨定狀態
  • 在 API 金鑰所屬組織下註冊或查詢代理身分
  • 依時間新到舊分頁列出某個代理的決策事件與結果事件
適用情境
當你需要為代理的重要決策、對外操作或子代理委派留下可驗證、防竄改的紀錄,並希望事後提供證明連結時使用。它的定位是選擇性回執(每個活躍日約 3 至 10 筆事件),而非完整追蹤。
執行需求
遠端 MCP 端點 api.audifact.io,使用 streamable HTTP,不需安裝本機套件。需要 Audifact 帳號以及在主控台建立的 API 金鑰(af_...),透過 X-API-Key 標頭或用戶端的密鑰欄位提供。
安裝前請注意
每筆記錄的事件都會消耗該 API 金鑰所屬帳戶的額度,記錄會產生費用。帳本僅能追加:項目經簽章並以雜湊串接,無法編輯或刪除。API 金鑰不要放進聊天或檔案,應使用用戶端的遮蔽密鑰欄位。公開標籤預設關閉;隨附技能會在寫入前遮蔽密鑰與訊息內容,但摘要仍會離開你的電腦。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Audifact,將其新增到工作區。
  2. 連接 X-API-Key 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.audifact%2Faudifact/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "audifact": {
      "type": "http",
      "url": "https://api.audifact.io/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

Audifact agent plugin

Your agent keeps a signed receipt of its decisions.

This repo packages Audifact’s hosted MCP server (https://api.audifact.io/mcp) plus a skill that tells the agent to log consequential decisions, external actions, and subagent delegations — then hand you proof links (https://audifact.io/e/{event_hash}).

It is receipts, not silent full tracing. Target about 3–10 events per active day.

Install

1. Audifact API key (all clients)

  1. Create an account at https://audifact.io/signup (the plugin never creates accounts).
  2. Dashboard → API Keys → create a key (af_..., shown once).
  3. Paste it only into the client’s secret / masked field. Never into chat or files.

2. Pick your client

Official MCP Registry / VS Code / Copilot / other registry clients

Listed as io.audifact/audifact in the MCP Registry (search “audifact”). Add the remote server from the registry or your client’s MCP gallery. Provide X-API-Key when prompted. Metadata: server.json.

Claude Code (self-hosted marketplace — no review queue)

text
/plugin marketplace add audifact/audifact-plugin/plugin install audifact@audifact

Paste the key into Audifact API key (userConfig, stored in the OS keychain).

Grok Bot / Cursor (x.ai catalog)

Install from the catalog when listed. Paste the key into AUDIFACT_API_KEY.
(Repo renamed from grokbot-plugin → audifact-plugin; resubmit replaces the 2026-10-16 draft.)

Agent Skills only (npx skills add)

bash
npx skills add audifact/audifact-plugin

This installs the skill instructions. You still need the MCP server connected in the same client, or the skill has no tools to call.

3. Confirm

Ask the agent to confirm the Audifact connection. It should log one plugin_connected decision and return a proof URL.

⚠️ Append-only ledger

Everything logged is signed and hash-chained and cannot be edited or deleted. The skill redacts before writing: no secrets, tokens, passwords, full message bodies or file contents — only short summaries.

Billing

Every event consumes credits on the Audifact account that owns the API key.

Privacy

  • Public labels are off by default.
  • Each agent logs under its own agent_name (e.g. grokbot-cos, claude-code).

Tools

log_decision, log_outcome, get_proof, register_agent, list_agent_decisions (deprecated alias: list_my_recent_decisions), list_agent_outcomes.

Repo layout

PathRole
.mcp.jsonGrok/Cursor: X-API-Key: ${AUDIFACT_API_KEY}
.grok-plugin/x.ai / Grok Bot plugin manifest
.claude-plugin/Claude Code marketplace + userConfig key (overrides MCP auth for Claude)
skills/audifact/Agent Skills SKILL.md
server.jsonOfficial MCP Registry remote metadata
assets/logo.svgBrand AF monogram

License

MIT

來源:README.md,提交 12ad2d3

工具

6

log_decision

Log a signed decision event to the ledger. Managed Mode (default for MCP): omit signing fields and pass agent_name - Audifact securely manages an Ed25519 keypair and signs on behalf of the agent. Events are immutable once recorded; managed mode provides strong auditability after receipt. For maximum provenance, use client-side signing via the SDK (agent_private_key_b64, or agent_public_key + signature). Linked outcomes must use the same signing method as the decision (managed or client-signed with the same agent key). Organization is always taken from the API key (do not send organization_id). Scenario hash is computed server-side from scenario_name + scenario_definition (+ optional context_schema) via resolve_scenario - you usually do not pass scenario_hash.

輸入參數tssignatureagent_namecontext_jsondecision_typemetadata_jsonscenario_hashscenario_namecontext_schemadecision_labeldecision_valueagent_public_key另有 8 個

log_outcome

Log a signed outcome event linked to a prior decision via decision_event_hash. Managed Mode (default): omit signing fields - the managed key from the linked decision's agent is used automatically when the decision was also managed. For client-signed decisions, pass agent_private_key_b64 or agent_public_key + signature using the same agent key. Signing method must match the linked decision (managed or client-signed). Outcomes do not accept scenario fields - scenario context is inherited from the linked decision.

輸入參數tssignatureagent_nameoutcome_type必填metadata_jsonoutcome_labeloutcome_value必填agent_public_keypublic_output_jsondecision_event_hash必填public_outcome_typepublic_outcome_label另有 2 個

get_proof

Get proof

Fetch the public proof payload for one ledger event by its 64-char hex event_hash. When to use: after log_decision/log_outcome when you need trust labels, chain validity, anchor status, or a paired-event proof URL. When NOT to use: to browse many decisions or outcomes — use list_agent_decisions / list_agent_outcomes first, then call get_proof on a chosen event_hash; do not use this to write events (use log_decision / log_outcome). Requires X-API-Key. Returns proof fields only for events in that key's org; unknown or other-org hashes return EVENT_NOT_FOUND (same message either way). Read-only; does not mutate the ledger. Response includes event_hash, event_type, event_seq, public_* mirrors, hash_valid, agent_chain_valid, trust_level, trust_label, proof_anchor_status_label, and chain metadata.

輸入參數event_hash必填

register_agent

Register agent

Register or look up an agent identity under the API key's organization. When to use: before client-side signing flows that need a known public_key, or to attach a human-readable name to an existing key. When NOT to use: Managed Mode log_decision (pass agent_name instead — Audifact provisions the key); do not use this to log decisions or outcomes. Idempotent on public_key: repeating the same key returns the existing agent. Requires X-API-Key. Returns the agent record (id, public_key, name).

輸入參數namepublic_key必填

list_agent_decisions

List agent decisions

List decision events for one agent (by public key) in the API key's org, newest first by default. When to use: to review what an agent already logged, pick an event_hash for get_proof, or page through history before linking an outcome. When NOT to use: to list outcomes (use list_agent_outcomes); to fetch one event's trust/anchor proof (use get_proof); to write a new decision or outcome (use log_decision / log_outcome); this is org-scoped via X-API-Key (not a public explorer listing) and does not accept agent_name — pass the agent's public_key from a prior log_decision response or register_agent. Requires X-API-Key. Read-only. Unknown public keys return an empty decisions list (total 0), not an error. Returns {decisions, total, next_cursor, has_next}. Pass next_cursor as cursor for the next older page.

輸入參數limitcursoragent_public_key必填

list_agent_outcomes

List agent outcomes

List outcome events for one agent (by public key) in the API key's org, newest first by default. When to use: to audit what results an agent recorded, find an outcome event_hash for get_proof, or page outcomes without already knowing hashes. When NOT to use: to list decisions (use list_agent_decisions); to fetch one event's trust/anchor proof (use get_proof); to write a new decision or outcome (use log_decision / log_outcome); this is org-scoped via X-API-Key (not a public explorer listing) and does not accept agent_name — pass the agent's public_key from a prior log_decision / log_outcome response or register_agent. Requires X-API-Key. Read-only. Unknown public keys return an empty outcomes list (total 0), not an error. Returns {outcomes, total, next_cursor, has_next}. Each outcome includes decision_event_hash when linked. Pass next_cursor as cursor for the next older page.

輸入參數limitcursoragent_public_key必填

版本歷史

2
  1. v0.1.1最新Oct 19, 2026
  2. v0.1.0Oct 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。