Getting Started

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

• understand the public product family from the docs landing
• begin with Auk if you need a programmatic integration surface
• treat the website, docs, and console as clients or shells around the same canonical backend
• use the trust and contact routes when you need legal, privacy, research, or accessibility coordination

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
• static keyword search
• no dashboard CMS
• no auth
• no newsletter
• no embedded AI runtime

Illustrative Integration Flow

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