A template is a reusable rating question set. Each template is composed of one or more dimensions like Usability, Visual Design, Accessibility, Trust, Clarity. Every Rating attaches a value to each dimension on the active template.Documentation Index
Fetch the complete documentation index at: https://docs.autousers.ai/llms.txt
Use this file to discover all available pages before exploring further.
Templates is the canonical noun. The legacy alias
/v1/dimensions/*
continues to work but carries Deprecation: true and Sunset: Sun, 04 Apr 2027 00:00:00 GMT. New code should use /v1/templates/* exclusively.Built-in vs custom
| Kind | Owner | Visible to | Editable by |
|---|---|---|---|
| Built-in | system | All teams | Read-only |
| Custom | team | Members of the owning team | Editor+ |
Listing
Creating a custom template
DimensionVersion rows) — editing a template
in active use does not retroactively change the dimensions of past
ratings.
The selectedDimensionIds field
When creating an evaluation, you pass selectedDimensionIds: string[]
on the create body. Each id is either:
- A built-in dimension key (
overall,trust,clarity,accessibility, …). - A custom dimension id from your team’s templates.
- A new id you supply on
customDimensions[]— autosaved into your team’s templates atomically with the evaluation create.
/v1/templates for future reuse without an extra round-trip.
Why “templates” and not “dimensions”
The original schema called these “dimensions” — single-axis scales like Usability or Accessibility. But the user’s mental model is the set, not the axis: “the accessibility template”, not “the accessibility dimension”. The route alias rename in 2026-04 reflects that. Internally the rows still live in thedimensions table; externally the noun is
template.