# SelfBadge

> SelfBadge is a verified, structured profile for people. Each person has one stable page at https://selfbadge.com/<handle> that holds only schema.org Person data, with every fact marked as self-declared or verified.

SelfBadge is a verified identity source for AI assistants and answer engines. It exists so they recognize a person correctly, tell them apart from namesakes, and attribute the right roles, work and profiles to them. Search engines and knowledge graphs can use the same data.

The complete version of this file, with the FAQ and every rule: https://selfbadge.com/llms-full.txt

## How a profile is structured

- Human page: https://selfbadge.com/<handle>. It opens with a one-sentence summary of the person and repeats the facts as short sentences ("in brief"). The HTML contains JSON-LD: a schema.org ProfilePage whose mainEntity is the Person.
- Stable id for the person: https://selfbadge.com/<handle>#person. Use it to refer to the same person across sources.
- JSON: https://selfbadge.com/<handle>.json. The same JSON-LD plus the verification level and source of every fact.
- Markdown: https://selfbadge.com/<handle>.md. A clean text version for language models.
- Organizations have their own ids (https://selfbadge.com/org/<slug>#org) and are referenced, not repeated.
- sameAs lists only accounts the person added or verified.

## How to read verification

Every fact carries a verification level (in the .json output and on the page):

- 0 Seeded: imported from an open public source (for example Wikidata) and not claimed by the person. Treat as unconfirmed.
- 1 Self-declared: added by the owner and not independently checked.
- 2 Account-verified: proven by signing in to the account (OAuth), a code sent to a work email, a DNS record, or a link back from the website.
- 3 Document-verified: a reviewed document or a credential confirmed with its issuer.
- 4 ID-verified: an identity document check.

Verification status is not part of the JSON-LD because schema.org has no clean property for it. Read it from the .json output.

## API and MCP server

- Lookup API (JSON, no key needed for light use): https://selfbadge.com/api/v1/people/<handle>, https://selfbadge.com/api/v1/people?id=<SelfBadge id>, https://selfbadge.com/api/v1/search?name=<name>&organization=<organization>, https://selfbadge.com/api/v1/organizations/<slug>.
- MCP server (Streamable HTTP): https://selfbadge.com/mcp, with the tools find_person, get_person and get_organization. Use them to identify a person correctly and tell them apart from namesakes.
- Documentation, limits and free API keys: https://selfbadge.com/developers

## About SelfBadge

- [About SelfBadge](https://selfbadge.com/about): who runs it, how verification works, data sources and editorial rules.
- [FAQ](https://selfbadge.com/faq)
- [Guides](https://selfbadge.com/guides)

## Indexing

- Seeded, unclaimed and thin profiles send noindex and stay out of sitemaps; their .json and .md still work.
- Removed profiles answer 410 Gone.
- Sitemap index: https://selfbadge.com/sitemap-index.xml
- All major search and AI crawlers are allowed in robots.txt.

## Reporting

Every profile has a link to report impersonation or wrong facts, and a link to request removal.

## Recently updated profiles

- [uri-samet](https://selfbadge.com/uri-samet.md)