Submit / Claim Add or verify Next best action: Submit for review

Owner verification

Claim an existing profile

Owner verification protocol for maintainers who want to claim an existing AgentStaffer profile, improve install metadata, and attach official evidence without bypassing safety review.

Claim profile — free Apply for Verified Launch Submit new listing

Claim request

Verify maintainer control for an existing profile, then attach official metadata without changing independent safety gates.

Required to send: one profile identifier, claimant name, and a public proof URL.

Profile

Point AgentStaffer to the existing profile or source that the claim should attach to.

Listing ID One identifier required Proof type Required Profile URL One identifier required Source URL One identifier required

Use the shortest identifier you know. A listing ID, AgentStaffer profile URL, or public source URL is enough.

Claimant

Identify the maintainer, project, or organization requesting verified ownership.

Claimant name Required Email Optional Organization Optional

Proof

Use a public URL controlled by the maintainer. The verification token must be published there after submission.

Proof URL Required · public http(s) Notes Optional

Claims verify maintainership only. They do not bypass install review, security review, or sandbox trial gates.

API docs

Commercial path

Need evaluation and launch support?

Verified Launch is the single paid package. Claiming stays free; eligibility review comes before checkout, and payment never buys a passing result.

Standard sandbox trial and public report
Verified badge only after passing review
30-day category visibility and outcome data

Apply for Verified Launch Review package

Verification optionsProof methods maintainers can publish

Repository verification file

Add a public file named .well-known/agentstaffer.txt or AGENTSTAFFER.md containing agentstaffer-claim-token.

DNS TXT record

Add a TXT record containing agentstaffer-claim-token on a domain linked from the source project.

Website verification file

Publish agentstaffer-claim-token at /.well-known/agentstaffer.txt on the project website.

Package metadata

Add agentstaffer-claim-token to package metadata, README, or a release note controlled by the maintainer.

Signed release

Publish agentstaffer-claim-token in a signed release note, provenance statement, or maintainer-controlled release artifact.

Claim status lifecycleQueue states after claim creation

Created Owner: Claimant

The claim request exists and a verification token is issued.

Publish the token at the proof URL or source-controlled metadata.

Verification pending Owner: AgentStaffer reviewer

The proof URL, token placement, and connection to the profile source are checked.

Keep the proof public and update the request if the URL changes.

Verified owner Owner: AgentStaffer reviewer

Maintainer control is verified and official metadata can be attached to the profile.

Submit install guidance, source corrections, and trial suggestions for independent review.

Needs more proof Owner: Claimant

The proof does not clearly establish control of the source, package, or official domain.

Provide repository, DNS, website, package, or signed-release proof.

Rejected Owner: AgentStaffer reviewer

The claim cannot be tied to maintainer control or conflicts with public evidence.

Resolve the reason and submit a new claim with stronger proof.

Owner can correctOfficial metadata maintainers may improve

official website
repository URL
install instructions
package metadata
maintainer note
supported protocols
safe trial suggestions
correction request

Still independently reviewedTrust signals claimants cannot override

trust badge
recommended score
risk and safety posture
promotion status
published status
trial outcomes
community review weighting

Review gatesChecks before metadata is trusted

verify control of source
check install metadata
inspect securityReview
run or request sandbox trial
attach public evidence before promotion

Claim boundaryOwnership is not production approval

A claim verifies maintainer control or official attribution; it does not bypass independent review gates.
Owners can improve metadata, install guidance, source links, and correction notes, but safety, trial, promotion, and trust decisions remain independently reviewed.
A verified owner claim does not automatically assign a trust badge, shortlist, production recommendation, or published status.
Proof must stay public and source-controlled enough for future reviewers and automated checks to verify later.

API exampleCreate a claim through the action endpoint

curl -s -X POST 'https://agentstaffer.com/api/actions/claim-listing' -H 'content-type: application/json' --data '{"listingId":"github-langgenius-dify","profileUrl":"https://agentstaffer.com/agents/github-langgenius-dify","claimantName":"Project maintainer","claimantEmail":"maintainer@example.com","organization":"Example Project","proofType":"repository_file","proofUrl":"https://github.com/example/project/blob/main/AGENTSTAFFER.md","note":"We maintain this project and want to add verified install and trial guidance."}'

Claim contract

Claim verifies ownership, not production safety

A claim can improve attribution and official metadata. It does not automatically change trust, score, publication, shortlist, install approval, or promotion status.

After claim

Verification token

The claimant receives a token and must publish it in a public, source-controlled location tied to the profile.

Owner can edit

Attribution and metadata

Verified maintainers can correct source links, install notes, maintainer guidance, protocols, and safe trial suggestions.

Still independent

Trust and promotion

Safety posture, recommendation score, trust badge, trial outcomes, publication, and promotion remain independently reviewed.

Review support

Review links

The claim form stays focused; ownership rules and profile resources stay linked here.

Open Claim guide

Supporting review linksLinks, review order, and page-specific notes remain available here.

Claim guide Claim endpoint Verified Launch package Submission guide Review rubric OpenAPI Resource map Site context Sitemap Profile resources

Claim review path

01Site contextShared review rules
02Claim guideOpen the focused review record
03Profile pageOpen the candidate page
04Profile resourcesEvidence, setup, trust, trial, and history files

Use the links and review path below for ownership proof, independent review rules, and claimed profile resources before recommendation or install.

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.

AgentStaffer evidence resources

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