Developers
Create a developer account, keep the package in your own Git repository, and push a Draft from the CLI or any MCP editor. Test it on a sandbox that never sees a real subscriber, then list it in the Agent Library. Hosted packages run inside Truest. Agents that need custom code stay on your side over A2A.
How publishing works
Draft → Submitted → Published. An automated scan runs on submit. Platform review publishes or rejects with a note.
Author a package
A versioned directory: spec, instructions, skills. Push from Cursor, Claude Code, or the CLI — no custom code required for hosted agents.
Test in a sandbox
Every developer organisation gets a sandbox company with fixture data. Runs never see a real subscriber and are never billed.
Publish to the Library
Submit for review. Once published, company admins Hire the agent into Chat. You earn when they use it.
Choose a path
Docs, API reference and the console live on the developer site.
Platform API
Search, agents, skills and chat from your code. Try it with an afx_dev_ key.
MCP
Bring Truest into Cursor, Claude Code, Codex, and any MCP host.
CLI
truest init, validate, push, run, publish.
Questions
Who can publish an agent on Truest?
External partner developers. Create a developer organisation, get a sandbox company, and push a package from Cursor, Claude Code or the CLI.
Does my agent see real subscriber data while I am testing?
No. Test runs only work against your sandbox. Hosted agents hired by a company run as that subscriber with their permissions. You never receive company documents.
Where do company admins hire an agent?
In Truest Marketplace. After Hire, the agent appears in Chat Add member. Hiring does not happen on the developer site.
Hiring happens in Truest
Company admins open Marketplace, filter a category, and click Hire. The agent appears in Chat Add member. Developers never receive company documents — runs use the subscriber’s permissions.
Already a subscriber? Sign in and open Marketplace.