Build with LocalEndpoint

Developers

Developer routes expose schemas, validators, examples, OpenAPI-style metadata, and UAI-1 records for local-first integrations.

Extension developer resources Open route index

Developer starting points

Inspect the contract. Keep execution on the device.

Start with identity, OpenAPI, the explicit route index, or the endpoint plugin guide. Every route here is read-only: discovering metadata never grants runtime authority.

01 / IdentityLocalEndpoint identity

Current package identity, public boundary, and metadata posture.

/.well-known/localendpoint.json 02 / OpenAPIOpenAPI profile

Read-only route profile for public inspection and integration planning.

/.well-known/openapi.json 03 / RoutesPublic route index

Explicit human and machine route table with no generic runtime fallback.

/api/public-route-index.json 04 / ExtensionsExtension developer resources

Open the starter kit, authoring guide, catalog, and submission process without granting authority.

/developers/plugins/#build-extension

Advanced machine routes and trust protocol

Agent briefLLM-readable guide

Short public guidance for AI systems reading the site.

/llms.txt EnvelopeUAI-1 example

Machine-readable context wrapper with runtime authority kept false.

/api/uai-1/envelope/example.json QualityQuality gates

Current readiness signals, route clarity, and non-certification boundaries.

/api/quality-gates/status.json

Protocol relay

Public discovery becomes a local-ready contract.

The developer path turns the website into a deterministic handshake: agents read context, developers validate shape, evidence travels, and runtime authority still stops at Desktop.

01 / Announce Identity declares the boundary

Well-known files describe public purpose, package posture, and runtime authority false.

02 / Shape Schemas make requests comparable

UAIX and route contracts define what can be inspected before any local handoff.

03 / Prove Validation emits evidence

Browser receipts, hashes, and quality gates make review portable without private endpoint data.

04 / Handoff Desktop owns authority

The public site prepares context; human-visible local approval remains on the device.

Protocol rule Read context Validate shape Carry evidence Deny runtime

Developer contract Read routes Validate schema shape Export evidence Runtime authority remains false

LocalEndpoint owns

Package, policy, prompt, registry, and audit boundaries.

LocalEndpoint validates .uaix packages, expands .uai file memory, assembles prompts locally, owns policy decisions, persists registry and audit evidence, and writes JSONL events without prompt text or generated text.

UAIX.LmRuntime owns

Bounded managed local GGUF execution.

The runtime adapter receives an already-approved display-safe context, verifies the reviewed GGUF expectation, emits ordered token observations, preserves session identity, and does not parse .uaix packages or persist private text.

Worker handoff owns

Traceability before model allocation.

LocalChatViabilityEvidence is created before a worker envelope exists. Missing, malformed, non-isolated, authority-bearing UAIX context, invalid offload state, stale model selection, local API drift, or public boundary drift records a blocked no-op before model session allocation, tokenization, or inference; session identity, turn identity, and provider request fingerprints travel through start, stream, token, and terminal evidence.

Read-only agent firewall

Machine-readable does not mean machine-authorized.

The developer surface gives agents enough structure to understand LocalEndpoint, compare public contracts, and produce review evidence without crossing into localhost probing, credential requests, command dispatch, or autonomous execution.

01 / Discover Read public guidance

Agents start with the public brief and identity records.

02 / Inspect Follow explicit routes

The route index is the map; no generic runtime fallback is implied.

03 / Validate Check shape locally

Validation proves manifest shape and redaction posture, not runtime authority.

04 / Handoff Stop before authority

Anything actionable belongs to a human-visible Desktop review.

Agent firewall Read-only discovery Schema inspection Evidence allowed Runtime denied

Agent boot sequence

Read the public surface like an AI, but keep authority human.

The correct agent path is deterministic: discover identity, inspect the explicit route table, validate schema shape, check quality gates, produce evidence, and stop before runtime execution.

01Read /llms.txt and /.well-known/ai-agent.json
02Confirm routes in /api/public-route-index.json
03Inspect UAI fields through /api/uai-1/conformance-pack.json
04Check gates at /api/quality-gates/status.json
05Validate locally; share redacted evidence only
06Hand off to Desktop for human approval

Agent contract Metadata is readable. Runtime authority is false.

Allowed: route discovery, schema inspection, example validation, quality evidence review.

Denied: localhost probing, credential requests, public command dispatch, autonomous execution, certification claims.

Build

Declare endpoint scope

Use schemas and examples to describe what a local endpoint is allowed to expose.

Review

Generate evidence

Validate payloads, redact sensitive fields, and share reviewable artifacts instead of private data.

Handoff

Keep authority local

Route public discovery toward future desktop approval flows rather than browser-triggered execution.

Operating boundary

Public clarity, local authority.

Public product, docs, download, and validation pages do not dispatch desktop commands, probe localhost, upload files, collect runtime telemetry, or claim runtime safety certification. Account credentials are accepted only on dedicated account routes.