We build compact AI messaging tools.
JustAnIota official shield mark JustAnIota UAI tooling ɩ.com Compact AI messaging tools Language-neutral AI messaging: registries, schemas, validation.
Draft IOTA-1 tools
  • Current surface JustAnIota tooling draft
  • Plain-English definition Compact, structured AI messaging tools
  • Current attribution Michael Joseph Kappel, MCP
  • Short-domain status ɩ.com redirects to JustAnIota.com

Tools

Validator

Local validator workflow for JustAnIota envelopes, UAI target declaration, Unicode safety, registry references, and compact export warnings.

  • Record JAI-TOOL-0021
  • Path /es-us/tools/validator/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-TOOL-0021
Surface
Tools
Access
Public and linkable

How to use this page

Use this page to test candidate messages against the published UAI-1 record and save the results before release.

Validation inputs

ExamplesRegistry

Validation Path

Human review and machine validation stay separate here

Use the page workbench when a person needs fixture loading and export, and use the REST route when CI, automation, or client code needs a JSON POST target.

Human surface

Fixture loading and export

This page is for side-by-side review, validator output inspection, and downloadable validation records.

Machine surface

JSON POST route

Automation should resolve the validate route through discovery or the catalog and submit a JSON payload instead of depending on browser-only behavior.

Request posture

Public guardrails, not private quota

The public POST route rejects oversized JSON with 413 and returns 429 plus Retry-After when launch-stage throttles trip; it remains an unauthenticated public review surface, not a private bulk-validation service.

Release evidence

Keep the packet with the release

A passing validator result is part of a release packet, not a standalone certification claim or universal support badge.

Validation inputs

ExamplesPublished fixtures for baseline checks.RegistryResolve the intended public profile.

Proof path

Validator-backed proof path

Keep the public reading order tied to one evidence trail: profile, schema, example, validator result, and release record.

  1. 1Pick a message profile.Start with a published UAI-1 profile and the record family that matches the exchange you need to prove.
  2. 2Compare it with schemas and examples.Resolve the schema, registry entry, and one fixture before writing or mapping your candidate packet.
  3. 3Run validator evidence.Validate keyed, minified-keyed, or keyless JSON against the current public UAI-1 records.
  4. 4Attach the result to implementation or handoff records.Carry the exported result into implementation notes, changelog entries, or Project Handoff evidence.
Machine POSTValidate one candidate payload
curl -s https://justaniota.com/wp-json/uaix/v1/catalog
curl -s https://justaniota.com/wp-json/uaix/v1/examples/uai.intent.request.v1
curl -s -X POST https://justaniota.com/wp-json/uaix/v1/validate -H "Content-Type: application/json" -d @uai-message.json

Pair the validate route with the supporting catalog, registry, and example records when the result will travel into release evidence.

Plain English

The validator checks whether a candidate message is ready for review.

Technical summary

It validates shape, required metadata, Unicode safety risks, registry dependency, and compact export readiness, then produces a visible report.

Deep spec

Passing this local browser check is useful evidence. It is not UAI-1 conformance, certification, or UAIX.org approval.

Validation pipeline

  • Parse JSON and reject malformed input.
  • Require profile, UAI target version, locale, direction, normalization, registry, and payload.
  • Warn on PUA, bidi controls, variation selectors, invisible controls, and unsupported compact output assumptions.
  • Generate a demo compact form only after registry-dependent fields are present.

Validator / Encoder

Check the envelope before exporting compact tokens

The workbench validates required fields, Unicode safety warnings, registry IDs, compact-token mappings, public-safe payload shape, and deterministic demo encoding. When the plugin is active it uses the REST validator and keeps the browser path as fallback.

Validation report 

			

			

				Demo compact form