Agentic AI
Agentic AI Platform & Services
Sig and the agentic AI layer across every Cignus platform — AI assistants and agents that reach Helios API services, data sources, and MCP servers through role-based access control, plus custom agent development for your mission.
AI is only useful in aviation operations if it can reach real data — and only the data the person asking is cleared to see. The Agentic AI Platform is the layer that puts Sig, the Cignus aviation AI, inside every Cignus tool and platform, connected to Helios API services, data sources, and MCP servers through role-based access control.
The same platform backs our agentic AI services: custom agents, retrieval over your own document collections, and MCP integrations built for your systems, your data, and your access rules.
Capabilities
An AI that works inside your tools, within your role
Sig everywhere
Sig is embedded across Cignus applications — from cignus.ai to the NOTAMS Dashboard and Obstruction Watch — so help and analysis are available where the work happens.
Role-based access control
Sig and every agent reach Helios through the same role-based access as Cignus applications. What an agent can read or do follows the user’s role, enforced at the API layer — never in the prompt.
API services and data sources
Live NOTAMs, obstruction data, operational analytics, and other Helios data services become tools an agent can call, scoped per user.
MCP servers
Model Context Protocol servers expose Cignus platforms and data to AI agents and clients in a standard, auditable way.
Custom-trained models
Aviation-specific models — such as the NOTAM parsers behind the NOTAMS Dashboard — handle the phraseology general-purpose models get wrong.
Agentic AI services
We design and build agents, retrieval pipelines, and MCP integrations for your organisation, on your infrastructure or ours.
Architecture
How it works
1 · Connect
Helios API services, data sources, and MCP servers are registered as tools, each with the roles allowed to use it.
2 · Authorize
Every tool call carries the user’s identity; Helios interceptors check role and scope before any data is returned.
3 · Act
Sig or a custom agent plans the steps, calls the tools it is allowed to, and answers with the results — inside the application the user is already working in.
Technical profile
At a glance
- Assistant
- Sig — embedded in Cignus applications and cignus.ai
- Integration
- Helios REST APIs, data services, Model Context Protocol (MCP) servers
- Access control
- Role-based, per tool and per data scope, enforced at the Helios API layer
- Models
- Large language models plus custom-trained aviation models
- Services
- Custom agents, retrieval over private document collections, MCP integration, model fine-tuning
- Platform
- Helios — Cignus’s AWS-native aviation data and AI platform
- Access
- Role-based, enforced per request at the Helios API layer — not inside the application
FAQ
Common questions
Can Sig see data I am not cleared for?
No. Sig reaches data through the same role-based APIs as the applications, so it can only use what your role already allows.
Can you build agents on our own systems?
Yes. Our agentic AI services connect agents to your APIs and data sources through MCP, with your access rules applied at every call.
How is access controlled?
By role, at the API layer. Every request to Helios passes through interceptors that check the caller’s role and scope before any data is returned, so the same rules apply whether the request comes from the application, an API client, or an integration. Nothing is governed inside the application itself.
Put agentic AI to work in your operation
Talk to us about Sig in Cignus platforms, or about agents and MCP integrations for your own systems.