Getting Started

Understand how Parametrig's public surfaces fit together before you integrate.

Parametrig currently has three primary public surfaces:

parametrig.com for company and product positioning
docs.parametrig.com for curated public documentation
api.parametrig.com for the canonical backend and API entrypoint

How To Start

The intended first path is now sandbox-first:

1. create a sandbox key 2. connect or inspect a sandbox webhook path 3. run the simulation flow and save the first artifact 4. verify the event -> claim -> payout story in non-final terms 5. cross to live only after that path is clean

Use the detailed walkthrough here:

Sandbox Walkthrough

Documentation Scope

This docs site focuses on material that should be public and durable:

product and API overviews
integration guidance
platform/runtime boundaries that help partners understand the system
future discovery artifacts such as sitemap, llms.txt, and raw markdown

Scope Boundaries

This site is not the place for:

private planning or execution tracking
unpublished legal drafts
investor-only material
internal-only operations reasoning

Current Launch Shape

The first docs launch stays deliberately simple:

markdown content in git
static site build
Pagefind-backed search in the right rail
no dashboard CMS
no auth
no newsletter
TrigIQ available in the right rail over the public docs corpus only

Sandbox-First Walkthrough

The launch posture is intentionally not “go live first and hope it lines up.”

For new operator workspaces, the first-value sequence should be:

sandbox key
  -> sandbox webhook capture
  -> simulation artifact
  -> event / claim / payout proof
  -> explicit live boundary

The docs and console should tell the same story:

authentication starts with sandbox keys, not live keys
webhook delivery should be provable in the first-party sandbox inbox
simulations are a first-class guided surface, not only a pricing calculator
the move to live is an explicit operational decision, not the silent default

Once a workspace has already crossed to live, the operator should not be forced back through sandbox as if onboarding were still incomplete. Sandbox remains the rehearsal lane, not a permanent reset.

partner app
  -> docs.parametrig.com for public contract understanding
  -> api.parametrig.com for canonical integration
  -> console.parametrig.com only if an operator-facing browser client is needed

First Public Questions To Answer

Before you integrate, the main things to confirm are:

which published surface you are integrating against
what auth posture applies to that surface
what part of the lifecycle is public contract versus private internal engine
which support or trust route should be used if something needs escalation