com.airplaneian
3
Narrow ›
-
com.airplaneian.contrail.temp.defs
defs
An airport, airfield, or landing site referenced by a flight record. Every field is optional, and absent means unknown or not applicable. The identifier fields come from different systems and a place may have any combination of them, so write each one the place actually has. A place with no published identifier is described by 'name' and 'geo' alone.
-
com.airplaneian.contrail.temp.flight
record
An assertion that a particular flight existed, rather than a personal log entry about the author. Only 'createdAt' is required. Every other field is optional, and absent means unknown or not applicable rather than empty or zero. The exception is 'relationship', where absent means no claim is being made. Records of the same flight written by different people are expected, so write the identifying fields consistently. Any kind of flying is in scope, and origin may equal destination.
-
com.airplaneian.contrail.temp.trip
record
An assertion that a set of flights belonged to one journey. Only 'createdAt' is required, and absent means unknown or not applicable. The reference points one way only, from trip to flight, and a trip references only flight records the author wrote.
com.atiproto
37
Narrow ›
-
com.atiproto.actions
defs
Workflow envelope shared between atiproto XRPC endpoints and the agent interpreter. The server emits an outboundWorkflow when it needs the agent to execute repo writes against the user's PDS; the agent runs the actions and calls back with an inboundWorkflow.
-
com.atiproto.authEnhanced
permission-set
-
com.atiproto.authGeneral
permission-set
-
com.atiproto.cart
record
A record representing a shopping cart for items/subscriptions
-
com.atiproto.item
record
A record representing a item given by one user to another
-
com.atiproto.payment.cart.clone
procedure
Clone an existing cart, creating new item and subscription records. Useful for reopening expired carts or repeating payments.
-
com.atiproto.payment.cart.create
procedure
Create a new empty cart
-
com.atiproto.payment.cart.get
query
Get a specific cart sent by the authenticated user, including resolved item and subscription records. One of `uri`, `itemUri`, or `subscriptionUri` is required.
-
com.atiproto.payment.cart.list
query
List carts created by the authenticated user.
-
com.atiproto.payment.cart.put
procedure
Update a cart. Only open carts can be updated.
-
com.atiproto.payment.item.create
procedure
Create a item on a DID or specific record. Creates or adds to a cart and returns a checkout URL.
-
com.atiproto.payment.item.get
query
Get a specific item sent by the authenticated user. Looks up by item record uri, subject (recipient) DID, or record uri. These are mutually exclusive and resolved in that order.
-
com.atiproto.payment.item.list
query
List items sent by the authenticated user
-
com.atiproto.payment.item.put
procedure
Update a pending item. Only pending items can be updated.
-
com.atiproto.payment.item.validate
query
Validate that the authenticated user (as the sender) has completed item payment(s). Looks up by itemUri (a specific item record), recordUri (sums all items for that record), or subject (recipient DID). These are mutually exclusive and resolved in that order.
-
com.atiproto.payment.list
query
List items and subscriptions for the authenticated user. Always returns items given by the user and subscriptions the user has created.
-
com.atiproto.payment.subscription.cancel
procedure
Cancel an active subscription
-
com.atiproto.payment.subscription.create
procedure
Create a subscription to a user. Returns a one-off cart with checkout URL.
-
com.atiproto.payment.subscription.get
query
Get a specific subscription sent by the authenticated user. Looks up by subscription record uri or subject (recipient) DID. These are mutually exclusive; uri takes precedence.
-
com.atiproto.payment.subscription.list
query
List subscriptions for the authenticated user
-
com.atiproto.payment.subscription.put
procedure
Update a pending subscription. Only pending subscriptions can be updated.
-
com.atiproto.payment.subscription.validate
query
Validate that the authenticated user (as the sender/subscriber) has an active, Stripe-verified subscription. Looks up by subscriptionUri (a specific subscription record) or subject (recipient DID). These are mutually exclusive; subscriptionUri takes precedence.
-
com.atiproto.profile
record
A record representing a user's tipping/subscription settings
-
com.atiproto.recipient.payment.cart.get
query
Get a cart that pays the authenticated user — a cart whose items target this user. Look up by cart URI, by a contained item record URI, or by a contained subscription record URI. One of `uri`, `itemUri`, or `subscriptionUri` is required.
-
com.atiproto.recipient.payment.cart.list
query
List carts whose items pay the authenticated user — i.e. carts targeting this user as a payment recipient. Read-only, no PDS writes.
-
com.atiproto.recipient.payment.item.get
query
Get a specific item received by the authenticated user (as the recipient/subject). Looks up by item record uri, sender DID, or record uri. These are mutually exclusive and resolved in that order.
-
com.atiproto.recipient.payment.item.list
query
List items received by the authenticated user (items where the authed user is the recipient/subject). Includes items marked private, which are only stored in atiproto's database.
-
com.atiproto.recipient.payment.item.validate
query
Validate that a sender has completed item payment(s) to the authenticated user (as the recipient/subject). Looks up by itemUri (a specific item record), recordUri (sums all items for that record), or sender (sender DID). These are mutually exclusive and resolved in that order.
-
com.atiproto.recipient.payment.subscription.get
query
Get a specific subscription received by the authenticated user (as the recipient/subject). Looks up by subscription record uri or sender DID. These are mutually exclusive; uri takes precedence.
-
com.atiproto.recipient.payment.subscription.list
query
List subscriptions received by the authenticated user (subscriptions where the authed user is the recipient/subject). Includes subscriptions marked private, which are only stored in atiproto's database.
-
com.atiproto.recipient.payment.subscription.validate
query
Validate that a sender has an active, Stripe-verified subscription to the authenticated user (as the recipient/subject). Looks up by subscriptionUri (a specific subscription record) or sender (subscriber DID). These are mutually exclusive; subscriptionUri takes precedence.
-
com.atiproto.recipient.profile.get
query
Get the authenticated user's profile settings. Returns defaults if no profile exists.
-
com.atiproto.recipient.profile.put
procedure
Create or update the authenticated user's profile settings
-
com.atiproto.repo.item.count
query
Count active (completed) items. If recordUri is provided, counts items for that record. If subject is provided, counts items received by that DID. If neither is provided, counts items sent by the authenticated user. Optionally filtered by a start/end datetime window. When the authenticated user is the subject/owner of the target, the response also includes the sum of amounts.
-
com.atiproto.repo.profile.get
query
Look up public profile information for any user
-
com.atiproto.repo.subscription.count
query
Count active subscriptions. If subject is provided, counts subscriptions received by that DID. If omitted, counts subscriptions the authenticated user has active (as the subscriber). Optionally filtered by a start/end datetime window (matching billingStartDate). When the authenticated user is the subject/owner of the target, the response also includes the sum of amounts.
-
com.atiproto.subscription
record
A record representing a subscription from one user to another
com.atproto
88
Narrow ›
-
com.atproto.admin.defs
defs
-
com.atproto.admin.deleteAccount
procedure
Delete a user account as an administrator.
-
com.atproto.admin.disableAccountInvites
procedure
Disable an account from receiving new invite codes, but does not invalidate existing codes.
-
com.atproto.admin.disableInviteCodes
procedure
Disable some set of codes and/or all codes associated with a set of users.
-
com.atproto.admin.enableAccountInvites
procedure
Re-enable an account's ability to receive invite codes.
-
com.atproto.admin.getAccountInfo
query
Get details about an account.
-
com.atproto.admin.getAccountInfos
query
Get details about some accounts.
-
com.atproto.admin.getInviteCodes
query
Get an admin view of invite codes.
-
com.atproto.admin.getSubjectStatus
query
Get the service-specific admin status of a subject (account, record, or blob).
-
com.atproto.admin.searchAccounts
query
Get list of accounts that matches your search query.
-
com.atproto.admin.sendEmail
procedure
Send email to a user's account email address.
-
com.atproto.admin.updateAccountEmail
procedure
Administrative action to update an account's email.
-
com.atproto.admin.updateAccountHandle
procedure
Administrative action to update an account's handle.
-
com.atproto.admin.updateAccountPassword
procedure
Update the password for a user account as an administrator.
-
com.atproto.admin.updateAccountSigningKey
procedure
Administrative action to update an account's signing key in their Did document.
-
com.atproto.admin.updateSubjectStatus
procedure
Update the service-specific admin status of a subject (account, record, or blob).
-
com.atproto.identity.defs
defs
-
com.atproto.identity.getRecommendedDidCredentials
query
Describe the credentials that should be included in the DID doc of an account that is migrating to this service.
-
com.atproto.identity.refreshIdentity
procedure
Request that the server re-resolve an identity (DID and handle). The server may ignore this request, or require authentication, depending on the role, implementation, and policy of the server.
-
com.atproto.identity.requestPlcOperationSignature
procedure
Request an email with a code to in order to request a signed PLC operation. Requires Auth.
-
com.atproto.identity.resolveDid
query
Resolves DID to DID document. Does not bi-directionally verify handle.
-
com.atproto.identity.resolveHandle
query
Resolves an atproto handle (hostname) to a DID. Does not necessarily bi-directionally verify against the the DID document.
-
com.atproto.identity.resolveIdentity
query
Resolves an identity (DID or Handle) to a full identity (DID document and verified handle).
-
com.atproto.identity.signPlcOperation
procedure
Signs a PLC operation to update some value(s) in the requesting DID's document.
-
com.atproto.identity.submitPlcOperation
procedure
Validates a PLC operation to ensure that it doesn't violate a service's constraints or get the identity into a bad state, then submits it to the PLC registry
-
com.atproto.identity.updateHandle
procedure
Updates the current account's handle. Verifies handle validity, and updates did:plc document if necessary. Implemented by PDS, and requires auth.
-
com.atproto.label.defs
defs
Metadata tag on an atproto resource (eg, repo or record).
-
com.atproto.label.queryLabels
query
Find labels relevant to the provided AT-URI patterns. Public endpoint for moderation services, though may return different or additional results with auth.
-
com.atproto.label.subscribeLabels
subscription
Subscribe to stream of labels (and negations). Public endpoint implemented by mod services. Uses same sequencing scheme as repo event stream.
-
com.atproto.lexicon.resolveLexicon
query
Resolves an atproto lexicon (NSID) to a schema.
-
com.atproto.lexicon.schema
record
Representation of Lexicon schemas themselves, when published as atproto records. Note that the schema language is not defined in Lexicon; this meta schema currently only includes a single version field ('lexicon'). See the atproto specifications for description of the other expected top-level fields ('id', 'defs', etc).
-
com.atproto.moderation.createReport
procedure
Submit a moderation report regarding an atproto account or record. Implemented by moderation services (with PDS proxying), and requires auth.
-
com.atproto.moderation.defs
defs
Appeal a previously taken moderation action
-
com.atproto.repo.applyWrites
procedure
Apply a batch transaction of repository creates, updates, and deletes. Requires auth, implemented by PDS.
-
com.atproto.repo.createRecord
procedure
Create a single new repository record. Requires auth, implemented by PDS.
-
com.atproto.repo.defs
defs
-
com.atproto.repo.deleteRecord
procedure
Delete a repository record, or ensure it doesn't exist. Requires auth, implemented by PDS.
-
com.atproto.repo.describeRepo
query
Get information about an account and repository, including the list of collections. Does not require auth.
-
com.atproto.repo.getRecord
query
Get a single record from a repository. Does not require auth.
-
com.atproto.repo.importRepo
procedure
Import a repo in the form of a CAR file. Requires Content-Length HTTP header to be set.
-
com.atproto.repo.listMissingBlobs
query
Returns a list of missing blobs for the requesting account. Intended to be used in the account migration flow.
-
com.atproto.repo.listRecords
query
List a range of records in a repository, matching a specific collection. Does not require auth.
-
com.atproto.repo.putRecord
procedure
Write a repository record, creating or updating it as needed. Requires auth, implemented by PDS.
-
com.atproto.repo.strongRef
object
A URI with a content-hash fingerprint.
-
com.atproto.repo.uploadBlob
procedure
Upload a new blob, to be referenced from a repository record. The blob will be deleted if it is not referenced within a time window (eg, minutes). Blob restrictions (mimetype, size, etc) are enforced when the reference is created. Requires auth, implemented by PDS.
-
com.atproto.server.activateAccount
procedure
Activates a currently deactivated account. Used to finalize account migration after the account's repo is imported and identity is setup.
-
com.atproto.server.checkAccountStatus
query
Returns the status of an account, especially as pertaining to import or recovery. Can be called many times over the course of an account migration. Requires auth and can only be called pertaining to oneself.
-
com.atproto.server.confirmEmail
procedure
Confirm an email using a token from com.atproto.server.requestEmailConfirmation.
-
com.atproto.server.createAccount
procedure
Create an account. Implemented by PDS.
-
com.atproto.server.createAppPassword
procedure
Create an App Password.
38 more under com.atproto ›
com.babesky
9
Narrow ›
-
com.babesky.actor.defs
defs
A link to a creator's profile on a content platform.
-
com.babesky.actor.featured
record
Featured posts record for the Babesky creator portfolio. An ordered selection of the creator's own posts (max 8) displayed as a curated preview reel in Atmosphere apps. Consumed alongside com.babesky.actor.profile, com.babesky.actor.links, and com.babesky.actor.support.
-
com.babesky.actor.links
record
A creator's content platform links, stored in their AT Protocol repository. Written by Babesky on behalf of users who opt in.
-
com.babesky.actor.profile
record
Core record of the Babesky creator portfolio. Stores the creator's tagline, avatar, content niches, ratings, collab availability, and contact preferences. Consumed alongside com.babesky.actor.links, com.babesky.actor.support, and com.babesky.actor.featured to render a full portfolio in Atmosphere-compatible apps.
-
com.babesky.actor.support
record
A creator's tip jar and financial support links, stored in their AT Protocol repository. Written by Babesky on behalf of users who opt in.
-
com.babesky.authManageSocial
permission-set
-
com.babesky.authManageStarterPacks
permission-set
-
com.babesky.authWriteCreatorProfile
permission-set
-
com.babesky.graph.verification
record
A verified creator attestation issued by Babesky. Records are written by Babesky's service DID (did:plc:qtapiembzpxlzsiagnc7eyy3) into its own repository, pointing at the subject's DID. Validity is dynamic: the handle and displayName must still match the subject's current values. Records must be deleted when a creator is removed from Babesky's database.
com.bsky38
12
Narrow ›
-
com.bsky38.influential.defs
defs
One subject's tallies, cached Bluesky profile, and campaign profile.
-
com.bsky38.influential.getLeaderboard
query
Paginated leaderboard of nominees ranked by counted votes.
-
com.bsky38.influential.getProfile
query
One nominee's tallies, cached Bluesky profile, and campaign profile.
-
com.bsky38.influential.getProfiles
query
Several nominees' tallies, cached Bluesky profiles, and campaign profiles, in one pass over the ranking.
-
com.bsky38.influential.getRandomNominee
query
Pick a random nominee, optionally excluding some DIDs.
-
com.bsky38.influential.getStats
query
Site-wide participation totals and the state of the voting window.
-
com.bsky38.influential.getTopPosts
query
A nominee's most-liked top-level Bluesky posts of the year, counted once when they joined the pool.
-
com.bsky38.influential.getVoterStatus
query
A voter's votes as indexed by the server, with remaining allowance.
-
com.bsky38.influential.profile
record
A nominee's campaign profile: a short blurb, a pinned post, and an avatar. Written by the nominee in their own repo; the record key MUST be 'self'.
-
com.bsky38.influential.searchNominees
query
Typeahead search over the nominee pool by handle, display name, or DID, ranked by leaderboard position.
-
com.bsky38.influential.setOptOut
procedure
Opt the authenticated account out of (or back into) the 38 Most Influential Bluesky Posters of 2026. Requests must carry a service-auth token bound to this method; the account is taken from the token's issuer. An admin-placed removal cannot be undone from here.
-
com.bsky38.influential.vote
record
Vote for an account. The record key MUST equal the subject DID.
com.cultureblocs
13
Narrow ›
-
com.cultureblocs.annotation
record
A bookmark/note about a specific work, typically minted by the AR gallery app at the moment of recognition. Meaningful entirely on its own — no bead required.
-
com.cultureblocs.bead
record
An atomic cultural memory: a visit, a dwell, an encounter, a screening. Minted on-device or by hand; annotated later.
-
com.cultureblocs.creative.connection
record
not from the namespace authority
A directional claim from this repository's holder about another party or record: 'we exhibited this', 'I performed on this', 'this is my work'. One-way and unapproved by default — the counterparty is never asked to accept anything. When two parties independently point at each other, any reader can compute a verified relationship from the closed loop; this is the mutual-mint primitive at professional scale. Pointing at a record with a CID pins the exact content attested to: if the target is silen
-
com.cultureblocs.creative.profile
record
A creative's self-asserted identity. Self-assertion is the normal state, not a deficient one: the record lives in the creative's own repository, which is the claim. Third-party attestation (com.cultureblocs.creative.connection) is an optional overlay some records acquire. This is a join layer, not a registry: externalIds carry ISNI/IPI/ORCID/Auracle/Wikidata and any future scheme so identifiers held elsewhere keep their value here.
-
com.cultureblocs.creative.work
record
not from the namespace authority
A minimal, self-asserted marker: 'I made this' / 'we made this'. Deliberately tiny. It proves that this claim was made on this date by the holder of this repository — nothing more, which is exactly the claim that can honestly be made. Everything else (industry metadata, scene layers, commercial registrations, licensing terms) belongs in other namespaces that REFERENCE this record's URI rather than adding fields to it.
-
com.cultureblocs.defs
defs
A named area — neighbourhood, town, city, borough, county, region — as a person would describe where they are. Deliberately carries no coordinates: this is how people say where they are based without being located. `wikidata` is the portable identity across countries; national codes (ONS GSS in the UK, Eurostat LAU in the EU) ride in externalIds so readers can roll a town up into its local authority and region.
-
com.cultureblocs.offer
record
Something a creative or a place offers, or needs, for a while: a recording engineer available for hire, off-peak rehearsal rates, a studio desk free for three months, 'looking for a drummer'. Separate from the profile because offers come and go. Pause and reopen an offer by changing `status` on the same record rather than deleting and recreating it, so links and history survive. Public by nature: carry links, never private contact details.
-
com.cultureblocs.place.lineup
record
Cultural detail attached to an event that the shared calendar record does not carry: who is on, and what is performed or shown. A layer, not a replacement — it references an event by strongRef and never duplicates it. Supersedes com.cultureblocs.venue.lineup, renamed with venue.profile → place.profile so the namespace stays consistent; the shape is unchanged except that `venue` is now `place`. If these fields prove generally useful they belong upstream in the community calendar lexicon, not here
-
com.cultureblocs.place.profile
record
A cultural place as a publishing party: a venue, gallery, rehearsal room, recording studio, artist studio, makerspace, supplier or shop — anywhere the public can visit or book. Supersedes com.cultureblocs.venue.profile, which covered only venues; a venue is now a place whose spaceTypes include 'venue'. This record is for spaces open to the public or bookable by them. A person working from home publishes a creative.profile (an area, never an address) and offers through com.cultureblocs.offer; the
-
com.cultureblocs.strand
record
A curated, ordered string of beads and annotations — typically one day's cultural path. The publishable story unit.
-
com.cultureblocs.venue.lineup
record
DEPRECATED — do not write new records. Use com.cultureblocs.place.lineup, identical except that `venue` is renamed `place`. This schema remains published so existing records stay resolvable. Original description: cultural detail attached to an event that the shared calendar record does not carry: who is on, and what is performed or shown. A layer, not a replacement — it references an event by strongRef and never duplicates it. The same discipline as the creative namespace: layers reference the c
-
com.cultureblocs.venue.listing
record
not from the namespace authority
DEPRECATED — do not write new records. Use community.lexicon.calendar.event instead: it is the shared event record of the open social web, so a venue's nights appear in every calendar app on the network rather than only in CultureBlocs. Cultural extras that the community event does not carry (who is on, works performed) live in com.cultureblocs.venue.lineup, which references the event. This schema remains published so existing records stay resolvable.
-
com.cultureblocs.venue.profile
record
DEPRECATED — do not write new records. Use com.cultureblocs.place.profile with spaceTypes including 'venue': the same publishing-party record, widened to cover rehearsal rooms, studios, suppliers and shops. This schema remains published so existing records stay resolvable; readers map it to place.profile as { spaceTypes: ['venue'], location, capacity, accessibility, links, externalIds, tags }. Original description: a venue or organiser as a publishing party: the small amount a grassroots space n
com.dryan
1
Narrow ›
-
com.dryan.timeline.entry
object
The dryan.com timeline's per-entry data, carried in the `content` open union of a site.standard.document record. The document holds what every entry shares (title, path, publishedAt, description, textContent, tags, coverImage); this holds the entry type, the day it belongs to, and the type-specific detail. atproto records cannot carry floats, so measurements that are not whole numbers (speeds, heart rates, coordinates) are decimal strings.
com.gamethesky
12
Narrow ›
-
com.gamethesky.deptofwar.run
record
One mission of Dept of War, published by the player into their own repo. The record stores every strike rather than a score: the sim is deterministic, so re-running the strike log against the same seed, mission and difficulty reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof — score and the rest are advisory and never trusted by a leaderboard.
-
com.gamethesky.epsteinfiles.run
record
One run of The Epstein Files, published by the player into their own repo. The record stores every input rather than a score: the sim is deterministic, so re-running the input log against the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof — score, level and the rest are advisory and never trusted by a leaderboard.
-
com.gamethesky.fightthesky.fighter
record
not from the namespace authority
A player's fighter, published into their own repo so anyone can fight its ghost: the build the sim uses, the style the CPU plays it in, and the paint it wears. One per account, at rkey `self`; saving again overwrites it. A ghost run pins the version it fought by CID, so overwriting changes no old result.
-
com.gamethesky.fightthesky.run
record
One run of Fight the Sky, published by the player into their own repo: a climb up the ladder, or a single ghost fight (see `ghost`). The record stores the fighter's build and every input rather than a score: the sim is deterministic, so re-running the input log against the same seed with the same build reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof — score, wins and the rest are advisory and never trusted by a leaderboard.
-
com.gamethesky.hatsoff.run
record
One Hats Off run, published by the player into their own repo. The record stores every shot rather than a score: the sim is deterministic, so re-running the fire log against the same seed on the same level reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof — wave, cured and the rest are advisory and never trusted by a leaderboard.
-
com.gamethesky.hauntthesky.house
record
A haunted house somebody made in Haunt the Sky's editor and published into their own repo: one floor, its look, its name, and optionally the maker's own cast. Anyone can play it from its link; runs in it name it by a strong ref, so a house rebuilt later never changes a night already played.
-
com.gamethesky.hauntthesky.run
record
One night of Haunt the Sky, published by the player into their own repo. The record stores every input rather than trusting a score: the sim is deterministic, so replaying the log on the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof; score, ticks, level and the rest are advisory and never trusted by a board.
-
com.gamethesky.make.fighter
record
A player's saved fighter for one chapter type of Game the Sky, at rkey = the chapter type's id (fight): their build, a style and their colors. Anyone can fight it as a ghost, the chapter's CPU at the wheel; a run against it pins this record's version.
-
com.gamethesky.make.game
record
A game somebody made in Make the Sky, published into their own repo: a title, a line about it, its look, and one to eight chapters, each one of Game the Sky's engines (a module) on one of its levels (a preset) with its knobs set. Play is decided by the chapters alone (and, in a game whose story branches, where its choices and jumps go). A game is edited in place (the same record, a new version): its board belongs to its way of playing (the chapters' modules, versions, presets and settings, and i
-
com.gamethesky.make.run
record
One play of a Make the Sky game, published by the player into their own repo. It stores every input rather than trusting a score: each chapter's engine is deterministic, so replaying its log on the same game reproduces the run exactly. Owning the record is the identity proof and replaying it is the score proof; score and the rest are advisory.
-
com.gamethesky.skytanks.run
record
One Sky Tanks run, published by the player into their own repo. The record stores every input rather than trusting a score: the sim is deterministic, so replaying the log on the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof; score, ticks, level and the rest are advisory and never trusted by a board.
-
com.gamethesky.skyvortex.run
record
One Sky Vortex run, published by the player into their own repo. The record stores every input rather than trusting a score: the sim is deterministic, so replaying the log on the same seed reproduces the run exactly. Owning the record is the identity proof, and replaying it is the score proof; score, ticks, level and the rest are advisory and never trusted by a board.
com.getorbyt
78
Narrow ›
-
com.getorbyt.actor.defs
defs
One box on the profile header's second page. The service composes it: what it says, its size and where it goes.
-
com.getorbyt.actor.getColorPalette
query
The server-owned profile foreground/background pairs shared with Byte.
-
com.getorbyt.actor.getProfile
query
An actor's Orbyt profile. Unauthenticated; a service-auth viewer adds `viewer` state.
-
com.getorbyt.actor.getProfiles
query
not from the namespace authority
Several Orbyt profiles in request order. Unknown actors are omitted.
-
com.getorbyt.actor.profile
record
The account's Orbyt profile, separate from its profile on any connected network. Every field is optional: an absent field falls back to the network profile, so an account that never edits here still renders. The profile's colours and app preferences stay in com.getorbyt.profile; how each Highlight box looks is here, with the boxes.
-
com.getorbyt.authFullApp
permission-set
-
com.getorbyt.community.beginDeletion
procedure
Begins permanent deletion for an unpublished Community and returns the current PDS declaration to delete. Requires authenticated service authorization by the current declaration holder.
-
com.getorbyt.community.cancelDeletion
procedure
Cancels deletion before the current declaration has been deleted from its PDS. Requires authenticated service authorization by the current declaration holder.
-
com.getorbyt.community.checkName
query
Whether a lowercase Community name is free. Names are globally unique at the AppView, and a record whose name is taken is rejected at projection time rather than at write time, so clients check before writing.
-
com.getorbyt.community.createAppeal
procedure
Creates the post author's single private appeal for a specific Community removal action. Requires authenticated service authorization.
-
com.getorbyt.community.createReport
procedure
Creates a private Community-moderator report for a linked post. Requires authenticated service authorization.
-
com.getorbyt.community.declaration
record
The canonical public descriptor for an Orbyt Community, and the record that declares the Community exists. Its AT-URI is the Community's identity everywhere else in the protocol. The record key is a TID, including for the replacement declaration an accepted ownership transfer produces: the recipient mints it before accepting and names it to the AppView, which stores it as the only URI the continuation may be written at. Every Community is public: the record is world-readable, and the directory a
-
com.getorbyt.community.defs
defs
Recent activity in a Community, so its page can show the people in it and not only its counts.
-
com.getorbyt.community.deleteRole
procedure
Deletes a role the Community defined, or, for the key moderator, puts the built-in moderator role back to its default permissions. A role someone holds cannot be deleted; move them to another role first. Only an administrator may delete roles. Recorded in the moderation log.
-
com.getorbyt.community.getCommunity
query
A single Community by AT-URI or by name, hydrated with viewer state when the request is authenticated. Exactly one of `community` and `name` is required: the AT-URI is the Community's identity, while the name is what a public link can carry.
-
com.getorbyt.community.getFeed
query
A Community's native feed skeleton, served from projected com.getorbyt.community.post links. Clients hydrate post URIs through their authenticated Bluesky AppView. Removed posts are only included for their author and Community moderators.
-
com.getorbyt.community.getModmailThread
query
One Modmail thread and its messages, newest first. Without member, the caller's own thread, which is absent until they first write. With another account's member, the caller needs manage-mail. Viewer-specific and never cached; reading does not mark the thread read (see updateModmailSeen).
-
com.getorbyt.community.getPostCommunities
query
The Community each post was published to, for a batch of posts. A post in no visible Community is omitted. A Community post record outranks a legacy channel tag on the post itself.
-
com.getorbyt.community.getWriteStatus
query
Whether the AppView accepted records the caller wrote to their own repository. Community records are projected from the firehose, not written through this service, so a record that violates a rule this service enforces — a name already taken, a post link the Community's postPolicy forbids — lands in the author's repository and is then silently dropped. This is how the author finds out. Only the caller's own records may be queried.
-
com.getorbyt.community.listAuditLog
query
Lists append-only Community audit events visible to the authenticated moderator or administrator.
-
com.getorbyt.community.listCommunities
query
The public Community directory. Unauthenticated; an authenticated request additionally receives viewer state on each Community.
-
com.getorbyt.community.listMembers
query
A Community's members. Anyone may list active members; listing muted or banned members requires a moderator role.
-
com.getorbyt.community.listModerationQueue
query
Lists private reports and appeals for one Community. Requires authenticated moderator authorization.
-
com.getorbyt.community.listModmailThreads
query
The mod team's Modmail inbox: one thread per member, most recent message first, each marked unread when the member wrote since this moderator last read it. Requires manage-mail. Viewer-specific and never cached.
-
com.getorbyt.community.listMyCommunities
query
The authenticated account's own Community memberships. Defaults to active and muted memberships.
-
com.getorbyt.community.listReportedPosts
query
The moderation queue grouped by post: each reported post once, with how many reports it has and why, newest report first. Requires manage-reports.
-
com.getorbyt.community.listRoles
query
The Community's roles: the built-in owner and moderator roles, then the roles the Community defined, in order. Requires manage-roles. Viewer-specific and never cached.
-
com.getorbyt.community.listTransfers
query
Lists ownership transfers visible to the authenticated caller as current holder, target, or Community administrator.
-
com.getorbyt.community.manageMember
procedure
Mute, ban, or re-role a member. Only an administrator may set a role; a moderator may mute and ban, but never a peer or an administrator. Administration is service state and may be granted to an account that does not hold the declaration record; authority over the record itself is never transferable and always belongs to the repository that holds it.
-
com.getorbyt.community.manageModmailThread
procedure
Archives a member's Modmail thread out of the open inbox, or brings it back. Requires manage-mail. A new message from the member reopens an archived thread on its own.
-
com.getorbyt.community.manageTransfer
procedure
Invites, accepts, declines, or cancels an ownership transfer. Requires authenticated service authorization; only the current declaration holder may invite or cancel and only the target may accept or decline.
-
com.getorbyt.community.membership
record
not from the namespace authority
A user-owned canonical membership link, one record per Community. The record key MUST be base32(sha256(community AT-URI)) truncated to 24 characters, lowercase and unpadded, so writing it twice replaces the record instead of adding a second one and a repo can never hold two memberships for the same Community. The AppView rejects a record whose key is not that derivation, so the invariant is enforced rather than assumed. The key is derived from the AT-URI rather than the Community name, which its
-
com.getorbyt.community.moderatePost
procedure
A moderator action on one post's Community-level state. Removal is scoped to the Community; only actions that change state are journaled.
-
com.getorbyt.community.post
record
not from the namespace authority
A user-owned canonical link between a Bluesky post and an Orbyt Community. A sidecar record: it lives in the post author's own repository and its record key MUST be the record key of the linked app.bsky.feed.post, exactly as app.bsky.feed.threadgate does. That makes one link per post structural rather than enforced after the fact, and lets the link be fetched with a single com.atproto.repo.getRecord once the post URI is known. The linked post remains canonical in app.bsky.feed.post.
-
com.getorbyt.community.replyModmail
procedure
Replies to a member's Modmail thread as the mod team. Requires manage-mail. Moderators cannot start a thread: they answer one a member opened. The member sees the reply in the thread and in Activity, from the team rather than from the moderator.
-
com.getorbyt.community.requestSync
procedure
Wake the existing Community ingester after a repository write. Acknowledgment is not projection success; use getWriteStatus to check acceptance. Only the caller's own Community record URIs are accepted. Rate limited and coalesced with scheduled ingestion.
-
com.getorbyt.community.resolveAppeal
procedure
Permanently upholds or restores one appealed Community removal. Requires authenticated moderator authorization.
-
com.getorbyt.community.resolveReport
procedure
Resolves one Community report by removing its post or dismissing the report. Requires authenticated moderator authorization.
-
com.getorbyt.community.resolveReportedPost
procedure
Resolves every open report about one post at once: remove the post, or dismiss the reports and keep it. Requires manage-reports, and manage-posts to remove.
-
com.getorbyt.community.saveRole
procedure
Creates a Community role, or changes one. Without a key it creates a role; with one it replaces that role's name and permissions. The key moderator changes what the built-in moderator role may do, and keeps its name. Only an administrator may define roles. Recorded in the moderation log.
-
com.getorbyt.community.sendModmail
procedure
"Message the mods": opens the caller's private thread with the Community's mod team, or continues it. Each account has one thread per Community, and a message reopens it if the mod team archived it. Anyone signed in may write, including a muted or banned member; whoever holds manage-mail answers with replyModmail instead. Rate-limited per sender.
-
com.getorbyt.community.setAnnouncement
procedure
Sets or clears the Community's announcement, shown on its page and, when set or changed, in its members' activity as `communityAnnouncement`. Requires manage-settings. The announcement is service state rather than part of the declaration record, so a moderator granted manage-settings can set it without writing the owner's repository. Setting and clearing are both recorded in the moderation log.
-
com.getorbyt.community.updateModmailSeen
procedure
Marks a Modmail thread read for the caller up to seenAt. Read state is per reader: the member's own, and each moderator's own. The mark only moves forward and never past now. Sending a message marks the thread read for its sender.
-
com.getorbyt.community.updatePublication
procedure
Publishes or unpublishes a Community. Requires authenticated service authorization and a manager action advertised by the Community view.
-
com.getorbyt.getLiveFeatures
query
The release features live for the viewer right now, including any the service turns on for this account before launch so it can be tested. A feature absent from the answer is off, and so is every feature when a client cannot reach this method or reads an older service that does not serve it. Anonymous callers get the features live for everyone. Never cached: the answer depends on who asks.
-
com.getorbyt.getServiceInfo
query
What this deployment of the Orbyt service can currently do, for clients that cannot be upgraded in step with it. Clients feature-detect against `capabilities` rather than comparing version numbers: only one version of this service is ever live, while many client builds run for months. Every field is optional and the whole call is optional — a client that cannot reach it, or reads an older service that does not serve it, must behave exactly as it did before. Unauthenticated.
-
com.getorbyt.graph.block
record
not from the namespace authority
An Orbyt block. Hides the subject's Orbyt content and relationship views from the blocker, and the blocker's from the subject.
-
com.getorbyt.graph.follow
record
Deprecated: Orbyt's follow is the account's app.bsky.graph.follow, and the service no longer reads these records for any rule. Older clients still write them. An Orbyt follow, independent of any follow on a connected network. Clients write it under the record key derived from `subject` (base32 of its SHA-256, 24 characters, as community.membership does), so importing the same follow from two clients writes one record. The service accepts any key and keeps one follow per pair.
-
com.getorbyt.graph.getFollowers
query
Legacy: accounts following the actor with the deprecated `com.getorbyt.graph.follow`, newest first. Orbyt's follow is the network follow; this stays for older builds and goes once `minimumClient` passes the last build that writes Orbyt follows. Unauthenticated; a service-auth viewer adds `viewer` state.
-
com.getorbyt.graph.getFollows
query
Legacy: accounts the actor follows with the deprecated `com.getorbyt.graph.follow`, newest first. Orbyt's follow is the network follow; this stays for older builds and goes once `minimumClient` passes the last build that writes Orbyt follows. Unauthenticated; a service-auth viewer adds `viewer` state.
28 more under com.getorbyt ›
com.luminframe
6
Narrow ›
-
com.luminframe.audioAnalysis
record
Reusable analysis of a public plyr track. Contains feature data, never audio or effect settings.
-
com.luminframe.collection
record
A curated, ordered list of shader effects, referenced by AT-URI. Curation is separate from authorship: a listed effect may live in any author's repo — listing it vouches for it without copying it, so attribution stays with the author's DID in the URI. Luminframe loads its default library from the record keyed 'featured' in luminframe.com's repo.
-
com.luminframe.effect
record
A custom shader effect: GLSL fragment code plus the typed parameters that drive it, publishable to the author's repo and loadable by Luminframe at runtime. The grammar a valid record must satisfy (reserved uniform names, body shape, parameter rules) is the shader environment contract, versioned by `env`.
-
com.luminframe.image
record
An image edited in Luminframe, saved to the author's repo, together with the effect recipe used to produce it.
-
com.luminframe.page
record
A shareable Luminframe page that names a visualizer and presents its song and effect palette as one work.
-
com.luminframe.visualizer
record
An image-free Luminframe visualizer: a song reference and the effect palette that responds to it.
com.pagehare
4
Narrow ›
-
com.pagehare.content.markdown
object
not from the namespace authority
Canonical markdown content for a site.standard.document, embedded in the document's open content union. The markdown string is the canonical article body; optional cover metadata is stored alongside it; the document's textContent and the com.pagehare.facets / com.pagehare.embeds sidecars are derived projections regenerated from it on every write. Note: at.markpub.markdown is tracked as a potential community successor $type once it stabilizes — only this wrapper $type would migrate, never the pay
-
com.pagehare.document
record
not from the namespace authority
PageHare's sidecar for a site.standard.document it wrote: one per PageHare document, with the same rkey, so listing this collection enumerates exactly the PageHare documents in a repo (site.standard.document is shared with other apps). It carries the document's facets: mentions, links, and tags inside long-form content, as byte-slice offsets (UTF-8) over the document's textContent field, reusing app.bsky.richtext.facet feature types so facet-aware indexers can parse with existing logic. The huma
-
com.pagehare.embeds
record
not from the namespace authority
Structural blob retention sidecar for a site.standard.document. PDSs retain blobs only while a record field references them; image URLs inside the markdown string do not count. Every blob the document's markdown references must therefore also appear here. A pure derivation: regenerated from the document's content.markdown (plus upload metadata) on every write (rkey mirrors the document rkey), never hand-edited.
-
com.pagehare.publication
record
not from the namespace authority
Marks a site.standard.publication as the one PageHare manages for this author. site.standard.publication is shared with other apps and its url can change (subdomain rename, custom domain), so PageHare finds its own publication through this pointer rather than by matching the url, and listing this collection enumerates PageHare publications. The rkey mirrors the publication's rkey.
com.pimstash
25
Narrow ›
-
com.pimstash.carcare.authFull
permission-set
-
com.pimstash.carcare.photo
record
A photo of Work in Car Care. Each photo is its own record, so its identity survives a re-encode.
-
com.pimstash.carcare.serviceItem
record
A Service Item in Car Care: one maintenance task on a Vehicle, either scheduled by distance and/or months or done once. Its Work references it by record key.
-
com.pimstash.carcare.vehicle
record
A Vehicle in Car Care: one car, truck or bike whose maintenance is tracked. Its Service Items reference it by record key.
-
com.pimstash.carcare.work
record
Work in Car Care: one time a Service Item was done. Its photos reference it by record key.
-
com.pimstash.gear.authFull
permission-set
-
com.pimstash.gear.closet
record
A Closet in Gear: one person's collection of Gear Items and the Loadouts packed from them. Its Items and Loadouts reference it by record key.
-
com.pimstash.gear.item
record
A Gear Item in a Closet: one piece of gear and what it weighs. Field names follow world.treeline.gear.item where it has the field. An Item's storage location is kept on the device and never written here.
-
com.pimstash.gear.loadout
record
A Loadout in Gear: a named set of one Closet's Gear Items, packed for a kind of trip.
-
com.pimstash.planner.authFull
permission-set
-
com.pimstash.planner.board
record
A Board in Planner: one person's Lists, Labels, Cards and comments. Every child names it by record key. A Board carries no people: its owner is the repository.
-
com.pimstash.planner.card
record
A Card in a List. Field names and limits follow site.exosphere.kanban.entry where it has the field. A Card has no Assignee.
-
com.pimstash.planner.comment
record
A comment on a Card. It names no author: the repository is its author.
-
com.pimstash.planner.label
record
A Label a Board's Cards can carry, named by record key from each Card.
-
com.pimstash.planner.list
record
A List on a Board: a column of Cards, in the Board's order.
-
com.pimstash.recipes.authFull
permission-set
-
com.pimstash.recipes.bookMeta
record
What pimstash's Recipes keeps about a Book that exchange.recipe.collection has no field for. It lives in the same repository and under the same record key as the collection it extends, which its subject names; a reader should ignore one whose subject does not name the collection at its own key.
-
com.pimstash.space.transfer
record
Marks a Space still being filled by a move. Written with a move's first run and deleted with its last, so every other device lists the Space as unfinished. A platform record: every pimstash Space type lists it.
-
com.pimstash.stuff.authFull
permission-set
-
com.pimstash.stuff.event
record
An Event in a Stuff Thing's History. Its kind is its payload's type; a payload type this client does not know is kept and listed as an unknown Event. The author is the repository the record sits in, so there is no actor field.
-
com.pimstash.stuff.kind
record
A Kind in a Stuff Trove: the fields its Things share unless a Thing sets its own.
-
com.pimstash.stuff.location
record
A Location in a Stuff Trove: a place Things are kept, in a tree of Locations, or the inside of a container Thing.
-
com.pimstash.stuff.thing
record
A Thing in a Stuff Trove. A shared field (name, category, make, model, measure, lifespanMonths, usageUnit, ratedUsage, photo) is absent, never null, to inherit the Kind's.
-
com.pimstash.stuff.trove
space
A private Space holding one Stuff Trove, keyed by the Trove id.
-
com.pimstash.stuff.troveMeta
record
A Stuff Trove's own name and cover. The Space holding it is the Trove: its key is the Trove id, and no other record names the Trove.
com.pipobscure
4
Narrow ›
-
com.pipobscure.bundle.attestation
record
A statement by the repository's owner about a bundle — that they vouch for it, or that it is bad — identified by its whole-file hash — the hash a bundle signature covers — or about a suite, identified by the hash of what it says (see com.pipobscure.bundle.suite). The record key is that hash in lowercase hex, so there is at most one attestation per account per bundle or suite, and a verifier knows which record to ask for. A good attestation of a suite counts for each bundle installed from it; a b
-
com.pipobscure.bundle.like
record
The repository's owner likes an app: a star for it, across its releases. It is of the app's listing (com.pipobscure.bundle.listing), and each like comes with a post from the same account saying so. The record key is the sha256 of the listing's at:// address in lowercase hex, so an account has one like of an app; liking it again counts on that record and lists the new post. A like vouches for nothing; nothing installs or refuses by it.
-
com.pipobscure.bundle.listing
record
A bundle the repository's owner makes available under a name: the record key, which is also what it installs as. It is an app, or a plugin for one, as its subject says. The record says only where the bundle is fetched from — a url, or a domain whose 'nzip:' TXT record names one, exactly one of the two. It vouches for nothing, and whatever is fetched is verified like any other download.
-
com.pipobscure.bundle.suite
record
A set of listed bundles the repository's owner makes available to install together, under a name: the record key. Installing the suite installs each member as it would be installed by itself, and an update follows the suite as members are added and taken out. The suite vouches for none of them: each member is reviewed and verified on its own. What it can do is set a minimum — a signer and attesters a member must carry — below which that member is refused.
com.publicdomainrelay
38
Narrow ›
-
com.publicdomainrelay.temp.agent.class
record
An agent class definition. Acts as a template that agents are instantiated from. The class is a named bundle of skills (strongRefs to com.publicdomainrelay.temp.agent.skill records) plus optional metadata. Instantiating an agent from a class means spawning a runtime (or sub-agent context) seeded with this skill set.
-
com.publicdomainrelay.temp.agent.skill
record
An agent skill record that describes a capability the agent can perform, with examples and property references.
-
com.publicdomainrelay.temp.auth.allowlist.rbacDid
record
not from the namespace authority
Self-allowlist granting the record owner's DID access to their own account-scoped operations. Used by bidders and other automated actors to authorize AT Protocol writes (e.g. applyWrites) on their own repo via service-auth tokens.
-
com.publicdomainrelay.temp.badgeBlueKeys
record
Associates a device key with a DID, enabling key→DID lookup for vouch graph traversal and service authorization.
-
com.publicdomainrelay.temp.compute.config.wif.simple
record
Simple Workload Identity Federation parameters used by the requester to obtain a token authorized for the provider.
-
com.publicdomainrelay.temp.compute.events.vm.delete
record
Requests that the provider delete/tear down a provisioned VM — e.g. because its workflow finished, or because its policy engine never came up. Sent by the requester, since the provider treats the VM as a black box and cannot observe these conditions itself.
-
com.publicdomainrelay.temp.compute.events.vm.onNetwork
record
Reports that a provisioned VM has come up on the network and is reachable (e.g. it registered its SSH key / fedproxy route and its policy engine answered).
-
com.publicdomainrelay.temp.compute.events.vm.started
record
Reports that a provisioned VM has started booting.
-
com.publicdomainrelay.temp.compute.vm
record
Descibes a virtual machine
-
com.publicdomainrelay.temp.gateway.deleteCompute
procedure
Tear down a compute resource identified by its receipt. Gateway submits a market.event with a compute.events.vm.delete payload to the winning bidder.
-
com.publicdomainrelay.temp.gateway.requestComputeVM
procedure
Request a VM through the compute contract gateway. Gateway builds cloud-init from sshPublicKey, creates compute.vm and market.rfp records, discovers bidders, runs the full RFP protocol, submits accept, and verifies the receipt. Returns receipt refs and websocatUrl for SSH access.
-
com.publicdomainrelay.temp.gateway.requestComputeWorkerEphemeral
procedure
Request an ephemeral Deno worker through the compute contract gateway. Gateway bundles source, creates workerManifest record, runs the full RFP protocol, and returns the worker instance ref for single-request execution.
-
com.publicdomainrelay.temp.gateway.requestComputeWorkerPersistent
procedure
Request a persistent Deno worker through the compute contract gateway. Gateway bundles source, creates workerManifest record, runs the full RFP protocol, starts the worker, and returns the worker instance ref and execute URL.
-
com.publicdomainrelay.temp.gateway.subscribeComputeEvents
subscription
Subscribe to lifecycle events for a compute contract. Gateway pushes events as they arrive from the bidder (vm.started, vm.onNetwork, terminated).
-
com.publicdomainrelay.temp.market.accept
record
Acceptance of a bid on an RFP
-
com.publicdomainrelay.temp.market.accepts.free
record
The requester's acceptance of a bid's free (no-cost) terms. Minted before settling and passed (by AT-URI + CID) to the grant endpoint named in the bids.free url; the bidder resolves it and mints a com.publicdomainrelay.temp.market.receipts.free in response. The free counterpart of com.publicdomainrelay.temp.market.accepts.x402.
-
com.publicdomainrelay.temp.market.accepts.x402
record
The requester's acceptance of a bid's x402 payment terms. Minted before settling payment and passed (by AT-URI + CID) to the x402 GET endpoint named in the bids.x402 url; the bidder resolves it, verifies payment, and mints a com.publicdomainrelay.temp.market.receipts.x402 in response.
-
com.publicdomainrelay.temp.market.badgeBlueKey
record
Publishes the public half of a badge.blue attestation key that this repo signs market.* records with. The record key is the key's did:key, so a verifier can look up a key by did:key directly in the author's PDS repo — a PDS-native key registry complementing DID-document key binding.
-
com.publicdomainrelay.temp.market.bid
record
A bid on an RFP
-
com.publicdomainrelay.temp.market.bidderDiscovery
record
Published by a bidder in its own repo to announce availability. The bidder periodically updates `updatedAt` to signal liveness. The market registry polls this record to decide whether the bidder is still active.
-
com.publicdomainrelay.temp.market.bidderRegistration
record
An index entry in the market registry's repo tracking a registered bidder. The registry creates one entry per (bidderDid, payloadNsid) pair when a bidder calls registerBidder. Liveness is determined by polling the bidder's own bidderDiscovery record — this index entry carries no heartbeat timestamps. When a bidder goes stale the registry deletes its index entries.
-
com.publicdomainrelay.temp.market.bids.free
record
Bid payload offering compute at no cost
-
com.publicdomainrelay.temp.market.bids.x402
record
Includes pricing/payment terms and x402 endpoint for issuing a receipt against an accept.
-
com.publicdomainrelay.temp.market.event
record
A lifecycle event reported against a receipt (e.g. a provider-opaque resource like a VM coming up, joining the network, or needing to be deleted).
-
com.publicdomainrelay.temp.market.listBidders
query
List active bidders indexed by the market registry.
-
com.publicdomainrelay.temp.market.offering
record
Declares that a bidder is willing to submit bids for RFPs whose payload NSID is in appliesTo. The bidder's market service DID reference (for submitRfp via PDS proxying) is given by endpointUrl.
-
com.publicdomainrelay.temp.market.receipt
record
Receipt for acceptance of a bid on an RFP
-
com.publicdomainrelay.temp.market.receipts.free
record
Proof-of-grant receipt minted by the bidder in response to a GET against the bids.free url. No payment is involved; the receipt is the bidder's verifiable record that it agreed to provide the resource for free. Returned (by AT-URI + CID) to the requester, which uses it as the payload of the higher-level com.publicdomainrelay.temp.market.accept so the bidder can verify the grant before provisioning. The free counterpart of com.publicdomainrelay.temp.market.receipts.x402.
-
com.publicdomainrelay.temp.market.receipts.x402
record
Proof-of-payment receipt minted by the bidder in response to a successful x402-gated GET against the bids.x402 url. Returned (by AT-URI + CID) to the requester, which uses it as the payload of the higher-level com.publicdomainrelay.temp.market.accept so the bidder can verify payment before provisioning.
-
com.publicdomainrelay.temp.market.registerBidder
procedure
Register a bidder with the market registry. Called by bidders after they publish a bidderDiscovery record in their own repo and connect to the relay. The registry verifies the caller's service-auth JWT issuer matches the bidderDid, then indexes the bidder so it appears in listBidders queries. Liveness is determined by the registry polling the bidder's bidderDiscovery record — there is no separate heartbeat procedure.
-
com.publicdomainrelay.temp.market.relays
record
List of AT Protocol relay URLs that the record owner recommends for market discovery. Requesters read this record via autoDiscoverRelayUrls to find relays to query for bidder offerings.
-
com.publicdomainrelay.temp.market.rfp
record
Top-level Request For Proposal (RFP). Envelope that strongRefs a domain-specific payload (e.g. compute.vm).
-
com.publicdomainrelay.temp.market.submitAccept
procedure
Submit the AT-URI and CID of an accept record directly to the bidder named in the winning bid's payload, settling the contract: the bidder resolves accept->bid->rfp->vm, provisions the resource, mints a market.receipt record, and returns a strong reference to it plus its submitEvent service DID reference. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced accept record. The r
-
com.publicdomainrelay.temp.market.submitBid
procedure
Submit the AT-URI and CID of a bid record directly to the RFP issuer, bypassing the firehose. Used when the RFP includes a submitBid service DID reference. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced bid record. The receiver additionally verifies the bid's badge.blue attestations (network.attested.signature): at least one inline signature must verify against the attest
-
com.publicdomainrelay.temp.market.submitEvent
procedure
Submit the AT-URI and CID of an event record directly to the counterparty, bypassing the firehose. Used when the accept or receipt includes a submitEvent service DID reference — e.g. so a requester can tell a bidder to delete a VM whose workflow finished, or whose policy engine never came up, since the bidder treats the VM as a black box. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored t
-
com.publicdomainrelay.temp.market.submitRfp
procedure
Submit an RFP directly to a bidder whose offering record matches the RFP payload NSID. The bidder creates a bid and optionally calls submitBid back to the RFP issuer. Must be called via PDS service-proxying (atproto-proxy); the receiver verifies the inter-service auth JWT and requires its issuer to be the DID that authored the referenced RFP record. The receiver additionally verifies the RFP's badge.blue attestations (network.attested.signature): at least one inline signature must verify against
-
com.publicdomainrelay.temp.requester.associateConfirm
procedure
Confirm requester association via PDS service-proxied XRPC call. The webapp calls this through the user's PDS with atproto-proxy header set to the requester's DID with #requester_associate service. The requester verifies the inter-service auth JWT, resolves the caller's handle, and presents a CLI confirmation prompt before proceeding with the RFP flow.
-
com.publicdomainrelay.temp.tangled.spindle.trigger
procedure
Manually trigger a pipeline run on a Tangled spindle. Intended to be called via PDS service proxying (the 'atproto-proxy' header, pointed at the spindle's did:web service entry), so the user's PDS mints and signs the inter-service auth token; the spindle verifies the token's issuer against their DID document and requires it to match the trigger's 'actor'. Mirrors the sh.tangled.pipeline fields a knot dispatches on a push/PR event.
com.t0ronto
3
Narrow ›
-
com.t0ronto.commons.attestation
record
A single attestation in the t0ronto data commons: one quad asserting that `subject` stands in relation `predicate` to an object. Subject is an at-uri (a project entity, or another attestation in the retracts case). Predicate is an at-uri to a project predicate entity (see scripts/predicate_seed.json). Object is exactly one of `objectRef` (an at-uri reference to another entity — an edge in the graph), `objectLit` (a scalar literal — a property value; external IRIs live here as xsd:anyURI), or `ob
-
com.t0ronto.commons.defs
defs
A social-platform presence, used as a com.t0ronto.commons.statement objectStruct (predicate `social`). The platform list is open — clients should fall back gracefully on unknown values. Per-platform value semantics differ: `bluesky` carries a DID (did:plc:* or did:web:*) so resolution flows through the AT Proto directory; `email` carries an email address; `website` carries a URL; other platforms carry either a URL or a platform-native handle.
-
com.t0ronto.commons.entity
record
An anchor in the t0ronto data commons: a bare, claim-free identity for a thing — an organization, programme, venue, neighbourhood, or a vocabulary concept. The anchor holds NO properties of its own. Everything true of it — name, type, topics, location, prefLabel, broader, alignments — is asserted by separate com.t0ronto.commons.statement records, which may be authored by many different DIDs. The anchor exists only to mint a stable, resolvable identity that statements point at. Whether an anchor
com.tituslegaldesign
5
Narrow ›
-
com.tituslegaldesign.immigration.agreement
record
A single 287(g) agreement between ICE and a state or local law enforcement agency, as documented in the Titus Legal Design 287(g) Program Report. One record per agency + program-model combination. The record key (rkey) is a permanent human-readable slug assigned by the publisher (e.g. 'ga-tift-county-so-tfm') and never changes, even if ICE's published agency name is later corrected.
-
com.tituslegaldesign.immigration.agreementEvent
record
An append-only changelog entry for a 287(g) agreement record. One event is written every time the sync detects a change: a new agreement, a cancellation, a field-level modification, or a data correction. Together these events form the public changelog that ICE's snapshot-only publishing omits. Record key is a TID (timestamp identifier); events are never updated or deleted. Events carry the CID of the agreement record version they describe, so a third party holding an older CAR export can verify
-
com.tituslegaldesign.immigration.authSync
permission-set
-
com.tituslegaldesign.immigration.dispute
record
A contested claim about a 287(g) agreement record. Written into the DISPUTING PARTY'S OWN repository, not the publisher's, and referencing the disputed record by AT-URI and CID. Anyone may publish one: the agreement's publisher need not consent and cannot suppress it. Consumers find disputes by querying com.atproto.sync.listReposByCollection for this collection and following the subject URIs. Record key is a TID.
-
com.tituslegaldesign.immigration.sourceSnapshot
record
A point-in-time capture of an upstream source publication: ICE's participating-agencies workbook, a FOIA production, or a roster PDF. Agreement events reference the snapshot that justified them, so every published change traces back to an archived, content-addressed copy of the document it came from. Record key is a TID. Snapshots are never updated or deleted; a revised upstream file is a new snapshot.