LocalEndpoint guide

Choose a working example

Start with safe examples that show how endpoint manifests, evidence packets, route metadata, and UAI-style envelopes fit together.

Open safe sample See UAI envelope

Safe artifact gallery

Examples that teach the connection shape without touching a machine.

These samples are public, metadata-only rehearsal objects. They show what a local endpoint can declare, what an agent can inspect, what evidence can prove, and where runtime authority stops.

Manifest Endpoint manifest sample

Allowed operations, denied operations, input limits, output shape, and evidence policy in one reviewable file.

Ability Agent ability sample

Machine-readable capability description without granting command execution.

Diagnostic Diagnostic metadata sample

A status shape that explains what local evidence could look like without inspecting this visitor's device.

Evidence Redacted evidence packet

Review data that proves shape and boundary without raw logs, secrets, or private endpoint payloads.

Envelope UAI-1 envelope example

Agent-facing metadata wrapper with runtime authority explicitly outside the public site.

Routes Public route index

The inspectable public surface humans and agents can read before any local approval path.

Rehearsal deck

Practice the whole connection without touching a private endpoint.

Examples are the safe proving ground: copy a public shape, validate it locally, compare redacted evidence, then adapt only the labels and limits your own workflow needs.

Copy Start from public-safe shape

Use known examples before introducing local endpoint names, limits, or private context.

Validate Run the browser workbench

Check schema shape and boundary language while the payload stays inside the tab.

Compare Read the evidence pair

Line up manifest, receipt, hashes, and redacted packet before treating the shape as useful.

Adapt Change intent, not authority

Replace labels and limits while preserving denied operations, redaction policy, and local approval.

Rehearsal rule Public sample first Validate in browser Compare evidence Adapt after review

Sample constellation

A rehearsal set for humans, validators, and agents.

The examples are designed to move together: start with a manifest, validate the shape, compare evidence, then let agents read the public route context without receiving runtime authority.

ManifestDeclare scope

Allowed operations, denied operations, limits, and evidence policy.

ValidatorProve shape

Run the sample locally in the browser and produce a receipt.

EvidenceShare safely

Redacted proof that stays useful without exposing private payloads.

RoutesRead context

Machine-readable public surface with authority still false.

Rehearsal contract Start with public-safe JSON Validate before adapting Export evidence, not secrets Keep runtime local

Example contract Public-safe JSON Metadata only No localhost check Validator-ready

Learn

Start from known-good JSON

The samples are intentionally public-safe, metadata-only, and suitable for local validator testing.

Adapt

Replace labels, not boundaries

Use your own local endpoint details while preserving denied operations, redaction policy, and explicit limits.

Verify

Run samples through the workbench

Load an example in the browser validator and export a receipt before sharing it.

Validate sample

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.