On June 3, 2026, EightX Labs opened agnt8x to the public — a platform the company calls “Workday for AI agents,” per its own launch announcement. Alongside it, they published the EightX Agent Manifest (EAM) v0.1, an open-source specification for declaring agent identity and capabilities in a way that compiles to any major runtime, documented at agnt8x.ai/docs and published on GitHub.
Two things in this launch matter for builders: the marketplace (where you can publish and earn recurring revenue from agents you build) and the EAM spec (which may become a portability layer you’ll want to know before it gets wide adoption).
The Problem agnt8x Is Solving
Enterprise buyers have more AI agents than they know what to do with. They’re spread across Claude, OpenAI Assistants, Vertex Agent Builder, Bedrock Agents, and a dozen niche orchestration frameworks — each with its own auth, billing, and audit trail. Governance is a spreadsheet held together with duct tape.
agnt8x positions itself as the neutral HR layer: one place to find, hire, onboard, manage, and orchestrate agents regardless of which LLM powers them.
For builders, the flip side is a buyer pool. If enterprises are managing agents through one catalog, the catalog becomes a distribution channel.
The Five Pillars
EightX Labs describes the five pillars this way in its launch announcement and product docs:
FIND — An ontology-based job board that matches agents to roles. Enterprises post role requirements; agents (and the builders behind them) are surfaced based on capability declarations in their EAM.
FORGE — A private catalog for enterprise-owned agents. If you’ve built proprietary agents for internal use, Forge is where they live under governance.
STUDIO — Described by EightX Labs as a nine-step onboarding workflow for publishing agents to the marketplace. This is the builder-facing entry point: connect your agent, declare its EAM, set pricing, go live.
MANAGE — Real-time P&L tracking, audit trails, and unified billing across all providers in one view. Enterprises see what each agent is costing and what it’s producing.
CONDUCTOR — Multi-agent orchestration across providers on a single canvas. Build workflows that hand off between a Claude agent, an OpenAI agent, and a Vertex agent without writing custom glue code. EightX Labs’ own launch materials call this “a capability no other platform has built” — a claim from the company itself, not an independently verified industry survey.
The EAM Spec: One Definition, Any Runtime
The EightX Agent Manifest (EAM) v0.1 is an open, Apache 2.0-licensed YAML format for declaring what an agent is — its identity, skills, connector requirements, sub-agents it can spawn, runtime compatibility, and operating policies, per the spec repository and EightX’s own documentation.
The practical implication: the same EAM file can compile to a Claude system prompt, an OpenAI Assistants definition, or a Google Vertex Agent, according to EightX’s docs — though the spec itself explicitly flags cases (like provider-specific fine-tuned models) where portability breaks rather than promising universal compatibility. Data residency requirements, PII handling rules, and authority limits are declared in the manifest and enforced by every compiler.
This is early. The spec is v0.1 (marked “Draft” in its changelog), and as of this writing no independent compiler or validator beyond EightX’s own tooling is publicly known. The Apache 2.0 license means the spec is open for anyone to implement, and if it gains traction it could become a portability layer worth knowing before it becomes mandatory boilerplate in RFPs.
Builder Monetization Model
The marketplace is two-sided. Enterprises pay agnt8x for platform access and agent usage. Builders earn recurring monthly revenue for as long as agents they publish remain active and running, per EightX’s own launch announcement.
This is meaningfully different from a one-time app sale. If an enterprise customer runs your billing-reconciliation agent thousands of times a month indefinitely, you collect a recurring share each month.
The revenue split is publicly posted, not hidden until onboarding: as of this writing, agnt8x’s pricing page lists a platform commission of 20% on agent hires and subscriptions, with builders keeping the remaining 80%; per-task fees carry a separate 10–15% platform commission per EightX’s docs. These figures can change — check the live pricing page before you plan around a specific split.
Deployment Modes (Matters for Enterprise Sales)
If you’re building agents targeting enterprise or government buyers, understanding the deployment tiers helps you pitch:
| Mode | Who it’s for | Data access |
|---|---|---|
| SaaS | Startups, mid-market | agnt8x cloud |
| Tenant Workspace | Larger enterprises | Single-tenant isolation |
| EMBASSY | Government, critical infrastructure | Full VPC, zero agnt8x access to runtime data |
Deployment modes per EightX’s launch announcement and docs. EMBASSY deployments today are hand-onboarded by the agnt8x enterprise team; EightX’s own docs state that “full self-serve Embassy tooling lands with the Series A infrastructure build, targeted Q3 2026” — note this is EightX’s stated target, not a confirmed funding close (no Series A has been publicly announced as of this writing).
Platform Pricing
As of this writing, agnt8x’s pricing page lists four employer-side tiers (pricing is live and subject to change, so verify current figures before quoting them to a prospect):
- Free — Browse agents and post jobs; 20% commission on agent hires and app subscriptions
- Solo — $0/month, 1 agent, 1 workspace, starter usage credits
- Pilot — $49.99/month (with a free trial), up to 2 agents, 1 team seat, MANAGE dashboard, Agent Passport
- Custom — Contact for pricing; unlimited agents/workspaces, sovereign trust tier, full monitoring, regulatory audit, dedicated Guardian, SOC 2 compliance
(Note: earlier drafts of this piece cited different tier names and prices; we could not confirm those against an archived snapshot of the launch-day pricing page, so the figures above reflect only what is verifiable on the live site now. Pricing on a pre-Series-A platform can move fast — verify before you quote it.)
Builders publishing to the marketplace are on a separate set of plans — you’re on the supply side, not the buyer side; see the revenue-share note above.
What to Watch
agnt8x is pre-Series A (EMBASSY is the Series A build target) and the EAM spec is v0.1. The platform is live with builder supply and enterprise demand, but the ecosystem depth — number of active agents, breadth of connectors, quality of ontology matching — will determine whether CONDUCTOR becomes the default orchestration layer or a footnote.
The EAM spec is the higher-stakes bet. If it sees adoption outside EightX’s own tooling, portable agent definitions become a real thing. If it doesn’t, it’s just how agnt8x represents agents internally.
Things to monitor:
- EAM v0.2 specification changes — follow eightx-labs/eam-spec on GitHub
- Third-party compiler implementations for Claude, OpenAI, Vertex
- EMBASSY GA date (targeted Q3 2026)
- Whether major agentic frameworks (LangGraph, CrewAI, AutoGen) publish EAM compatibility
Builder Decision Framework
Publish to the marketplace if: you have a vertical-specific agent that solves a repeatable enterprise workflow and you want distribution without building your own sales motion.
Adopt EAM now if: you’re building agents you expect to deploy across multiple LLM providers and want your capability declarations to be portable rather than bespoke per-provider.
Wait on CONDUCTOR if: your orchestration needs are single-provider. CONDUCTOR’s cross-provider value only materializes when you have agents running on Claude and OpenAI and Vertex simultaneously.
Watch EMBASSY if: your target customers are regulated industries (finance, healthcare, government). A zero-egress VPC deployment may be the unlock for deals that otherwise stall on data residency.