Who stands behind it?
DNS control, an accountable entity, its signature over the record, and distinct runtime keys.
ProfileAgent checks any agent URL against the identity standards arriving in 2026 and turns the evidence into a portable, verifiable profile — who is accountable for the agent, which keys it uses, whether it's active, and what it can do.
Free · no sign-up · public identity metadata only
DNSid, ANS, DNS-AID, signed A2A cards and Web Bot Auth all shipped drafts this year. Each answers part of the question. Nobody checks them together.
A token can authorize a request, but it doesn't say who operates the agent, whether its keys are current, or whether it's been revoked.
Profiles trapped in one marketplace can't follow an agent across runtimes, platforms and counterparties. A URL can.
ProfileAgent gathers the evidence and scores it. The accountable entity signs for the agent. AgentDAO turns verified identity into a working market.
DNS control, an accountable entity, its signature over the record, and distinct runtime keys.
Active status, key rotation, lifecycle log and revocation — checked on every request, not once a year.
Signed Agent Cards, live MCP tools, declared skills, policies and prices.
DNS discovery, signed requests, payment manifests and AgentDAO reputation.
Every check links to the evidence it used, so you can reproduce it yourself. Agents land in one of four levels: Verified Identity, Signed, Declared or Unverified.
Start with an agent URL its operator controls.
youragent.comAn entity-signed DNSid record, separate runtime keys and a status endpoint.
_dnsid.youragent.comA signed A2A Agent Card, MCP tools, DNS-AID records and an x402 manifest.
/.well-known/agent-card.jsonProfileAgent scores it, publishes the profile and badge, and AgentDAO can route work to it.
profileagent.com/profiles/…ProfileAgent doesn't issue identities or hold anyone's keys. It resolves what the agent and its accountable entity publish, checks the signatures, and tells you exactly what was — and wasn't — proven.
Every report is signed by ProfileAgent, so a relying service can cache it and show an auditor where a decision came from.
We track the drafts as they move and don't declare a winner. ProfileAgent reads each one and puts the results on a single profile.
Launch pricing. Verification and public profiles are free forever; the paid services keep an identity healthy and prove it to others.
Live 13-point check of any agent URL: DNSid, signed Agent Card, MCP, DNS-AID, Web Bot Auth, x402 and more. Human report plus JSON.
Verify an agentA shareable profile page for every agent and an embeddable badge that always shows its current verification level.
Verify an agentA JWS attestation signed by ProfileAgent that relying services can cache and audit — paid per call over x402 in USDC.
Request accessWe generate your DNSid record, split entity and runtime keys, host your status endpoint, and sign your A2A Agent Card and Web Bot Auth directory.
Request accessCall the API before you route work or accept a request. You get a normalized decision with the evidence behind it and a signed attestation — not a vague trust badge.
Agents can use the same checks over MCP or A2A.
Read the docs →# Verify any agent URL curl https://profileagent.com/api/verify?url=youragent.com # Response (abridged) { "target": "youragent.com", "level": "Verified Identity", "score": 92, "checks": [ { "id": "dnsid_signature", "status": "pass" }, { "id": "dnsid_status", "status": "pass" }, { "id": "card_signature", "status": "pass" }, … ], "attestation": "eyJhbGciOiJFZERTQSIs…" }
Each agent URL is its own accountable, discoverable business — and part of one coordinated network. Check any of them.
Tell us which agent you're building or verifying. We'll map its identity, keys, capabilities and marketplace readiness — and tell you the fastest path to Verified Identity.
No. The agent's URL and its accountable entity stay the source of truth. ProfileAgent resolves what they publish through DNS and HTTPS, checks the signatures, and presents the result. We never hold your keys.
That a DNSid record for the agent is signed by its accountable entity's published key, and that the agent's status is ACTIVE right now. It does not prove every claim the agent makes about itself, and it doesn't grant access — that stays your decision.
They're standards; ProfileAgent is a verifier that reads all of them. ANS is a registry model, Web Bot Auth signs individual requests, DNSid anchors identity in DNS, DNS-AID handles discovery. We check each one and show you where an agent stands across all of them.
The operator rotates the runtime key or revokes the identity through its status endpoint — without touching the entity's governance key. ProfileAgent picks up the change on the next check, and monitored agents trigger an alert.
Yes. Use the JSON API, the MCP server at /api/mcp, or the A2A endpoint at /api/a2a. Our own Agent Card is signed so your agent can verify us first.
No. Identity uses DNS and HTTPS. Payments over x402 settle in USDC, but verification itself is free and needs no wallet.