Registry overview
Find canonical trust records for Agents, Skills, Creators and provider identities.
The Clawdbase registry combines authenticated Pages with discoverable public entries. Search is global: the same registry search is available from the public site, Console and documentation header.
What a Page represents
A Page is a canonical record for one subject. Its URL, source identity, Trust and Confidence values, verification facts and scoring timestamps should all refer to the same record.
Authenticated Pages show control verified through the relevant provider. Discovered entries can still be browsed, but must not be presented as owner-verified.
Canonical routes
| Type | Route shape | Canonical anchor |
|---|---|---|
| Agent | /a/{owner}/{repo} or /a/id/{id} | Repository or internal ID |
| Skill | /s/{owner}/{repo} or /s/id/{id} | Repository or internal ID |
| Creator | /c/{handle} | Resolved creator identity |
| X account | /x/{handle} | Immutable X provider ID in storage |
| Telegram | /tg-account/{handle} | Telegram canonical identifier in storage |
The human-readable URL may contain a handle. Ownership and deduplication must still use the immutable provider identifier stored by the backend.
Registered and discovered records
The registry combines records that have different provenance. A registered Page has a provider-native ownership path and canonical registration record. A discovered record comes from indexed public sources and may not yet have an ownership relationship. The source filter exposes that distinction; it must never be hidden behind the visual score color.
Browse a Page safely
Search with enough context
Use the owner, repository, handle or display name. Select a Page type when the same text can refer to several kinds of entity.
Confirm canonical identity
Inspect the route, provider, source and verification state. Human-readable handles can change, while immutable provider IDs remain the canonical match key.
Read scores and freshness
Trust and Confidence come from the Page's authoritative score source. Read the status and timestamp before using them in a decision.
Follow context
For Agents and Skills, open the Creator or lineage relationship. For communication identities, confirm that the account is context for the intended artifact rather than evidence about code safety.
Registry invariants
- Search results, Console cards and public Pages resolve the same canonical record.
- Duplicate provider identities are merged by immutable provider ID, not by display text.
- A Page can remain publicly discoverable even when no owner is signed in.
- Owner-editable presentation never overwrites source identifiers, verification or scores.
- Loading and unscored states preserve layout and do not contain fabricated numbers.
Use Search and filters for the query contract and Registry card anatomy for every visible card field.