App
community.lexicon.app
Self-published app profiles and community listings: how apps declare what they are and which lexicons they speak.
A working group that stewards a shared namespace for AT Protocol schemas: built in the open, governed collectively, and free for anyone to use.
01 · About
Lexicon Community is a volunteer-run working group that creates and maintains community AT Protocol Lexicons.
Lexicons
are the schema definitions that give AT Protocol records their
shape: they describe the types, methods, and constraints
that applications share across the network. Most lexicons today
live under vendor-controlled namespaces like
app.bsky.*. Lexicon Community offers a neutral home:
schemas that no single company owns, governed by an open
Technical Steering Committee and published under the MIT license.
Thursday, August 6, 2026 at 1:00 PM ET, open to the community: RSVP on atmo.rsvp or read the announcement.
02 · Schemas
These namespaces are developed openly in the lexicons repository. The full directory of published schemas, with documentation for each, lives at Lexicons.
community.lexicon.app
Self-published app profiles and community listings: how apps declare what they are and which lexicons they speak.
community.lexicon.bookmarks
Save and retrieve bookmarks: a portable, protocol-native alternative to siloed read-later services.
community.lexicon.calendar
Events and RSVPs for the open social web: a shared schema for everything from meetups to conferences.
community.lexicon.interaction
Generic interaction primitives that apps can share, starting with a reusable like record.
community.lexicon.location
Represent places with multiple encodings: street addresses, geo coordinates, H3 cells, and Foursquare POIs.
community.lexicon.payments
Payment-adjacent primitives for open social apps, starting with a Web Monetization declaration.
community.lexicon.preference
User-declared preferences, starting with how AI may use your public data.
community.lexicon.…
Have an idea for a new namespace? Working groups are self-formed: anyone can start one. Bring the idea to the forum, along with the application that would use it.
03 · Contribute
Ideas start on the forum. Lead with the application, SDK, or tool you want to interoperate with. Working groups are self-formed, changes land as pull requests, and the Technical Steering Committee approves them once the work is done.
The full path, end to end, is written down in the design guide on the blog.