Agent Gallery
Agent Gallery OperationsCertifying Agents

Agent Readiness Measures

How the Agent Gallery certifies agents across Functionality, Performance, and Security.

Certifying Agents

Outcome: a clear, explainable certification that scales across thousands of agents.

Each agent in the Gallery is certified on three pillars:

  • Performance — effectiveness, correctness & latency
  • Security — risk-based posture, supply chain & agent-specific (i.e. prompt-injections)
  • Functional — ecosystem readiness & usability
DimensionMetric TypeAssessment OutputFrequency
PerformanceQuantitativePass / FailPost-Build / Continuous (latency measured at runtime)
SecurityQualitative Risk MatrixA, B, C, DPeriodic (currently every 30 days, compliant to ageing policy)
FunctionalEcosystem ReadinessExcellent, Strong, Moderate and BasicPost-Build

Readiness (Technology Readiness Level)

When certifying an agent, you select its current production tier / level — the Technology Readiness Level (TRL) that best reflects where the agent is in its lifecycle. This selection appears in the certification workflow as the Readiness step.

Certify My Agent — Readiness step showing the seven TRL tiers: Concept & Roadmap through Production Tier - Regulatory Usage.

The seven tiers are:

LevelTierDescription
1Concept & Roadmap TierAgent requirements and functionalities conceptualized and validated for business outcomes. Design/build in progress.
2Prototype TierWorking standalone agent prototypes validated for intended functionality and outcomes with mostly synthetic data.
3Trusted Agent Huddle TierWorking agent prototypes onboarded to AI Refinery and enabled for trusted agent huddle orchestration across systems.
4Pilot TierWorking agents with full functionality and limited robustness in a real-life workflow tuned to perform with production data.
5Production Tier – General UsageWorking agents that are deployed and operating in general purpose internal facing scaled production usage.
6Production Tier – Customer UsageWorking agents with high functionality, performance, tuning, controls for customer facing scaled production usage.
7Production Tier – Regulatory UsageWorking agents with high functionality, performance, tuning, regulatory level controls for highly regulated production usage.

For how TRL fits with maturity and certification, see Agent Maturity.

Whenever viewing the details of an agent, we can see the current certification status for Performance, Functional and Security dimensions. Clicking on the See details link on each of the certification status cards will open a dialog with the specific certification details.

Agent certification overview dashboard showing summary tiles and statuses.

The performance card consists of performance tests conducted on this agent. Hover each of the icons to see more details.

The Tools work and Latency tests work on aggregate data from multiple users, as such, they are not available for some of the agents on the gallery till more data is collected through frequent usage. Read Performance Certification to see how we validate correctness & speed.

Performance certification interface highlighting latency and correctness metrics.

The functional card consists of performance tests conducted on this agent. Hover each of the icons to see more details. Read Functionality Certification for more details.

Functional certification checklist emphasizing ecosystem readiness.

The security certification card consists of the final security score of this agent. Hover each of the icons to see more details (e.g. how many critical, high, medium vulnerabilities were flagged in the container scan). Read Security Certification for details on the grading pipeline.

Security certification risk matrix with graded findings.

Certification Process

Sequence of Certification

For MCP Agents built from open source repositories, the order is: build, certify, publish to gallery. For agents added by gallery users, certification runs in parallel so agents can be onboarded and tested quickly.

The certification workflow establishes a complete chain of evidence: code assessment, pre-testing documentation (Evidence Box 1), evidence collection (Evidence Box 2), and secure evidence bundling. For the full process, required artifacts, and how evidence is anchored to each agent and code version, see Chain of Evidence.

Next steps