Parametrig Product Documentation

Parametrig builds insurance infrastructure for the programmable economy.

This docs surface is intentionally static-first and contract-first:

• content lives in markdown
• search is generated at build time
• discovery artifacts are generated at build time
• public docs are curated intentionally instead of mirrored automatically from private internal material

What You Can Do Here

• start from the live Auk surface
• understand how the website, docs, console, and canonical backend relate
• review public trust and contact routes
• track only the product and platform material that is ready to be treated as public contract

Quickstart

The public docs start with the Auk surface and the canonical backend contract. This example shows the expected request posture without pretending that every internal surface is already public here.

curl https://api.parametrig.com/v1/quotes \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"product":"auk","context":{"partner":"demo"}}'

import requests

response = requests.post(
    "https://api.parametrig.com/v1/quotes",
    headers={"Authorization": "Bearer <token>"},
    json={"product": "auk", "context": {"partner": "demo"}},
)

const response = await fetch("https://api.parametrig.com/v1/quotes", {
  method: "POST",
  headers: {
    Authorization: "Bearer <token>",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ product: "auk", context: { partner: "demo" } }),
});

Current Public Shape

• parametrig.com explains the company and product posture
• docs.parametrig.com holds the curated public contract surface
• api.parametrig.com is the canonical backend entrypoint
• console.parametrig.com is a client over the same backend, not a separate source of truth

Product Family Posture

The public product family starts with Auk.

Additional family names exist internally, but they only appear in public docs when they are ready to be treated as real external contracts with durable behavior, trust posture, and support expectations.

Publishing Model

• public product and API overviews
• integration guidance
• platform/runtime boundary explanations that are safe to publish
• trust and contact routes for public docs readers
• discovery-friendly raw markdown and sitemap artifacts

What Does Not Belong Here

• internal roadmap sequencing
• private legal drafting
• internal review findings
• unpublished strategy or architecture deliberation