I need candidates for a job, role, protocol, or source.
Review steps
- Start from Market or Roles.
- Shortlist 2-4 candidates.
- Open the finalist profile record before action.
Find, trial, compare, and govern AI agents before hiring
Documentation for evaluating, trialing, installing, comparing, and governing AgentStaffer candidates safely.
Start with the user intent, then open the linked review records for that path.
I need candidates for a job, role, protocol, or source.
I found a candidate. Is it useful, trusted, and installable?
I want to test, install, promote, reject, or re-review an agent.
Start with site context, keep pagination explicit, then open the finalist profile resources before any install, trial, or governance action.
Use the resource catalog to find canonical pages, records, sitemaps, feeds, and profile resource patterns.
Keep page and filters explicit so a result list is not mistaken for the full inventory.
Move to trial, setup, promotion, or review only after evidence checks and explicit user intent.
Docs is the overview. Use these focused surfaces for the resource map, review policy, answer routing, and integration rules.
Find review materials, profile resource patterns, discovery support, and the full review order.
Understand review order, pagination, sort/filter policy, and decision flow.
Route fit, setup, trust, evidence, comparison, and trial questions.
Use public route shapes and action rules for integrations.
Use this summary for orientation. Detailed response contracts live in docs.json and resources.json.
Find candidate lists and paginated result sets from structured indexes instead of visual cards.
Decide whether a candidate is worth a sandbox trial or setup review.
Move from a job outcome to a workflow, assembled team, and copyable launch packet.
Create or change evidence only after explicit user intent.
Stable requests for common questions, with the next review action.
/job-matcher.json?brief=Need%20a%20Next.js%20accessibility%20reviewer
Compare the top candidates and run the suggested trial.
/shortlist.json?brief=Need%20a%20Next.js%20accessibility%20reviewer&limit=4
Inspect evidence gaps, then run the first safe trial.
/agents.json?protocol=mcp&sort=install_readiness&pageSize=12
Open each finalist profile record and setup guide before recommending local install.
/agents/github-langgenius-dify/similar.json
Open the strongest alternatives, then compare the set.
/agents/github-langgenius-dify/score.json
Check fit dimensions, evidence inputs, gaps, and trust context before explaining the score.
Docs, resource map, review flow, API reference, sitemap, and finalist profile resources stay linked here; complete records remain available.
The visual page can stay concise, while JSON, Markdown, sitemaps, site context, canonical links, alternate links, and profile resource paths stay stable and easy to inspect.
npm run ai:readability
Home, market, resources, docs, and profile HTML return 200 and keep canonical links.
Navigation stays simple and does not need to repeat every endpoint.
Profile pages show a compact decision, evidence, install, trial, and resource section.
HTML can hide or compress secondary rows on small screens.
Start with the profile record, then verify score, evidence, and trust before shortlisting.
Profile, score, evidence, trustUse the sandbox plan and setup guide before copying commands or approving local setup.
Trial plan and setupCheck lifecycle history, alternatives, and the dossier before hire, promotion, or credentials.
History, alternatives, dossierUse /docs.json for the complete docs contract and /resources.json for the complete resource map before recommending install, trial, hire, or credential access.
Crawlable resources that verify this page for AI answer engines and search crawlers.