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 分

    请在仓库或注册中心条目中声明许可证。