Ignition 8.3 API enhancementsIgnition 8.3.8API runner requiredAPI-24 - API v0.103.0 · Skill v0.3.9

Give AI agents the Gateway actions Ignition's built-in OpenAPI does not cover.

Ignition 8.3's OpenAPI is the native foundation. API v0.103.0 adds 72 discoverable, bounded actions for the work an AI agent still needs to inspect, dry-run, apply, read back, and verify across Jython, tags, alarms, Perspective, Vision, expressions, SFCs, UDTs, and Gateway runtime behavior.

Ignition 8.3 API v0.103.0

OpenAPI gap map / API v0.103.0

72 bounded actions that help an AI agent finish the job.

Ignition's built-in OpenAPI is the native foundation. The llmImport enhancement layer adds the tested workflows below for runtime discovery, bounded changes, exact readback, and evidence when the native API does not expose the complete agent workflow.

Native foundation

Built-in OpenAPI

Use Ignition's official endpoints first whenever they cover the task.

Enhancement layer

72 fixed actions

Discoverable names, bounded inputs, dry-run gates, result contracts, and readback.

Agent workflow

Inspect → act → verify

The agent can show what ran, what changed, what was read back, and what remains unproven.

Action inventory

Find the gap your agent needs to cross.

Showing 72 of 72 actions

Read onlyBounded testDry-run + apply

17 actions

Jython runtime and language boundaries

Shows the agent what Ignition's embedded Jython can actually parse, import, and execute before it writes a script.

Why an agent needs it

Prevents Python 3 syntax, unavailable-package, Unicode, import, Java interop, and runtime assumptions.

  • runtime-profile-v2Bounded test

    Reports the embedded Jython version, Python 2 behavior, UTF-8 boundaries, numeric behavior, and Java availability.

  • python2-guardrails-v1Bounded test

    Runs a fixed syntax and behavior matrix that separates valid Jython 2.7 code from Python 3-only forms.

  • python2-module-names-v1Bounded test

    Checks Python 2 standard-library module names and bounded Queue, URL, HTTP, ConfigParser, and SocketServer behavior.

  • import-fallback-guardrails-v1Bounded test

    Tests safe import fallbacks for missing modules, members, nested imports, and broad exception handling.

  • text-byte-boundaries-v1Bounded test

    Checks explicit UTF-8 encoding and decoding, str/unicode mixing, joins, formatting, and invalid codecs.

  • python3-api-guardrails-v1Bounded test

    Proves selected Python 3-only APIs are absent and records the bounded Python 2 alternatives.

  • exception-boundaries-v1Bounded test

    Exercises Python and Java exception routing, mixed catches, finally blocks, and cleanup-failure masking.

  • builtin-surface-v1Bounded test

    Checks Python 2 built-ins, eager map/filter/zip behavior, map(None, ...), reduce, and module naming.

  • stdlib-inventory-v1Read only

    Compares the embedded standard-library inventory with the fixed standalone Jython allowlist without importing arbitrary modules.

  • dependency-resolution-v1Read only

    Resolves a fixed set of Java classes through Ignition's class loaders and reports bounded version and loader evidence.

  • java-interop-v1Bounded test

    Checks Python callback adaptation, callback arity, Java char typing, and Java compiler availability.

  • language-compat-v1Bounded test

    Tests fixed syntax, XML support, and bounded import attempts for dataclasses, NumPy, and pandas.

  • embedded-runtime-v1Bounded test

    Checks warnings, restored sys.argv state, protocol-2 pickle behavior, interactive compilation, and Java 17 imports.

  • native-compat-v1Bounded test

    Separates pure-Python and Java-library options from unsupported native-extension assumptions.

  • overload-resolution-v1Bounded test

    Exercises fixed and varargs Java overload resolution with embedded classes and no external fixture.

  • unicode-data-v1Bounded test

    Checks selected Unicode 15.1 names, the data version, and invalid-name behavior without inferring Python 3 support.

  • sys-readonly-v1Bounded test

    Proves fixed sys attributes remain protected and verifies temporary runtime state is completely cleaned up.

9 actions

Execution safety and reliable outcomes

Gives an agent explicit contracts for timeouts, asynchronous work, writes, transactions, retries, scope, time, and logs.

Why an agent needs it

