Mnemom — Trust Ratings for AI Agents

REMOTE · API.MNEMOM.AI · SCANNED AUG 3

Trust infrastructure for AI agents: read a verifiable Trust Rating, claim an identity, earn a badge.

Available components

+3 this week 69 69 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security66

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (put_alignment_by_agent). See how to fix → View diagnostics → Fail
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability76

100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
AI-judged instruction clarity (good).Pass
Context-footprint check failed: tool/resource definitions use about 3198 tokens (~118/item across 27 items; 16 tools + 11 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.mnemom.ai

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http mnemom-mnemom https://api.mnemom.ai/mcp?profile=directory

# ~/.codex/config.toml

[mcp_servers.mnemom-mnemom]
url = "https://api.mnemom.ai/mcp?profile=directory"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mnemom-mnemom": {
      "type": "remote",
      "url": "https://api.mnemom.ai/mcp?profile=directory",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add mnemom-mnemom --url https://api.mnemom.ai/mcp?profile=directory --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  mnemom-mnemom:
    url: "https://api.mnemom.ai/mcp?profile=directory"

// mcp.json

{
  "mcpServers": {
    "mnemom-mnemom": {
      "type": "http",
      "url": "https://api.mnemom.ai/mcp?profile=directory"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 66

First indexed and scored.

Show 7 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://api.mnemom.ai/mcp?profile=directory

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mnemom.ai	CN=WE1,O=Google Trust Services,C=US	1 Aug 2026	30 Oct 2026	ECDSA 256	ECDSA-SHA256	ffc1a21401a416780e6fd20ebf0a9d9f
SANs: mnemom.ai, api.mnemom.ai
CN=WE1,O=Google Trust Services,C=US (CA)	CN=GTS Root R4,O=Google Trust Services LLC,C=US	13 Dec 2023	20 Feb 2029	ECDSA 256	ECDSA-SHA384	7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA)	CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE	15 Nov 2023	28 Jan 2028	ECDSA 384	SHA256-RSA	7fe530bf331343bedd821610493d8a1b

DNSSEC secure

Validation of api.mnemom.ai. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
ai.	present	3799	8	Verified
mnemom.ai.	present	2371	13	Verified
api.mnemom.ai.				Verified address RRset verified with the apex keys

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=31536000
content-security-policy	default-src 'none'; frame-ancestors 'none'
x-content-type-options	nosniff
x-frame-options	DENY
referrer-policy	strict-origin-when-cross-origin

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://api.mnemom.ai/mcp?profile=directory	Verified	200
http (plaintext)	http://api.mnemom.ai/mcp?profile=directory	HTTPS enforced	301	https://api.mnemom.ai/mcp?profile=directory

MCP tools — 16 exposed · ~2,222 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

claim_agent ~159

Claim a verifiable identity — bind an agent to your organization so its trust and accountability record is provably yours. No human in the loop.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)
hash_proof	string	yes	Agent possession proof: the full 64-hex SHA-256 digest of `${apiKey}\|${agentName}` (or `${apiKey}` for an unnamed singleton agent).
org_id	string	—	Optional. The organization to claim the agent into (e.g. `org-...` or `pers-...`). The caller must be a member of this org (role floor: member). If omitted, the agent is claimed into the caller's per…

Name	Type	Req	Description
agent_id	string	yes	—
claimed	boolean	yes	—
claimed_at	string	yes	—
org_id	string	yes	The organization the agent was claimed into (echoes the resolved org — the supplied `org_id`, or the caller's personal org when omitted).

No examples provided.

get_agent ~51

Look up an agent's public identity and trust state by ID — the accountable record other agents and humans can rely on.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)

Name	Type	Req	Description
agent_hash	string	—	First 16 hex chars of `SHA256(apiKey + '\|' + agentName)` for named agents, or `SHA256(apiKey)` for unnamed singleton agents. The gateway computes the same value on each request and uses it as the loo…
agent_proof_captured_at	string\|null	—	—
agent_proof_hash	string\|null	—	Owner projection: captured hash_proof of the bound key (mig 263).
aip_enforcement_mode	string\|null	—	—
avatar_url	string\|null	—	—
billing_account_id	string\|null	—	—
caller	string	—	Self-describing caller context for THIS response. `org_member` callers receive the full owner record (all fields here); `anonymous`/`authenticated` (non-member) callers receive the reduced public pro…
claimed	boolean	—	Public projection only: whether the agent has been claimed by a user.
claimed_at	string\|null	—	—
claimed_by	string\|null	—	Owner projection: user id that claimed the agent.
containment_status	string\|null	—	Containment state of the agent (ADR-053).
created_at	string	—	—
created_by	string\|null	—	Owner projection: user id that created the agent (provenance).
deleted_at	string\|null	—	Owner projection: soft-delete timestamp (null when live).
email	string\|null	—	—
groups	array	—	Active groups this agent belongs to, name-ordered; `[]` when none. Present on org-fleet rows (GET /v1/orgs/{org_id}/agents). Archived groups are excluded.
id	string	—	—
key_prefix	string\|null	—	First 8 chars of the bound API key hash — useful for key-rotation debugging.
last_seen	string\|null	—	—
name	string\|null	—	Agent name (2-32 chars, alphanumeric + hyphens). Present on all list and get responses.
org_id	string\|null	—	Owner projection: the agent's org binding (ADR-062 authz boundary).
public	boolean	—	Identity-record visibility axis — whether the agent's IDENTITY RECORD is publicly discoverable. This is DISTINCT from reputation visibility: every registered agent's reputation is public by accountab…
status	string	—	—
user_id	string\|null	—	—

No examples provided.

get_reputation ~104

Look up an AI agent's published Trust Rating — Mnemom's portable reliability signal for autonomous software, computed from the agent's own verified activity record. Returns the rating plus the technical factors behind it. Free, public, read-only: every registered agent's rating is published by standard (the `visibility` field is the reputation-publication axis, distinct from identity-record visibility).

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)

Name	Type	Req	Description
a2a_trust_extension	object	—	A2A trust extension for interop. Only present on `GET /reputation/{agent_id}` (not on batch/compare rows).
agent_id	string	yes	—
agent_name	string\|null	—	—
checkpoint_accounting	object\|null	—	Structured breakdown of how checkpoints were counted toward the score. `analyzed` is the scoring population; `excluded` buckets are mutually exclusive and `analyzed + synthetic + insufficient_thinkin…
checkpoint_count	integer	yes	—
claimed	boolean	—	—
components	array	yes	—
computed_at	string\|null	—	—
confidence	string	yes	—
grade	string\|null	yes	AAA–D or NR.
is_eligible	boolean	yes	—
next_compute_at	string\|null	—	Next scheduled recompute — the 00/06/12/18 UTC cron slot strictly after `computed_at` (`floor(computed_at/6h)*6h + 6h`). Null when `computed_at` is null.
score	integer\|null	yes	—
tier	string\|null	—	—
trend_30d	number\|null	—	—
visibility	string	yes	Reputation-publication axis — whether this agent's Trust Rating is published. Every registered agent's reputation is `public` by accountability standard (the default; that is the whole point of a por…

No examples provided.

get_reputation_badge ~63

Get an embeddable Trust Rating badge for an agent — returns the badge image URL plus ready-to-paste Markdown and HTML snippets for a README or agent card.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)

Name	Type	Req	Description
agent_id	string	yes	The agent the badge is for (echoed from the request).
badge_url	string	yes	Canonical SVG Trust Rating badge image URL (always on api.mnemom.ai).
html_embed	string	yes	Paste-ready HTML badge snippet.
markdown_embed	string	yes	Paste-ready Markdown badge snippet.
profile_url	string	yes	Human-readable reputation profile page (on www.mnemom.ai).
verified_url	string	yes	Public cryptographic verification URL for the rating.

No examples provided.

get_started ~103

Zero-auth, no-args orientation: who Mnemom is, the surface map, how to authenticate and what it unlocks, and the value tools to try right now (headlining scan_trust + the reputation reads).

Input Output Examples

Name	Type	Req	Description
token	string	—	Optional Dojo try-me invite token. When supplied and valid, returns the token-gated dojo briefing manifest (the same content as GET /v1/dojo/try-me/resolve); omit for public orientation.

Name	Type	Req	Description
authenticate	object	yes	How to authenticate and what auth unlocks.
developer_path	object	yes	The developer hero on-ramp: the npx one-liner plus the intent-named MCP prompt-skills (try-me, onboard_an_agent, become_sovereign). Advertisement only — no functional dependency on those prompts exis…
doctrine	string	yes	—
showcase_agent	object	yes	A real Mnemom-owned agent the try_now reputation reads target, so the loop runs verbatim.
skill_path	object	yes	The two-step on-ramp to declaring and advertising capabilities as A2A skills in a signed, portable AgentCard.
sovereignty_path	object	yes	The five-step on-ramp to becoming a sovereign, accountable agent, composed from existing tools. Walked end to end by the become_sovereign MCP prompt.
surface_map	object	yes	Stable links to the canonical read-only surfaces.
try_now	array	yes	Zero-auth value tools to call right now.
value_prop	string	yes	What Mnemom does for an agent.
verify	string	yes	How to verify signed artifacts in-band (verify, don't trust).
visibility_model	object	yes	Disambiguates the two axes that share the word 'public': reputation-publication visibility (public by standard) vs identity-record visibility (agent.public), plus the caller-context self-description.
what_we_keep_private_and_why	string	yes	—
who	string	yes	One-line positioning.

No examples provided.

list_agents ~55

List your agents — List all agents owned by the authenticated user. Supports pagination.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Maximum number of agents to return (max 100)
offset	integer	—	Number of agents to skip for pagination

Name	Type	Req	Description
agents	array	yes	—
scope	string	yes	Echoes the resolved listing scope.

No examples provided.

preview_compose_alignment_by_agent ~190

Preview composed alignment (dry run) — Composes the cascade against a hypothetical body at the agent layer and returns conflicts + the composed view. No DB writes. Used by the dashboard editor for live conflict markers.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)
body	object	—	Unified alignment card (ADR-008/ADR-039). Authored in YAML or JSON; composed server-side with platform defaults, org template, and active exemptions before storage. This schema matches the runtime va…

Name	Type	Req	Description
coherence_violations	object	yes	—
conflicts	object	yes	—
effective	object	yes	—
full_report	object	yes	—
ok	boolean	yes	—
summary	boolean	yes	—
tool	string	yes	—
what_changed	string	yes	—
what_to_do_next	string	yes	—
what_would_break	string	yes	—

No examples provided.

preview_compose_protection_by_agent ~152

Preview composed protection (dry run) — Composes the cascade against a hypothetical body at the agent layer and returns conflicts + the composed view. No DB writes. Used by the dashboard editor for live conflict markers.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)
body	object	—	Unified protection card (ADR-037). Safe House thresholds + trusted-source policy for a single agent. Shape matches src/composition/types.ts::UnifiedProtectionCard (canonical) and what the runtime val…

Name	Type	Req	Description
conflicts	object	yes	—
effective	object	yes	—
full_report	object	yes	—
ok	boolean	yes	—
summary	boolean	yes	—
tool	string	yes	—
what_changed	string	yes	—
what_to_do_next	string	yes	—
what_would_break	string	yes	—

No examples provided.

put_alignment_by_agent ~209

Publish or replace the alignment manifest — Accepts YAML (`text/yaml`, `application/yaml`) or JSON. Body is the full `UnifiedAlignmentCard`; server-side composition merges it across the platform → org → team → agent cascade and writes the canonical composed card. Requires `Idempotency-Key`. Honor...

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)
body	object	—	Unified alignment card (ADR-008/ADR-039). Authored in YAML or JSON; composed server-side with platform defaults, org template, and active exemptions before storage. This schema matches the runtime va…

Name	Type	Req	Description
_composition	—	—	—
agent_id	string	yes	Target agent id. On PUT, server overwrites to match the URL path.
audit	object	yes	—
autonomy	object	yes	—
autonomy_mode	string	yes	ADR-039 master switch for the action-policing pipeline (autonomy constraints). Required at the top level post-cutover; the legacy `enforcement.mode` location is rejected.
capabilities	object	—	—
card_id	string	—	Card row id. Server-assigned on PUT (`ac-{uuid}`).
card_version	string	yes	Card schema version (required, non-empty). Current canonical value: `unified/2026-04-26`.
conscience	object	—	—
content_hash	string	—	Response-only: content hash of the composed card (`sha256:<hex>`), injected by the GET/PUT response. Server-assigned — do not send on a PUT.
enforcement	object	—	Optional ADR-039 Decision-3 user-facing knobs for unmapped-tool handling. The legacy `mode`, `unmapped_tool_action` and `fail_open` keys are REJECTED by the validator (mode → top-level autonomy_mode;…
expires_at	string\|null	—	—
extensions	object	—	—
integrity_mode	string	yes	ADR-039 master switch for the values/conscience pipeline (integrity constraints). Required at the top level post-cutover; the legacy `integrity.enforcement_mode` location is rejected.
issued_at	string	—	—
principal	object	—	Required object describing whose authority the agent acts under (ADR-039 Decision 10).
values	object	yes	—
version	integer	—	Response-only: monotonic card version, injected by the GET/PUT response. Server-assigned — do not send on a PUT.

No examples provided.

put_protection_by_agent ~171

Publish or replace the protection manifest — Accepts YAML (`text/yaml`, `application/yaml`) or JSON. Body is the full `UnifiedProtectionCard`; server-side composition merges it across the platform → org → team → agent cascade and writes the canonical composed card. Requires `Idempotency-Key`. Hon...

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)
body	object	—	Unified protection card (ADR-037). Safe House thresholds + trusted-source policy for a single agent. Shape matches src/composition/types.ts::UnifiedProtectionCard (canonical) and what the runtime val…

Name	Type	Req	Description
_composition	—	—	—
agent_id	string	yes	—
card_id	string	—	—
card_version	string	yes	—
content_hash	string	—	Response-only: content hash of the composed card (`sha256:<hex>`), injected by the GET/PUT response. Server-assigned — do not send on a PUT.
expires_at	string\|null	—	—
extensions	object	—	Free-form extension slot for non-canonical fields. Ignored by the composer; preserved on read for tooling that needs an audit-tail metadata bag.
issued_at	string	—	—
mode	string	yes	Strictest-wins composition: enforce > nudge > observe > off.
protected_surface	object	—	Org-declared protected surface policy (MNE-830). Strengthen-only UNION across platform → org → team → agent: each scope may add entries; none may remove. The composer always emits this block; callers…
review	object	—	Review-hold policy (Safe House Review, Slice 2a — MNE-920 design). gate_on is the minimum verdict band per surface that escalates to a review-hold. Composition is strictest-wins; on_timeout defaults…
screen_surfaces	object	yes	Which request surfaces Safe House inspects. Composed across scopes by OR-per-field (any scope requiring inspection wins).
thresholds	object	yes	Score bands. Must satisfy warn <= quarantine <= block; each value in [0, 1].
trusted_sources	object	yes	Sources for which detectors short-circuit (each match logged in the trace). Composed as platform->agent intersection (compliance ceiling) with org+agent union inside that ceiling — an agent cannot wi…
version	integer	—	Response-only: monotonic card version, injected by the GET/PUT response. Server-assigned — do not send on a PUT.

No examples provided.

report_recipe_fn_fp ~185

Submit a false-positive / false-negative correction for one of Mnemom's automated detection rules (a 'recipe') — technical feedback that improves detection accuracy, like filing a bug report against a spam filter.

Input Output Examples

Name	Type	Req	Description
agent_id	string	—	Optional. Customer's agent id, when the report concerns a specific agent.
checkpoint_id	string	—	Optional. Related integrity_checkpoints id (helps the reviewer correlate).
evidence	string	—	Optional raw payload / log excerpt the admin reviewer can inspect.
recipeId	string	yes	The detection_recipes id the report is filed against (the recipe that misfired or failed to fire).
summary	string	yes	Customer's description of what happened.
type	string	yes	'fn' (false negative — recipe should have fired) or 'fp' (false positive — recipe fired on legitimate behaviour).

Name	Type	Req	Description
candidate_id	string	yes	—
ok	boolean	yes	—
related_recipe_id	string	yes	—
type	string	yes	—

No examples provided.

scan_trust ~202

Scan a website's agent-trust-readiness and return a signed scorecard (Trust, plus an Access axis on newer rubrics). Zero-auth. Results are CACHED for up to 24h — check `cached` and `scannedAt` on the result; pass `fresh: true` to force a re-scan (rate-limited). Proxies to the SSRF-locked isittrustready scanner; the Ed25519 signature + permalink are preserved verbatim. Rubric + docs: https://www.isittrustready.ai/rubric and https://docs.mnemom.ai/.

Input Output Examples

Name	Type	Req	Description
fresh	boolean	—	Force a fresh re-scan instead of the cached result (results are cached up to 24h; the engine rate-limits re-scans). Equivalent to the scanner's rescan flag.
url	string	yes	Domain or URL to scan, e.g. "example.com" or "https://example.com".

Name	Type	Req	Description
access	object	—	The independent Access/discoverability axis (never blended with Trust). Present from the two-axis rubric (0.3.0+).
cached	boolean	—	True when served from the scanner's 24h cache rather than a fresh scan.
categories	array	—	Trust-axis categories with per-category scores + checks.
grade	string	yes	Trust letter grade (A+…F).
permalink	string	—	Shareable /r/ permalink (only on /r/ responses; transport field).
rubricVersion	string	—	Rubric version (e.g. "0.4.0").
scannedAt	string	—	When this scorecard was produced. Results are cached up to 24h — pass fresh:true to scan_trust to force a re-scan.
schema	string	yes	iitr-scan schema version string (e.g. "iitr-scan/v0.N").
score	number	yes	0–100 weighted overall TRUST score.
signature	object	yes	Ed25519 signature over the canonical result (transport field; stripped before verify).
target	string	yes	Normalized host that was scanned.
verification	object	—	Self-describing in-band verification block {alg, kid, jwks, canonicalization} — how to verify this scorecard's signature. Self-describing, so signed-EXCLUDED (stripped before verify).

No examples provided.

search_reputation_directory ~199

Resolve an agent name or id-prefix to a real agent_id over the PUBLIC reputation directory (only agents whose reputation visibility is public). Zero-auth. The arriving-agent entry point: discover a concrete agent_id, then call get_reputation / verify_reputation on it.

Input Output Examples

Name	Type	Req	Description
confidence	string	—	Filter to agents at a given reputation-confidence level (driven by how much evidence backs the score).
grade	string	—	Filter to one grade (e.g. `AAA`, `B`, `NR`).
page	integer	—	1-based page number for pagination. Default 1.
per_page	integer	—	Number of results per page. 1–100, default 20.
q	string	—	Name search (ilike) or agent-id prefix match.
sort	string	—	Result ordering. Default "score" (highest-rated first); other supported keys order by recency or name.

Name	Type	Req	Description
agents	array	yes	—
page	integer	yes	—
per_page	integer	yes	—
total	integer	yes	—

No examples provided.

verify_agent_binding ~93

Verify that an API key is bound to this agent — confirms the holder is the accountable owner (anti-impersonation), hashing the key client-side.

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)
key_hash	string	yes	First 16 hex chars of SHA256(apiKey) or SHA256(apiKey + '\|' + agentName) for named agents.

Name	Type	Req	Description
bound	boolean	yes	True if the submitted hash matches the registered key.
caller	string	yes	Self-describing caller context. `key_prefix` is present iff `caller` is `org_member`; `anonymous` and `authenticated` (non-member) callers receive `{ bound, caller }` only. This is BY DESIGN, not a p…
key_prefix	string\|null	—	First 16 chars of the registered key (or null if not yet captured). Returned ONLY to callers who are members of the agent's org (`caller` === `org_member`); omitted for anonymous / cross-org callers.

No examples provided.

verify_reputation ~104

Attest an agent's Trust Rating — returns a Merkle-root + hash-chain attestation (hash_chain_valid) proving the rating derives from an unbroken, append-only checkpoint chain, plus a pointer to the signed integrity certificate. This is a chain-integrity attestation, NOT an in-band Ed25519 signature check (that parity is verify_scan, for website scorecards).

Input Output Examples

Name	Type	Req	Description
agent_id	string	yes	Agent identifier (e.g. smolt-abc123)

Name	Type	Req	Description
agent_id	string	yes	—
computed_at	string	yes	—
grade	string	yes	—
score	number	yes	—
verification	object\|null	yes	—

No examples provided.

verify_scan ~182

Verify a website scan scorecard's Ed25519 signature IN-BAND (verify, don't trust). Pass a `scan` (a scorecard from scan_trust) or a `url` to re-scan; returns {verified, key_id, canonicalization} checked against the public key at mnemom://iitr/jwks. Zero-auth. Spec + rubric: https://www.isittrustready.ai/rubric and https://docs.mnemom.ai/.

Input Output Examples

Name	Type	Req	Description
scan	object	—	A scan scorecard previously returned by scan_trust (or iitr's /r/ JSON), passed back verbatim to verify. Same shape as scan_trust's result; the signature is checked against mnemom://iitr/jwks.
url	string	—	Alternatively, a domain/URL to re-scan and then verify.

Name	Type	Req	Description
algorithm	string	yes	Always "Ed25519".
canonicalization	string	yes	The exact canonicalization used (so the verdict is reproducible).
key_id	string\|null	yes	The signing key id (kid) checked.
reason	string	—	Why verification failed or could not be evaluated (absent when verified).
scorecard	object	—	The scorecard verified (present when re-scanned via `url`).
verified	boolean	yes	True iff the signature verifies against the in-band JWKS.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	66
27 Jul	66
28 Jul	67
29 Jul	68
30 Jul	66
31 Jul	67
1 Aug	68
2 Aug	68
3 Aug	69