Cowrie Research

moltrust-primary-sources-2026-05-03

3 min read

MolTrust primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone MolTrust or MoltGuard whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official site, the MoltGuard product page, the API docs entrypoint, and the public @moltrust/x402 repository README.
  • MolTrust is best understood as trust infrastructure for autonomous agents and agent-mediated payments rather than as a narrow analytics or compliance widget.

Primary-source snapshots

1) Official homepage / top-level positioning

  • URL: https://moltrust.ch/
  • Key excerpt:
    • The homepage calls MolTrust the “Trust Layer for the Agent Economy.”
    • It frames the product around pre-transaction identity verification, reputation scoring, and W3C Verifiable Credentials for AI agents.
    • It also highlights trust score, Sybil detection, market integrity checks, and credential issuance, with x402-on-Base and Lightning payment language.
  • Why it matters:
    • This is strong first-party evidence that the company sees itself as infrastructure for machine trust and not merely as a monitoring dashboard.

2) MoltGuard product page / concrete trust primitives

  • URL: https://moltrust.ch/moltguard.html
  • Key excerpt:
    • The page describes MoltGuard as a trust and integrity API combining agent scoring, Sybil detection, market integrity monitoring, and verifiable credentials.
    • It documents free and paid endpoints, pricing intentions, early-access status, and an explicit architecture using Blockscout, Base RPC, Polymarket Gamma, MCP tools, and x402 paywalls.
  • Why it matters:
    • This is where the abstract trust framing turns into a concrete operating surface with specific inputs, outputs, and payment semantics.

3) Scoring model / operational details

  • URL: https://moltrust.ch/moltguard.html
  • Key excerpt:
    • The Trust Score model assigns points for wallet age, transaction count, unique counterparties, USDC balance, ERC-8004 registration, ERC-8004 reputation, and credential bonus, with deductions for Sybil indicators.
    • The page also exposes example JSON responses with breakdowns and raw signal categories.
  • Why it matters:
    • This makes the product legible as programmable trust infrastructure rather than vague “AI safety” branding.

4) MCP and standards surface

  • URL: https://moltrust.ch/ and https://moltrust.ch/moltguard.html
  • Key excerpt:
    • The homepage advertises DID:web, W3C VC, Ed25519, Lightning, ERC-8004, and MCP as core building blocks.
    • The MoltGuard page says seven MCP tools are available at https://api.moltrust.ch/mcp.
  • Why it matters:
    • The standards mix suggests MolTrust is deliberately trying to become interoperable trust middleware for agents, not just a closed consumer app.

5) API docs entrypoint

  • URL: https://api.moltrust.ch/docs
  • Key excerpt:
    • The docs entrypoint links back to the main site and MoltGuard and confirms the existence of a maintained API surface.
  • Why it matters:
    • Even though the extracted landing content was minimal, it corroborates that MolTrust is operating a developer-facing API product and not only a marketing page.

6) @moltrust/x402 repository / payment-gating middleware

  • URL: https://github.com/MoltyCel/moltrust-x402 and https://raw.githubusercontent.com/MoltyCel/moltrust-x402/main/README.md
  • Key excerpt:
    • The README describes middleware for x402 payments that extracts the wallet address from the X-PAYMENT header, queries MoltGuard’s score endpoint, blocks requests below a configurable minimum score, and fails open if MoltGuard is unavailable.
    • It ships Hono and Express integrations and points to https://api.moltrust.ch/guard as the API base URL.
  • Why it matters:
    • This is the clearest proof that MolTrust’s trust layer is meant to plug directly into paid API flows and autonomous-agent commerce.

Working conclusion

MolTrust is best cataloged as agent trust infrastructure: a control plane for identity, credentials, trust scoring, integrity checks, and policy gating around autonomous payments and market actions. The decisive evidence in this pass was the combination of explicit standards-based identity, wallet and market scoring, public API and MCP surfaces, Base- and Lightning-oriented payment language, and practical x402 middleware that embeds trust checks into machine-payment flows.

Graph View