Helps the agent distinguish accepted work from verified completion and outcome-unknown states.

  • deadline-budget-v1Bounded test

    Tests monotonic clocks, integer-millisecond validation, deadline rounding, clamping, and one-budget allocation.

  • async-ownership-contract-v1Bounded test

    Exercises Future completion, worker failure, timeout, cancellation, interruption, and executor cleanup.

  • write-readback-state-v1Bounded test

    Classifies write quality, readback, stale values, mismatches, partial failures, and fully verified success.

  • message-payload-contract-v1Bounded test

    Validates a fixed bounded message schema, including exact keys, types, counts, duplicate paths, and finite numbers.

  • transaction-lifecycle-v1Bounded test

    Checks begin, work, commit, rollback, close, cleanup failure, and commit-outcome-unknown ordering.

  • idempotency-state-v1Bounded test

    Exercises duplicate and conflict suppression, retry authorization, bounded attempts, completion, and unknown outcomes.

  • scope-capability-contract-v1Bounded test

    Tests ordered scope, availability, resource, authorization, completion, and Vision UI-thread decisions.

  • date-time-contract-v1Bounded test

    Checks epoch units, strict parsing, explicit time zones, DST gaps and overlaps, and elapsed versus calendar time.

  • logging-diagnostic-contract-v1Bounded test

    Tests a bounded diagnostic schema, severity policy, correlation IDs, sensitive fields, lazy debug work, and logger failures.

9 actions

Project Library and event lifecycle evidence

Covers the hard parts of changing shared project code while Gateway requests, callbacks, and tag events may still be in flight.

Why an agent needs it

Reduces bad assumptions about imports, cached references, signature changes, callbacks, and duplicate event delivery.

  • tag-event-lifecycle-contract-v1Bounded test

    Checks Gateway Tag Change versus Value Changed selection, initial execution, missed events, quality, timestamps, and project lifecycle.

  • tag-event-reconciliation-contract-v1Bounded test

    Exercises duplicate suppression, stale observations, conflicts, overflow, quality recovery, checkpoints, and outcome-unknown handling.

  • project-library-state-v1Bounded test

    Observes fixed Project Library generation and thread-safe state across a two-phase import protocol.

  • project-library-import-contract-v1Bounded test

    Tests failed initialization, missing dependencies, circular imports, acyclic imports, and successful caching.

  • project-library-reference-contract-v1Bounded test

    Checks how held module, function, and object references behave when a module is replaced or removed.

  • project-library-member-contract-v1Bounded test

    Checks captured functions and bound methods when module functions or class members are removed.

  • project-library-signature-contract-v1Bounded test

    Tests changed defaults, keyword names, required arguments, positional order, and captured callables across generations.

  • project-library-return-contract-v1Bounded test

    Tests migrations from scalar, list, or None returns to exact versioned result envelopes.

  • project-library-callback-contract-v1Bounded test

    Exercises callback registration, generation conflicts, replacement, unregister, captured callbacks, and empty cleanup state.

4 actions

Gateway capability and data discovery

Lets an agent inspect a bounded picture of the Gateway before choosing a tool or making a compatibility claim.

Why an agent needs it

Replaces guesses about available functions, data shapes, secret APIs, and configuration access with direct evidence.

  • ignition-basics-v1Read only

    Reports availability of fixed database, transaction, tag, async, Vision, and Perspective functions in Gateway scope.

  • data-boundaries-v1Bounded test

    Checks Dataset and PyDataset iteration, JSON boundaries, malformed input, date round trips, time zones, and message-function availability.

  • secrets-availability-v1Read only

    Reports only the availability of current and legacy secret-management function names without reading any secret value.

  • system-config-read-v1Read only

    Performs bounded configuration discovery without returning configuration values or calling write operations.

8 actions

Perspective resources and live-session workflows

Adds bounded ways to inspect tags, create owned test resources, update routes and scripts, and exercise a live session.

Why an agent needs it

