Developer reference
Developers
Cryptographically attested governance and intelligence tools for the agent economy.
What is Stratalize
These are developer docs for the Stratalize platform and data tools: integration guides and API reference for MCP and attestation verification.
All public tools follow the same ML-DSA-65 post-quantum cryptographic attestation standard and JCS RFC 8785 canonicalization.
Get started
OAuth via MCP
Connect your organization, complete OAuth, then call tools using an API key or Bearer token as required by your MCP client.
MCP integration guide/docs/mcp
Verify attestation
Validate ML-DSA-65 signatures offline using the published public key from /api/trust/signing-key.
Attestation verification guide/docs/attestation
Standards & Compliance
Stratalize implements the following open standards and specifications. Each is publicly auditable.
- OAuth 2.0 with PKCE
- RFC 7636. MCP authentication flow.
- OAuth Resource Metadata
- RFC 9728. Tool discovery via
/.well-known/oauth-protected-resourceand/.well-known/oauth-authorization-server. - JSON Canonicalization Scheme
- RFC 8785. Used for deterministic serialization before ML-DSA-65 signing.
- ML-DSA-65
- NIST FIPS 204. Active signature algorithm for response attestation.
- MCP
- Model Context Protocol. Tool integration with AI agents.
Authentication
- Public tools: no auth required for discovery-style reference tools.
- Organization tools: OAuth via MCP; see /docs/mcp.
Resources
- MCP Registry, discover Stratalize servers under the
com.stratalize/*namespaces. - /api/trust/signing-key, public verification key (JSON).
- Status page, live at status.stratalize.com.