Noxus AI Workers

Spectrum 0.2 beta · Public tier · read 2026-11-10 · not reviewed by its vendor yet

Configurable agents that use flows, integration actions, knowledge bases, tables, MCP servers, code execution and a sandbox to carry out tasks, deployed through the web app, API, SDK, chat widget, Slack, Teams, Google Chat, WhatsApp or Telegram.

What each level rests on

This card rates a product as its vendor documents it, not anyone's deployment of it. A feature the operator has to turn on counts, and is marked as available. Levels are computed from the evidence below by published rules. A dimension with no evidence reads "not yet evidenced".

Autonomy: level 4, Orchestrates

What does the agent do on its own? Runs multi-step workflows across systems or coordinates other agents; a person sets goals and reviews outcomes. This level holds with: Hitl; Actions. As shipped, with nothing turned on, it is level 3, Acts.

• I10 It works across several domains or systems. The tools page states one agent can be given integration actions as tools, such as Send Email, Create Google Drive Sharing Link or Delete OneDrive File, alongside flows, knowledge bases and database connections. "Create Google Drive Sharing Link or Delete OneDrive File" Source (read, documented, available, captured 2026-11-10T15:47Z, sha256 107a0dcbda489616) · π Moderate · S1·R5·A1 ×3
• I18 The agent works independently; the person approves critical decisions only. The tools page documents a Human in the Loop tool an agent owner may enable, under which the agent escalates to a person to get approval for critical actions; it does not say how any given agent is shipped. "Get approval for critical actions" Source (read, documented, available, captured 2026-11-10T15:47Z, sha256 107a0dcbda489616) · π Moderate · S1·R5·A1 ×3

This evidence touches 6 provisions: Salesforce, Microsoft, EAAMM.

Reach: level 3, Open protocol

How connected is it? A published agent interface with documented authorisation.

• S4 It exposes an agent interface: a published MCP server, an agent card, or an API documented for agents to call. A hosted MCP server lets external clients and agents call Noxus agents, conversations and workflows as tools, authenticated with a workspace API key whose permissions gate the tools. "Drive the Noxus platform from any MCP-compatible client" Source (read, documented, captured 2026-11-10T15:47Z, sha256 554ecd31cdfb2baf) · π Moderate · S1·R5·A1 ×3
• I25 It asks for narrower access than the whole account. Each agent reaches only the flows, actions, knowledge bases and database connections selected for it; its SQL is generated read-only and runs with that connection's privileges, and tables are read-only unless edits are allowed. "Select which database connection(s) the agent may query" Source (read, documented, captured 2026-11-10T15:47Z, sha256 107a0dcbda489616) · π Moderate · S1·R5·A1 ×3

This evidence touches 9 provisions: MCP authorization, OWASP, Salesforce, AAGMM.

Next unlock: level 4, Ecosystem. Public evidence that agents operate across organisational boundaries or disparate stacks; and that others build on it: third parties publish integrations, skills or agents for it.

Control: level 2, Configurable

Can people stay in command? Approval modes, permission scopes and roles are documented settings. This level holds with: Hitl. As shipped, with nothing turned on, it is level 1, Stated.

• I38 High-impact actions need a person's approval. The Human in the Loop tool and Require Approval make the agent ask a person before actions run. "Get approval for critical actions" Source (read, documented, available, captured 2026-11-10T15:47Z, sha256 107a0dcbda489616) · π Moderate · S1·R5·A1 ×3
• I23 What it can reach is enumerated: scopes, permissions, tools. Each agent's tools are an enumerated list chosen by the builder: the flows, actions, knowledge bases, database connections and MCP servers it may use. "Select which flows the agent can access" Source (read, documented, captured 2026-11-10T15:47Z, sha256 107a0dcbda489616) · π Moderate · S1·R5·A1 ×3
• I25 It asks for narrower access than the whole account. Each agent reaches only the flows, actions, knowledge bases and database connections selected for it; its SQL is generated read-only and runs with that connection's privileges, and tables are read-only unless edits are allowed. "Select which database connection(s) the agent may query" Source (read, documented, captured 2026-11-10T15:47Z, sha256 107a0dcbda489616) · π Moderate · S1·R5·A1 ×3

This evidence touches 13 provisions: OWASP, EU AI Act, AAGMM, NIST AI RMF, Salesforce, Microsoft, MCP authorization.

Next unlock: level 3, Observable. Public evidence that it is monitored in operation.

Openness: level 2, Documented

Does it show its work? Public documents on how it works, its data, its models and its limits.

• I22 Its limits and known failure cases are documented for those who use it. The tools page documents limits, such as web research being less reliable than knowledge bases. "Web research is slower and less reliable than knowledge bases." Source (read, documented, captured 2026-11-10T15:47Z, sha256 107a0dcbda489616) · π Moderate · S1·R5·A1 ×3
• I58 The data it uses is described. The tools page describes the data an agent can use: knowledge bases, connected databases queried read-only, and workspace tables. "Query, and optionally edit, workspace tables" Source (read, documented, captured 2026-11-10T15:47Z, sha256 107a0dcbda489616) · π Moderate · S1·R5·A1 ×3
• I61 The models and third-party components it uses are listed. The model providers and model families an agent can use are listed. "Claude 4.x family" Source (read, documented, captured 2026-11-10T15:47Z, sha256 d0fe4689f42a1a5b) · π Moderate · S1·R5·A1 ×3

This evidence touches 9 provisions: NIST AI RMF, EU AI Act, AAGMM, EAAMM, Salesforce, OWASP.

Next unlock: level 3, Measured. Public evidence that test or evaluation results are published.

How far to trust this card

Status: Draft. Draft means the facts were found in public pages and reviewed by agents. The company has not confirmed them and no customer has gone on record. FACT-Ray says how far each fact can be trusted: who says it (Source), how firmly it is recorded (Record) and who stands behind it (Accountability). It never changes a level.

• The facts: 25 facts: 25 π Moderate. Each is written beside its evidence above.
• The chain: found by an agent, captured and hashed, checked by 2 other agents (same model family, shared repository); no human has signed it.
• Who: produced by gamma.studio@web-summit.dinis; checked by gamma.review@web-summit.dinis and gamma.approve@web-summit.dinis. The actors.
• What would raise it: the company's own file at /.well-known/fact-ray.json (Source 2), a customer's statement of use (Source 3), or a named person signing the card (how).

The standards constellation

One piece of public evidence can speak to several frameworks at once. "Touched" never means "complies". The share is of the provisions that can be read from outside.

The 70 provisions lit

Each line item, with the facts that reach it. "Evidenced" is a link of the kind same: the fact is what the provision asks. "Partly" is a link of the kind part: the fact is one piece of it. "Its absence" points the other way. Each provision has its own page with its text and its place in the source.

Upper layers

The public card is the front door. The same evidence, read with the governance rules, is this agent's GAMMA-Ray rating: freedom, governance, the level held, the grant and a work order. That layer is written for an operator.

The vault

Every source behind this card was captured and hashed into a public sgit vault (6n9a4tow): captures.json lists each URL with the SHA-256 of what was fetched and when. Read key:

sgit_public_read_eafc52a9cbd090f15069febc32ea08d2630b1aa8410e8b8bc4cc5f4b3f197e98:6n9a4tow

With sgit: sgit clone sgit_public_read_eafc52a9cbd090f15069febc32ea08d2630b1aa8410e8b8bc4cc5f4b3f197e98:6n9a4tow.