Moves the agent from generating loose JSON to applying a constrained change and reading the saved resource back.

  • perspective-tag-read-v1Read only

    Reads value, quality, and timestamp evidence from two fixed Perspective test tags plus a missing-path case.

  • perspective-click-counter-v1Bounded test

    Tests a fixed click-counter function against valid inputs and exact type and range failures.

  • perspective-boolean-tag-write-v1Dry-run + apply

    Dry-runs or writes one fixed Boolean test tag, then verifies write quality and exact readback.

  • perspective-session-navigate-v1Dry-run + apply

    Dry-runs or requests allowlisted navigation for one verified llm-tools browser session and page.

  • perspective-static-view-folder-v1Dry-run + apply

    Creates or updates one owned Perspective view shape with scan locking, atomic replacement, and label readback.

  • perspective-page-route-folder-v1Dry-run + apply

    Creates or updates one owned /llm-tests route while preserving page configuration and verifying the route count.

  • perspective-project-script-folder-v1Dry-run + apply

    Creates or updates one fixed Gateway project-script module and verifies the saved revision after a scan.

  • perspective-project-script-t11-invoke-v1Read only

    Invokes the fixed project module with bounded inputs and validates the exact returned envelope.

7 actions

Tags, history, complex values, and grouped UDTs

Adds scoped reads and writes for tag work that an agent needs to inspect, change, and verify carefully.

Why an agent needs it

Gives the agent bounded prefixes, dry runs, hashes, readback, quality, truncation, and retry evidence.

  • tag-read-v1Read only

    Reads up to 64 scoped qualified tag paths with value, quality, timestamp, type, and bounded nested serialization.

  • tag-browse-v1Read only

    Browses a scoped base path with recursive and type filters, sorting, truncation, and continuation evidence.

  • tag-write-v1Dry-run + apply

    Dry-runs or applies up to 32 scoped scalar writes, with before/after reads, quality, equality, and per-item results.

  • tag-query-history-v1Read only

    Queries bounded raw history for exact scoped tag paths over a window of no more than 24 hours.

  • grouped-udt-file-v1Dry-run + apply

    Inspects, creates, or replaces one validated grouped-UDT resource with dry-run, hash preconditions, and readback requirements.

  • tag-read-complex-v1Read only

    Reads scalar, array, Dataset, or Document values with explicit size, depth, type, quality, and truncation boundaries.

  • tag-document-cas-v1Dry-run + apply

    Dry-runs or writes one Document tag under timestamp and SHA-256 preconditions, then verifies its hash and readback.

6 actions

Alarm status, journal, acknowledgement, and shelving

Adds scoped alarm inspection and controlled operator actions with exact event or source identifiers.

Why an agent needs it

Lets an agent query first, dry-run changes, and verify acknowledgement or shelving state before reporting success.

  • alarm-query-status-v1Read only

    Queries bounded current alarm rows by scoped tag prefixes, state, priority, and selected associated data.

  • alarm-query-shelved-v1Read only

    Lists bounded shelved alarm sources with expiration, expired state, user, completeness, and truncation fields.

  • alarm-acknowledge-v1Dry-run + apply

    Dry-runs or acknowledges exact scoped event IDs, then verifies each retained event is acknowledged.

  • alarm-shelve-v1Dry-run + apply

    Dry-runs or shelves exact scoped alarm sources for a bounded duration and verifies the shelved-path readback.

  • alarm-unshelve-v1Dry-run + apply

    Dry-runs or unshelves exact scoped alarm sources and verifies they are absent from the shelved-path readback.

  • alarm-query-journal-v1Read only

    Queries one named alarm journal for exact event IDs, scoped paths, selected data, and a window of no more than one hour.

5 actions

Expression tags, Event Streams, and Named Query bindings

Adds owned fixtures for version-specific expression work that needs real Gateway configuration and runtime evidence.

Why an agent needs it

Lets the agent prove configuration, execution, quality, selection, locale, and cleanup instead of only returning expression text.

  • expression-tag-batch-v1Dry-run + apply

    Dry-runs or creates up to 100 bounded, side-effect-free expression tags inside one owned run folder.

  • expression-tag-fixture-suite-v1Dry-run + apply

    Creates server-owned expression profiles for sibling and dynamic references, quality behavior, and fixed runScript exception controls.

  • expression-tag-cleanup-v1Dry-run + apply

    Inspects, dry-runs, or deletes only an owned expression run folder and verifies its absence.

  • event-stream-expression-fixture-v1Dry-run + apply

    Sets up, triggers, inspects, and cleans up one fixed Event Stream expression fixture with bounded source values.

  • perspective-named-query-expression-fixture-v1Dry-run + apply

    Exercises a fixed Perspective view, Named Queries, route, locale, selection, tag run, navigation, inspection, and cleanup workflow.

3 actions

