API

API Overview

The public API surface is designed around a stable canonical backend and programmatic integration.

Parametrig's public API surface is served from the canonical backend at api.parametrig.com.

Public API Principles

  • one canonical backend source of truth
  • programmatic access first
  • browser surfaces are clients, not the authority
  • stable external contracts should not depend on UI-specific behavior

Current Public Family

The current published API family starts with Auk.

This docs surface should expand only when public contract material is ready to be durable, discoverable, and supportable. Internal product families or engine boundaries should not appear here just because they already exist behind the current backend.

Surface Families

Additional named surfaces may be published later as they become real external contracts, but they should not appear here before their product and trust boundaries are actually ready.

As public API references expand, this docs site should become the home for:

  • endpoint overviews
  • authentication guidance
  • webhook/event guidance
  • examples and integration notes

Illustrative Request Posture

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" } }),
});

Lifecycle Expectation

As the public reference expands, this docs surface should become the home for:

  • request and response examples
  • auth guidance
  • event and webhook semantics
  • error behavior
  • versioning expectations
  • support and escalation boundaries

Publication Rule

Public API material belongs here only when it is ready to be treated as a public-facing contract.