Developers
Developers
Integration surface for ChatGPT and capture clients. Product claims stay soft: verifiable digital record, not legal proof.
Public origin
- API / MCP / OAuth:
https://api.crystalize.it - SaaS tool:
https://app.siriusdetector.com/tool/crystalize/ - Signing keys (public): crystalize.it/security/signing-keys
OAuth
- Authorization Server metadata:
/oauth/chatgpt/.well-known/oauth-authorization-server - Protected resource metadata:
/.well-known/oauth-protected-resource - PKCE S256 · authorization code · refresh · revoke
- Issuer:
https://api.crystalize.it/oauth/chatgpt
MCP
- Endpoint:
POST https://api.crystalize.it/mcp - Operational tools cover preview, confirm/start, status, Evidence Package and verify — plus UI surfaces when Apps UI is enabled
- Fail-closed when integration flags are off (see Status)
Capture API
Authenticated capture routes under /api/v1/captures*. Newer clients may also use /api/v2 when enabled on the host. Downloads return the Evidence Package (archive) and/or a human-readable PDF report via signed links where issued.
Evidence Package (integrator view)
- Delivered after Preview → Confirm → successful capture
- Includes content, PDF report, integrity/time marks, and offline verification helpers
- Clients should surface download + verify — not invent legal conclusions
- Public fingerprint for key check: Signing keys
Architecture
ChatGPT→MCP→OAuth→
Integration Service→Worker→Engine→Evidence Package
Flow (must respect)
Preview → user confirmation → create → status → result → verify. No capture without confirm.
Related
ChatGPT product page · Evidence Package · Security · Privacy