Search Lexicons

Find lexicons by what their descriptions, definitions and fields say.

Only show
  1. container image manifest following OCI specification, stored in ATProto Optional reference to another manifest (for attestations, signatures) OCI schema version (typically 2) Repository name (e.g., 'myapp'). Scoped to user's DID. OCI media type Referenced

    published by @did:web:lexicon.atcr.io
  2. Shared definitions for the graph namespace (follows

    published by @kich.io
  3. favourite of another account's collection, so the viewer can revisit it and follow what gets added. Strong reference to the collection record being favourited. Indexed by URI; the CID is informational

    published by @currents.is
  4. personal board where followers can read and post notes

    published by @bulletin.my
  5. List collection rules owned by the authenticated user.

    published by @lexicon.atpix.net
  6. Update an existing collection rule.

    published by @lexicon.atpix.net
  7. A single photo in a grow's gallery. Modeled as its own record (rather than blobs embedded in entries) so galleries can grow without bloating other records and so each photo carries its own caption, ordering, and capture date. A photo attaches to a plant (the usual case — per-plant galleries) and/or to the grow (group/room shots, the cover), and may optionally link to the `org.cannadb.growEntry` it documents. The image blob lives on the publishing PDS; the record carries the blob ref plus metadat

    published by @cannadb.org
  8. straitforward translation from OGC Features and Geometries Json (https://docs.ogc.org/DRAFTS/21-045r1.html) to ATProto lexicon, following the draft lexicon styleguide. The most distinct change is the representation of coordinates as integers (#float64) defined

    published by @willem.dobs.nl
  9. resolver document for multi-context design tokens (theming, breakpoints, accessibility modes). Follows the DTCG Resolver 2025.10 specification. Describes how token sets and contextual modifiers combine to produce resolved token values for a given input. Root

    published by @bomberstudios.com
  10. A record containing a collection of design tokens in DTCG 2025.10 format. The record has typed metadata fields (name, description, createdAt) alongside the token tree. Token/group keys sit at the same level as metadata; atproto ignores unexpected fields, so the token tree passes through without schema-level validation.

    published by @bomberstudios.com
  11. Record containing an agent skill published over ATProto. Follows the Agent Skills open standard (agentskills.io). Semantic version string (e.g. 1.0.0). Author-declared. The complete SKILL.md file content — frontmatter and body, verbatim. This is the source

    published by @solpbc.org
  12. page.cavu.authReader permission-set
    published by @cavu.page
  13. Wire format for messages a client sends server-bound over the same WebSocket opened by `page.corvus.subscribeOps`. Atproto's `subscription` lexicon type is server-push only — every server→client frame is defined under `page.corvus.subscribeOps`. The client→server side of the duplex socket is described here as a separate frame union. Clients dispatch on each message's `$type` discriminator (e.g. `page.corvus.backchannelFrame#op`). **Multi-block.** A single WebSocket connection authenticates one

    published by @corvus.page
  14. this query does NOT walk graph relations. Callers fetch ops for the blocks they care about and follow refs explicitly with subse Maximum number of ops to return in this page. The dids

    published by @corvus.page
  15. nobody is signed up for a challenge they didn't join - and it's public, like a follow, so a challenge can show who's taking part before anyone has entered. Entering a prompt joins

    published by @2bit.pics
  16. membership. Together, the two records form a bilateral proof of membership — similar to how AT Protocol follows work. AT URI of the Sphere record (site.exosphere.sphere.profile) on the owner

    published by @exosphere.site
  17. site.mochott.authFull permission-set

    Permission set granting full access to mochott blog features. Referenced as the OAuth scope include:site.mochott.authFull.

    published by @tokimeki.blue
  18. subscription record in the social graph. Represents a user following a publication. AT URI of the publication profile record being subscribed to. Timestamp when the subscription was created

    published by @tokimeki.blue
  19. list of suggested actors. Expected use is discovery of accounts to follow during new account onboarding. Snowflake for this recommendation, use when submitting recommendation events

    published by @sprk.so
  20. absent. A third line naming where the title sits, such as the album. Client settings that follow the user across devices. Every field is optional and a client applies its own default for an absent … link to another site asks for confirmation first. Options for voice channels. The color theme. system follows the operating system. Whether the channel list shows the latest message under each channel name. Whether a link

    published by @colibri.social

Lexicon Garden

@