Badge Reference
The Developer Portal uses small coloured badges on card tiles to summarise what a listing is, what state it is in, and what it will do once installed. This page is the authoritative reference for every badge the portal renders.
If you are looking for the badges shown to end-users in Settings → Integrations, see Apps & Channels — Badge Reference instead.
Where badges appear
| Section | URL | What you are looking at |
|---|---|---|
| Apps | /developer/apps | App listings you have registered (with or without an adapter URL). |
| Skills | /developer/skills | Skill listings — engine-facing tool + credential + knowledge bundles. |
| Tools | /developer/tools | Your custom ToolFactory tool definitions and the read-only Standard Tool Library catalog. |
| MCP Servers | /developer/mcp | MCP server connections you have configured for tool discovery. |
Listing status
Apps and Skills share the same lifecycle statuses. The badge is a direct read of the listing's status column.
| Badge | Status value | What it means |
|---|---|---|
| Draft (grey) | draft | The listing exists in your portal only. It is not visible in the marketplace, not installable by any organisation other than yours, and can be edited freely. |
| In Review (yellow) | in_review | You have submitted the listing for platform review. The ORQO team inspects the manifest, adapter, and any declared tools. No edits are accepted until review concludes. |
| Published (green) | published | Review passed. The listing is now visible in the public Integrations catalog and installable by any organisation. |
| Rejected (red) | rejected | Review failed. Read the review notes on the detail page, address the issues, and resubmit. |
| Suspended (red) | suspended | A previously-published listing that has been pulled from the catalog (e.g. upstream API broken, security finding, author request). Existing installations keep running but no new installations are possible. |
Ownership
Ownership is a separate axis from status — every published listing is either first-party or third-party.
| Badge | Column | What it means |
|---|---|---|
| Platform (green) | platform = true | A first-party ORQO listing. The platform flag is only settable by ORQO staff superadmins from the developer portal. Platform listings never go through the public review lifecycle. |
| Community (grey) | platform = false | A third-party listing published by a developer or organisation. This is the default for every listing you create in the Developer Portal. Community listings progress through the full draft → in_review → published lifecycle. |
App-specific badges
On /developer/apps cards:
| Badge | Meaning |
|---|---|
| Channel | The adapter declares no MCP tools — it handles inbound/outbound message transport only. See Apps vs Channels. |
| Category | The category value from the manifest (titleised — e.g. Communication, Development, Research). Drives the filter pills at the top of the page. |
| N triggers (yellow) | The manifest declares N triggers — scheduled or event-driven entry points that start workflows on behalf of the App. A count badge only appears when N > 0. |
| CI passing (green) | The most recent automated manifest + adapter verification succeeded. This covers /health, manifest parsing, and — for non-Channel Apps — MCP tools/list discovery. |
| CI failing (red) | The most recent CI run failed. Open the detail page to read the failure output. A red badge blocks the Submit for Review action. No badge at all means CI has not yet run (e.g. no adapter URL set). |
| N installs | How many organisations currently have this App installed. Useful as a popularity / blast-radius signal before you push a new version. |
Skill-specific badges
On /developer/skills cards:
| Badge | Meaning |
|---|---|
| Category | As with Apps — the manifest category. |
| N tools (blue) | The number of tools the skill manifest bundles. This is the union of standard-library names, ToolFactory references, and MCP tools resolved from the skill's server. |
| MCP (blue) | The skill declares an mcp_url — i.e. it points at an MCP server that will be provisioned when the skill is installed. Skills without an MCP server show no MCP badge; they either reference the standard library or bring ToolFactory tools of their own. |
| N installs | As with Apps — active installation count across organisations. |
Custom tool badges
On /developer/tools, each tool you have created shows a combination of the following flags. They correspond 1-to-1 with columns on the tool_definitions record.
| Badge | Column | What it changes at runtime |
|---|---|---|
| Library (grey) | sealed = true | The tool is platform-managed. Its Python source is maintained by ORQO and cannot be edited in the portal. You can still remove it from your tool set. Library tools are the same tools that appear read-only under the Standard Tool Library section. |
| Auto-share (blue) | auto_share_result = true | When an agent in a team calls this tool, the result is broadcast to the rest of the team automatically. Use this for tools whose output is genuinely useful for every teammate — e.g. a shared research result — and leave it off for noisy tools. |
| Runtime (yellow) | requires_runtime = true | The tool executes on a connected runtime instead of inside the engine. This is mandatory for any tool that runs shell commands, touches the filesystem, or spawns subprocesses — the engine will refuse to turn the flag off for such tools. |
| KG (accent) | enriches_knowledge_graph = true | The tool's result is fed into the asynchronous Knowledge Curator pipeline. Enable this for tools whose output is knowledge-worthy (research, scraping, document reading); leave it off for control-plane tools (send message, toggle flag). |
| N params | parameters.size | The count of declared parameters on the tool. Informational only. |
Standard Tool Library badges
Under the Tool Library section on the Tools page, each standard tool shows:
| Badge | Meaning |
|---|---|
| Category | One of Filesystem, Shell, Git, Web, Communication, Integrations, Documents, Data, Knowledge. The category drives the tab pills at the top of the library. |
| Runtime (yellow) | The tool requires a runtime to execute (shell, filesystem, git — all runtime-only). |
| N params | Number of declared parameters on the tool signature. |
| N credentials (yellow) | Number of credentials the tool reads at invocation time. Opening the drawer shows the exact credential keys. |
Standard Library tools never display Library (they are all library tools by definition), Auto-share, or KG — those flags belong to the tool_definitions table and are not exposed for engine-native tools.
MCP Server badges
On /developer/mcp cards:
| Badge | Meaning |
|---|---|
| Transport (mono-font) | The transport declared on the MCP connection — sse, http, or stdio. Rendered in a monospace font to distinguish it from human-readable labels. |
| Verified (green) | The last tools/list handshake succeeded. The server is reachable and tool discovery is up-to-date. |
| Unverified (yellow) | The server is fully configured but has not yet responded successfully. Use the Verify action on the drawer to run the handshake. |
| Not configured (yellow) | The record exists but is missing required configuration (URL, credentials, or transport). You cannot verify it until configuration is complete. |
| N tools | The number of tools discovered on the server's last successful tools/list call. Zero means either the server was never verified or it exposes no tools. |
Quick legend
Across the portal, colours are used consistently:
| Colour | Meaning |
|---|---|
| Green (success) | Ready / healthy / published / verified |
| Yellow (warning) | Needs attention, missing configuration, or review pending |
| Red (error) | Failed verification, rejected, or suspended |
| Blue (info) | Informational tag — no action implied |
| Accent | Category or knowledge-graph flag |
| Grey (neutral) | Draft, library, locked, or plain count |
If a card is missing a badge you expect — e.g. no CI passing on an App — it usually means the underlying check has not run yet, not that it failed. Open the detail drawer to see the most recent verification output.