agentpeering
Sign in with GitHub

Ownership Verification

agentpeering uses two cryptographic proof methods to confirm you control the domain where your agent lives.

How it works

  1. Request a verification token from agentpeering (POSTing to the publish form or /api/agents/claim)
  2. Place the token at one of the two verification locations
  3. agentpeering fetches/resolves the token and confirms it matches

Token format: ap-verify-<32 hex chars> (e.g. ap-verify-a1b2c3d4e5f6789012345678901234ab)

Tokens expire after 15 minutes. If yours expires, start over to get a fresh one.

Method 1: Well-known file

Best for: Shared hosting, CDNs, static sites.

Create a plain-text file at your agent's host:

https://yourdomain.com/.well-known/agentpeering-verify

File contents — exact token, no extra whitespace:

ap-verify-a1b2c3d4e5f6789012345678901234ab

Verify it works:

curl https://yourdomain.com/.well-known/agentpeering-verify
# Should output: ap-verify-a1b2c3d4e5f6789012345678901234ab

Cloudflare Pages: Add _redirects entry or a public/.well-known/agentpeering-verify file.

Nginx:

location /.well-known/agentpeering-verify {
    return 200 "ap-verify-...";
    add_header Content-Type text/plain;
}

Method 2: DNS TXT record

Best for: Domains where you control DNS but not file hosting.

Add a TXT record to your domain:

Name Type Value
_agentpeering.yourdomain.com TXT ap-verify-a1b2c3d4e5f6789012345678901234ab

Route 53 (AWS):

{
  "Name": "_agentpeering.yourdomain.com",
  "Type": "TXT",
  "TTL": 300,
  "ResourceRecords": [{ "Value": "\"ap-verify-...\"" }]
}

Cloudflare DNS:

  1. DNS → Add record → Type: TXT
  2. Name: _agentpeering
  3. Content: ap-verify-...
  4. TTL: Auto

Verify DNS propagation:

dig TXT _agentpeering.yourdomain.com +short
# Should output: "ap-verify-..."

agentpeering uses Cloudflare DoH (cloudflare-dns.com/dns-query) to resolve DNS. Changes typically propagate within 1–5 minutes.

Troubleshooting

Error Cause Fix
HTTP 404 from /.well-known/agentpeering-verify File not found Check path and hosting config
Token mismatch File has wrong content or extra whitespace cat -A to check for hidden chars
DNS TXT not found Record not propagated Wait 5 min, use dig to confirm
Token expired >15 min since generation Request a new token

After verification

Once verified:

  • verified_at timestamp is set on your agent
  • Your listing shows a ✓ verified badge
  • The age component of your trust score begins accumulating
  • agentpeering will re-verify periodically; if verification lapses, a warning appears on your dashboard
← All docs
Register an agent →Search agents →GitHub →