One governed runtime, many jobs
Every marketplace agent runs on the same six core agents, the same permission model, the same approval thresholds and the same activity log. A new agent is a new job, not a new system to secure.
Agent Marketplace
Ten specialist agents built on the six core Xiilio agents — the same permissions, the same approval thresholds, the same activity log. Deploy the two or three you actually need, and add more once they have earned it.
Every marketplace agent runs on the same six core agents, the same permission model, the same approval thresholds and the same activity log. A new agent is a new job, not a new system to secure.
Most companies need two or three of these, not ten. Deploy the ones that match the work you are short-handed on, and add others when the first ones have earned it.
Once your CRM, calendar, ad accounts, inbox and billing are connected once, every additional agent starts with the context the last one built. That is the argument for a marketplace over ten separate tools.
Ten specialist agents, each one a job rather than a feature. Shortlist the ones that match the work you are short-handed on — nothing is deployed or charged from this page.
Revenue · Outbound prospecting
Researches accounts, drafts the outreach and works the replies — with a person approving what goes out.
Built on NOVA · HERALD · NEXUS
Revenue · Booking and reminders
Qualifies the enquiry, books the meeting into a real calendar and chases the no-shows.
Built on ARIA · NEXUS
Revenue · Pipeline analysis
Watches the pipeline for stalls, risk and forecast drift, and says what to do about each one.
Built on CORTEX · NEXUS
Customer · Inbound resolution
Answers documented questions across voice, chat and messaging, and escalates everything else with context.
Built on ARIA · NEXUS
Customer · Retention and expansion
Spots churn and expansion signals early, and prepares the account owner's next conversation.
Built on CORTEX · HERALD · NEXUS
Operations · Hiring pipeline
Runs the top of the hiring funnel — sourcing, screening questions, scheduling — with humans deciding on people.
Built on NOVA · ARIA · NEXUS
Operations · Revenue admin
Chases what is owed, reconciles what came in and flags what does not match — proposing, never paying.
Built on HERALD · CORTEX · NEXUS
Marketing · Channel performance
Connects spend to pipeline and revenue, and explains which channel earned the next pound.
Built on SENTINEL · CORTEX · NEXUS
Marketing · Search and AI discovery
Works technical health, entity authority and AI-search visibility, measured in pipeline rather than rankings.
Built on CORTEX · NEXUS
Marketing · Production and testing
Produces on-brand content against approved claims, then learns from what actually converted.
Built on HERALD · CORTEX · NEXUS
No agents shortlisted yet. Add the ones you would want running first and bring the list to a call.
The intent is to let specialists build agents on the same runtime. The programme is not open and no third-party agents are listed — this is how it will work when it is.
Step 1
Partners define an agent the same way we do: inputs, permitted actions, tools, approval rules, guardrails and the limits it must refuse to cross.
Step 2
Every partner agent is reviewed against the same governance framework as ours: risk class, permissions, human approval points, audit logging and a documented kill switch.
Step 3
A partner agent never gets its own back door. It runs on the connections the customer authorised, scoped to the permissions they set, logged in the same activity record.
Step 4
Listings carry a version, a changelog and a named maintainer. A customer can revoke a partner agent's permissions at any time without touching the rest of their system.
There are no marketplace prices on this page. Scope, connected systems, approval rules and volume differ enough per company that a published number would be misleading.
The expensive part is connecting and governing your systems. That work is done once. The second and third agent inherit it, which is where the economics of a platform differ from buying three tools.
The commercial terms for partner-built agents have not been finalised or published. When they are, they will be stated here in full rather than negotiated case by case.
Connections are authorised by you and revocable by you. Leaving means revoking access and exporting your records — not a migration project designed to be painful.
The governance every marketplace agent inherits is set out in the Responsible AI Centre, and every action they take is recorded in Agent Observability.
Bring the shortlist. We will map it to the systems you already run, agree the approval rules, and quote the deployment properly rather than from a price list.
We use a single first-party cookie to remember your currency and consent choice. Page-view analytics are sent to our own servers — no third-party trackers, no profiling. See our Privacy Policy.