AIGNC

Explicit model discovery, text, image, and audio requests through the AIGNC API gateway.

4 listed actions2 capability groups

Connection facts

What the AIGNC connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method: api-key
Setup: Obtain an API key and account instructions from the AIGNC supplier, then connect provider aignc in StackOS. The supplied service address is not a verified signup, console, or public documentation page.
Capability groups: Image Generation, Model Access
Action boundaries: 1 read action3 cost-bearing actions

Action catalog

Actions listed for AIGNC.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

Search AIGNC actions

4 matching actions

Analyze AIGNC Audio

Model AccessUses a paid service

Analyze a project-scoped managed audio artifact using the explicit instruction and selected model. The daemon resolves and encodes the audio artifact for this request. Returns an action-call ID for polling while the provider works.

Complete AIGNC Chat

Model AccessUses a paid service

Make one nonstreaming text request using the agent-selected model and messages, with optional explicit Google search on Gemini models. Returns an action-call ID for polling while the provider works.

Generate AIGNC Image

Image GenerationUses a paid service

Make one text-to-image request and persist the returned JPEG as an artifact. Returns an action-call ID for polling while the provider works.

List AIGNC Models

Model AccessReads data

Read the current AIGNC model IDs. Discovery does not enable unreviewed model capabilities or select a model.

Direct answer

How does the AIGNC integration work?

People continue using AIGNC as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

01Your requestStart in your AI
02StackOS planExpands the steps
03AIGNCDoes its bounded part
04Checked resultKeeps the proof

Common questions

AIGNC and StackOS.

What can the AIGNC integration do in StackOS?

The current catalog includes 4 AIGNC actions across Image Generation, Model Access. The exact actions used depend on the workflow and approval rules.

Does StackOS replace AIGNC?

No. AIGNC remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.