Skip to main content
Claim a published tool from its public registry page by proving that your organization controls the tool’s website or docs domain. After verification, UseAgents transfers the tool to your organization and can also offer other unclaimed tools on the same verified domain.

Prerequisites

  • A UseAgents account
  • A signed-in session
  • Admin access to the organization that should own the tool
  • A tool that shows the Claim this tool button on its public page
  • Access to either:
    • the tool website’s /.well-known/ path, or
    • the homepage HTML so you can add a meta tag

Before you start

The claim flow is available only when all of these are true:
  • The tool is already published
  • The tool is still owned by the UseAgents holding organization
  • The tool has a valid website URL or docs URL that can be used for verification
If the tool is already owned by another organization, unpublished, or missing a claimable URL, you cannot start a claim from the UI.

Claim a tool

  1. Open the tool’s public page in the registry.
  2. Click Claim this tool.
  3. Sign in if prompted.
  4. Select the organization that should own the tool.
  5. Click Start website verification.
  6. Copy the verification instructions shown on the claim page.
  7. Prove ownership using one of these methods:
MethodWhat to add
Well-known fileCreate https://<your-host>/.well-known/useagents-verification.txt and set the file contents to the exact token shown in the UI
Meta tagAdd <meta name="useagents-verification" content="<token>" /> to the homepage for the verified host
  1. Return to the claim page and click Verify website ownership.
  2. After verification succeeds, click Complete claim.
The tool is then transferred to the selected organization.

What the verification checks

UseAgents verifies ownership against the tool’s website URL first. If no website URL is present, it uses the docs URL. During verification, UseAgents:
  • Checks the expected host over HTTPS in production
  • Follows a small number of redirects
  • Accepts either the well-known file or the homepage meta tag
  • Requires the token value to match exactly
If your organization has already verified the same domain before, UseAgents can reuse that proof and move the claim request directly into a verified state. On shared hosts such as github.io or vercel.app, the previously verified host must also match exactly. Claim requests expire after 30 minutes. If the request expires, start a new claim and use the new token.

Claim additional tools on the same domain

After the first tool is claimed, UseAgents may show additional unclaimed tools that match the same verified domain.
  1. Review the suggested tools.
  2. Select the tools you want to transfer.
  3. Click Claim selected.
This is useful when multiple SDKs, integrations, or tool listings share the same verified website or docs domain.

Domain matching rules

Most claims match by registrable domain. For example, a verified docs.example.com claim can match other tools under example.com. Some shared hosts are stricter. For these hosts, UseAgents matches by exact host instead of the broader domain:
  • github.io
  • vercel.app
  • notion.site
  • readme.io
If your tool lives on one of these platforms, verify the exact host used by the tool listing.

Verify the result

After the claim completes:
  1. Open the tool in your organization.
  2. Confirm the tool now appears under the selected organization.
  3. Check the tool’s settings, metadata, and deployment history.
  4. If you claimed sibling tools, confirm those tools also moved successfully.

Troubleshooting

  • You do not see the Claim this tool button: The tool may already be claimed, unpublished, or missing a valid website/docs URL for verification.
  • Verify website ownership fails: Make sure the token matches exactly, the file or meta tag is on the expected host, and the page is publicly reachable over HTTPS.
  • The claim expired: Start the flow again. Each new claim request generates a new token and a new 30-minute window.
  • Complete claim is disabled: Verification must succeed before you can finish the transfer.
  • Expected sibling tools do not appear: Only unclaimed tools that match the verified domain or exact shared host are offered.