Script
Stable v1 public URL
Developers
Developer docs stay focused on the public v1 widget, safe page context, optional server-signed identity, dashboard-owned route controls, and verification. They do not expose private workspace data or dashboard APIs.
Stable v1 public URL
Safe page fields only
Origins and blocked routes owned by AnswerLattice
Start here
Most teams should start with the dashboard packet, then use quickstarts only where framework-specific placement matters.
Agent packet, manual install, framework docs, and widget contract.
Next.js, React, Vue/Nuxt, and vanilla script examples.
Copyable instructions for coding agents installing the widget.
Stable v1 script URL, browser API, safe context, and compatibility policy.
Focused docs
Developer Doc
Safe page context rules for AnswerLattice widget installs: allowed fields, forbidden identifiers, screenshots, and route updates.
Open docDeveloper Doc
AnswerLattice widget verification checklist for script loading, allowed origins, blocked routes, route context, and dashboard status.
Open docDeveloper Doc
Sign short-lived AnswerLattice visitor context on your server and attach bounded allowlisted diagnostic links without trusting browser identity or recording sessions.
Open docAccount-gated server integration
AnswerLattice source includes a server-only API for governed answers, public entity identifiers, and bounded review signals. It is disabled by default, requires a named approved workflow, workspace readiness, an owner-issued al_ key, and explicit scopes. It is not a self-serve public entitlement.
View machine-readable OpenAPI contractPublic API stability
The current server API uses the /v1 path. Existing v1 fields, required inputs, authentication semantics, and status-code meanings will not be removed, renamed, retyped, or made more restrictive inside v1. Compatible optional response fields may be added after they appear in OpenAPI, so consumers should ignore unknown response fields.
A breaking request, response, authentication, or behavior change requires a new major URL such as /v2 plus an explicit migration guide. It does not silently replace the v1 contract.
Before an operation is retired, its OpenAPI operation will be marked deprecated, this page will publish the replacement, migration steps, and exact sunset date, and responses will emit Deprecation, Sunset, and successor-version Link headers. No v1 operation is currently deprecated or scheduled for removal.