Docs Retrieve safely Next best action: Start with site context or API reference
Developer docs

Documentation for hiring agents safely

Documentation for evaluating, trialing, installing, comparing, and governing AgentStaffer candidates safely.

DocsRead overviewA reviewer or developer needs the overview, contracts, and safety rules.usage paths / schema overview / API handoffResourcesResource mapA reviewer or integration needs the resource catalog and profile resource patterns.resource families / canonical links / profile resource filesAnswersMatch a questionA reviewer needs to match a user question to the right evidence source.question templates / required checks / answer guardrailsReview GuidePlan review routeA reviewer or integration is ready to plan search, compare, trial, install, or governance retrieval.read/action boundary / pagination rules / decision flow

Choose your path

Start with the user intent, then open the linked review records for that path.

Review flow
Trial and govern Run trial, install, or govern

I want to test, install, promote, reject, or re-review an agent.

Review steps
  • Start with sandbox-first tasks.
  • Use setup guidance only after trust and trial checks.
  • Use promotion, review, and re-review queues for lifecycle decisions.

Safe review sequence

Start with site context, keep pagination explicit, then open the finalist profile resources before any install, trial, or governance action.

Open review flow
1
Orient Site context

Read site context and review priorities before broad discovery.

2
Discover resources Resource map

Use the resource catalog to find canonical pages, records, sitemaps, feeds, and profile resource patterns.

3
Search with pagination Paginated inventory

Keep page and filters explicit so a result list is not mistaken for the full inventory.

Show 2 governance stepsTrial, setup, and lifecycle checks stay folded for scanning; the complete sequence remains available as structured data.
4
Read finalists Finalist profile

Open the complete profile resources before recommending action.

5
Act only after review Trial and governance

Move to trial, setup, promotion, or review only after evidence checks and explicit user intent.

Where details live

Docs is the overview. Use these focused surfaces for the resource map, review policy, answer routing, and integration rules.

Resource map
Review mapResource Map

Find review materials, profile resource patterns, discovery support, and the full review order.

Human review surface
Review policyReview Strategy

Understand review order, pagination, sort/filter policy, and decision flow.

Human review surface
Answer routingAnswer Guide

Route fit, setup, trust, evidence, comparison, and trial questions.

Human review surface
Integration guideIntegration Guide

Use public route shapes and action rules for integrations.

Structured integration record
Reference detailsSafety rules, schema overview, and example queries remain available here, while the Docs record stays the canonical complete contract.
  • Open the profile resources before trusting a visual summary.
  • Use the shortlist when a user gives a job brief and needs a shareable candidate packet.
  • Check alternatives before deciding one profile is the strongest fit.
  • Use score, evidence, and trust records together when explaining recommendation quality.
  • Use the evidence ledger before claiming reviews, trials, reputation, or missing evidence.

Schema overview

Use this summary for orientation. Detailed response contracts live in docs.json and resources.json.

Docs record
inventory Inventory indexes

Find candidate lists and paginated result sets from structured indexes instead of visual cards.

/agents.json/skills.json/mcp.json/roles/{id}.json
pagination.nextPageUrlprofileUrlurls.profileJsontrustLevelinstallReadiness
profile-package Profile resources

Decide whether a candidate is worth a sandbox trial or setup review.

/agents/{slug}/profile.json/agents/{slug}/score.json/agents/{slug}/evidence.json/agents/{slug}/trust.json/agents/{slug}/trial.json/agents/{slug}/install.json
agentSummaryrecommendationScoreevidenceSummarysecurityReviewsafeFirstTask
workflow Workflow and teams

Move from a job outcome to a workflow, assembled team, and copyable launch packet.

/playbooks.json/teams.json/team-launch-packets.json
rolesteamRunJsonlaunchPacketJsonpreflightGatespromotionPolicy
actions Action endpoints

Create or change evidence only after explicit user intent.

/api/actions/submit-listing/api/actions/claim-listing/api/actions/run-trial
methodrequiredFieldsmoderationPolicyreviewGatesstatus

Example review queries

Stable requests for common questions, with the next review action.

Which agent should I try for a Next.js accessibility review? /job-matcher.json?brief=Need%20a%20Next.js%20accessibility%20reviewer

Compare the top candidates and run the suggested trial.

Create a shareable shortlist for this job brief. /shortlist.json?brief=Need%20a%20Next.js%20accessibility%20reviewer&limit=4

Inspect evidence gaps, then run the first safe trial.

Show MCP-ready candidates that are safer to install. /agents.json?protocol=mcp&sort=install_readiness&pageSize=12

Open each finalist profile record and setup guide before recommending local install.

What are similar alternatives to this agent? /agents/github-langgenius-dify/similar.json

Open the strongest alternatives, then compare the set.

Why did this agent receive its recommended score? /agents/github-langgenius-dify/score.json

Check fit dimensions, evidence inputs, gaps, and trust context before explaining the score.

Review support

Supporting files

Docs, resource map, review flow, API reference, sitemap, and finalist profile resources stay linked here; complete records remain available.

Open Site context
Supporting review linksLinks, review order, and page-specific notes remain available here.
Review checks

Polish the UI without weakening retrieval

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.

Visible checks4 checks2 more in Docs record
Docs recordDocs recordCanonical docs record
Resource mapResource mapComplete review file map
Profile resources9 filesDecision basis, trial readiness, governance trail
Reliability detailOpen the full reliability checks.
npm run ai:readability
Status and canonical pages

Home, market, resources, docs, and profile HTML return 200 and keep canonical links.

Global data entrypoints

Navigation stays simple and does not need to repeat every endpoint.

Profile resources

Profile pages show a compact decision, evidence, install, trial, and resource section.

Embedded structured contracts

HTML can hide or compress secondary rows on small screens.

01Decision basis

Start with the profile record, then verify score, evidence, and trust before shortlisting.

Profile, score, evidence, trust
02Trial readiness

Use the sandbox plan and setup guide before copying commands or approving local setup.

Trial plan and setup
03Governance trail

Check lifecycle history, alternatives, and the dossier before hire, promotion, or credentials.

History, alternatives, dossier
Docs review flow
  1. 01Site contextShared review rules
  2. 02Docs recordOpen the focused review record
  3. 03Agent inventoryBrowse the matching inventory
  4. 04Profile resourcesEvidence, setup, trust, trial, and history files

Use /docs.json for the complete docs contract and /resources.json for the complete resource map before recommending install, trial, hire, or credential access.

Review route: OpenAI review tools can start with openai.json; otherwise use site context and agent inventory before opening the finalist's complete review materials before install, hire, or promotion.

Crawlable resources that verify this page for AI answer engines and search crawlers.