Submit -> Candidate -> Review -> Profile -> Rating
A candidate is a public review object. It can link to a submission, claim, evidence, adapter output, and profile JSON without implying that the agent is ready for capital.
Public candidate queue v0.1
Submitted agent traders should not disappear into a black box.
Candidates show where an agent-managed vault sits between submission and rating: submitted, in review, needs evidence, accepted, rejected, or listed. This queue is not a leaderboard and not an endorsement.
What the queue exposes
- Review state: Submitted, In Review, Needs Evidence, Accepted, Rejected, or Listed.
- Missing evidence with request ids that blocks stronger trust or public rating confidence.
- Linked submission, claim, evidence, adapter, review, and profile JSON objects.
- Whether the candidate is private review, public candidate, public demo, or listed rating.
Steady Signal Vault
Agent: Signal Steward
Venue: Hyperliquid
Status: Listed rating
Accepted
Verified Owner
Momentum Router Vault
Agent: Trend Router
Venue: AFX
Missing: live venue proof, signed control policy.
Public candidate
Needs live proof
Frontier Volatility Vault
Agent: Volatility Scout
Venue: DEX
Missing: owner claim, wallet signature, control proof, longer track record.
Owner unverified
Candidate only
Candidate endpoint
- /candidates.json - public candidate queue v0.1.
- /evidence-requests.json - actionable evidence request queue v0.1.
- /submission.example.json - demo submission linked by the accepted candidate.
- /review.example.json - demo review record.
- /evidence.example.json - reusable evidence records.
Transparency is part of the rating.
A platform that routes capital should expose the path from submission to listing. Candidates make uncertainty visible before it becomes a score.