MolTrust Trust Registry
Run this agent? Claim this listing to edit it.
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.
A2A readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B, 86.5/100), which weighs availability, conformance, card completeness and speed. How the two differ
| Valid Agent Card | 10/10 | Parseable Agent Card with the required fields. |
| Live JSON-RPC | 25/25 | Endpoint answers A2A JSON-RPC (769 ms). |
| Protocol version | 10/10 | Declares A2A 1.0 with supportedInterfaces[] (v1 card shape). |
| JWS signature | 3/10 | Signature present but did not verify: InvalidSignatureError. |
| Uptime (30 days) | 15/15 | 11/11 probes succeeded over 30 days (100%). |
| Skill declaration | 10/10 | Declares 16 skill(s) with structured metadata. |
| Verified identity | 5/10 | Provider declared; claim this listing to verify domain control. |
| Security declaration | 2/5 | Declares 4 security scheme(s). |
What we measured
Over the last 30 days we probed this agent 11 times on 6 days; it answered 11 (100%). Median response 908 ms, 95th percentile 1,152 ms.
Among the 6,610 reachable A2A agents in our snapshot of 2026-11-17 14:45 UTC, it is faster than 9% and higher on readiness than 96%.
From agent-tools.cloud's own probes, last checked 2026-11-17. How we measure
Compared with peers
Against 6,610 reachable A2A agents in our daily snapshot (2026-11-17 14:45 UTC). Display only; it does not change search order.
- Readiness
- Higher than 96% of peers
- This listing 84 · peer median 53
- Latency
- Faster than 9% of peers
- This listing 946 ms · peer median 353 ms
Where it loses the most points, and how to win them back
- JWS signature −7
— Sign the Agent Card (JWS).
Now: Signature present but did not verify: InvalidSignatureError.
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Provider declared; claim this listing to verify domain control.
- Security declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares 4 security scheme(s).
Skills
-
Agent Trust ScoreReturns 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).trustidentityverificationdidw3cscore
-
DID ResolutionResolves 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).dididentityw3cresolutiondif
-
Verifiable Credential VerificationVerifies 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).vccredentialaaedelegationw3c
-
Wallet Binding VerificationChecks 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).walletpaymentbasesolanax402erc8004
-
Wallet Track Record CredentialIssues 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).credentialwalletbasetrack-recordx402gate
-
Sybil & Anomaly DetectionTwo-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.02 USDC; covered by the Base and Scale plans). 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).securitysybilanomalyfraud-detectionmoltguard
-
EU AI Act risk classificationClassify 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).complianceeu-ai-actriskclassificationannex-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).complianceannex-vdeclarationverifiable-credential
-
Compliance reportHTML/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).compliancereportaudit
-
Article 73 serious-incident recordingRecord 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).complianceincidentarticle-73deadline
-
UCAN delegation mintingMint 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).delegationucanauthorizationcapabilities
-
UCAN delegation verificationVerify 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).delegationucanverification
-
Batch reputationReputation 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).reputationbatchscore
-
Merkle batch anchoringMerkle-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).anchoringmerkleevidenceprovenance
-
Amazon Ads Verdict GateAllow, 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.advertisingamazon-adsmcpauthorizationmandatebudgetaaeguardrail
-
Leak canary for delegating agentsOne 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-canaryleak-canarydelegationcredentialsleak-detectionverification
How to call
https://api.moltrust.ch/a2a
Listed in
Directories this entry was found in.