SFC transition and parallel-expression workflows

Adds fixed SFC environments where an agent can exercise transition, gate, retargeting, cancellation, and parallel cases.

Why an agent needs it

Provides bounded chart and tag evidence without accepting caller-supplied projects, expressions, paths, or Jython.

  • sfc-transition-expression-fixture-v1Dry-run + apply

    Sets up, starts, gates, retargets, inspects, and cleans up fixed SFC transition-expression cases.

  • sfc-parallel-expression-fixture-v1Dry-run + apply

    Exercises one fixed parallel-cancel SFC through setup, tag-driven start, cancellation, inspection, and cleanup.

  • sfc-parallel-expression-suite-v1Dry-run + apply

    Runs nine allowlisted SFC parallel-expression cases through setup, start, trigger change, inspection, and cleanup.

2 actions

Vision skill-lab and client-session evidence

Adds a bounded bridge for Vision work that spans Gateway setup, Client behavior, screenshots, language boundaries, and registered sessions.

Why an agent needs it

Lets the agent connect generated Vision code to a controlled test workflow instead of stopping at the script.

  • vision-skill-lab-v1Dry-run + apply

    Manages the fixed disposable Vision skill lab and its button, snapshot, window-state, runtime, Client, and Gateway language-boundary bridges.

  • vision-client-sessions-v1Read only

    Reads bounded registered Vision session rows for the expected project without returning client addresses.

2 actions

Local connectivity and encoding checks

Separates raw socket behavior from Ignition's HTTP client so the agent can diagnose the correct network layer.

Why an agent needs it

Replaces vague network assumptions with bounded localhost health, refusal, timeout, encoding, and cleanup evidence.

  • socket-unicode-v1Bounded test

    Exercises localhost-only raw-socket encoding, timeout, error, and cleanup cases.

  • http-client-v1Bounded test

    Exercises fixed localhost system.net.httpClient health and refused-connection cases separately from raw sockets.

These are bounded actions, not arbitrary code execution. A passing result proves only the documented action and returned evidence. The agent still has to inspect dry-run state, side effects, readback, and any unproven boundary before it reports success.

Why it was made

  • Starts with Ignition's official OpenAPI, then supplies bounded actions for the tested gaps in an agent's workflow.
  • Lets the agent discover exact action names before it makes assumptions about what the Gateway can do.
  • Separates request acceptance from dry-run state, external side effects, exact readback, and action-specific success.
  • Ships all 16 helper modules the Web Dev methods import, with no disabled method placeholders in the project ZIP.

Common use cases

  • Check the embedded Jython 2.7.4 runtime before generating Gateway scripts.
  • Read, browse, write, and query tag history inside explicit prefixes and limits.
  • Query, acknowledge, shelve, or unshelve selected alarms with dry-run and verification fields.
  • Exercise bounded Perspective, Vision, expression, SFC, Event Stream, and grouped-UDT workflows when OpenAPI does not cover the full task.

Proof style

Validate the artifact, not the promise.

Every result stays action-scoped. A top-level pass never replaces the documented action-specific fields, exact readback, side-effect state, trial state, or untested boundaries.

Example prompt

Copy-ready prompt
Read the Ignition 8.3 llmImport health route and summarize whether the Gateway is reachable, which API version is live, and the major action groups available. Keep the response concise. Then identify the exact fixed action and result fields needed for my task before running anything.

This is the kind of focused instruction the skill is designed to make useful. The value is in the checks and Ignition-specific defaults the AI uses after reading the skill.

Expected output

  • Confirms reachability, API v0.103.0, and the discovered 72-action inventory.
  • Groups the relevant expression, SFC, Vision, tag, alarm, Perspective, UDT, Jython, runtime, and data-boundary capabilities without dumping the full contract.
  • Names the action-specific fields that determine success, dry-run state, writes, and readback.
  • Keeps fixture-scoped results separate from broad claims about every Gateway, project, library, or resource.

Lifetime membership

Want access to this skill?

The one-time membership unlocks this skill, the full Ignition AI Toolkit, the Web Dev runner materials, setup docs, and versioned Ignition 8.1 and 8.3 downloads.

$99Limited-time Founder EditionFuture 8.3 skills included

No subscription. Lifetime members keep portal access to the current toolkit and future skill releases, including planned Ignition 8.3-focused skills as they are added.

Founder lifetime access - $99