MC-1 DOCS
API ReferenceCookbook
Docs/MC-1 Trust/Trust SDK design
PublishedGuidanceLAST REVIEWED · 30 AUG 2026

Trust SDK design

Integrate verification and local readiness without conflating them with certification.

Overview

The Python and TypeScript Trust clients are local prototypes pending the Trust API contract and publication. They should reject missing authorization, inactive state, malformed responses, and transport errors.

  • Keep bearer credentials server-side.
  • Use HTTPS for remote verification.
  • Match agent, action, resource, and audience in verification requests.
  • Treat local readiness as self-assessment only.

Production checklist

  • Keep credentials in a server-side secret store.
  • Set explicit cost, latency, privacy, provider, and regional constraints.
  • Capture route and evaluation evidence for incident review.
  • Test timeouts, cancellation, fallback, and denied-policy paths before rollout.
End of guide
Was this page helpful?
Trust SDK design | MC-1 Docs