Technical subset
Docs
Enough public detail to prove the engine is real without exposing the full internal corpus.
This docs subset is intentionally narrow. It exists to prove the public integration surface, not to dump the full operating corpus.
You should expect:
- quote and transaction request shapes,
- bearer-token auth expectations,
- reporting endpoint examples,
- a concise architecture summary.
API Overview
Public route map for partner-facing quotes, transactions, and reporting.
Quote Endpoint
Request a protection quote and receive locked terms plus evidence metadata.
Transaction Endpoint
Accept a quote, create a protected transaction, and preserve the partner-scoped evidence trail.
Auth and Reporting
Bearer-token expectations for partner reporting APIs and controls.
Architecture Summary
Public diligence view of Slice boundaries and partner-segregated pooling.