at.happyproto.registry.publishProfile

happyproto.at

{
  "$type": "com.atproto.lexicon.schema",
  "defs": {
    "main": {
      "description": "Check a package profile against the rules the indexer applies, and optionally write it to the caller's repo. The indexer validates a record only after it is published and skips an invalid one quietly, so a publisher writing the record itself gets no feedback; this answers the same refusal before the record exists. Pass validateOnly to check a record without writing it. Like every XRPC procedure this needs an authenticated caller, so validateOnly is a dry run rather than an anonymous one.",
      "errors": [
        {
          "description": "The caller's identity could not be determined, so there is no repo to write to.",
          "name": "AuthRequired"
        },
        {
          "description": "The record is not a profile the indexer would accept. The message names the reason.",
          "name": "InvalidRecord"
        },
        {
          "description": "The record could not be written to the caller's repo.",
          "name": "Upstream"
        },
        {
          "description": "The registry has no identity configured.",
          "name": "NotConfigured"
        }
      ],
      "input": {
        "encoding": "application/json",
        "schema": {
          "properties": {
            "record": {
              "description": "An at.happyproto.plugin.profile record.",
              "type": "unknown"
            },
            "slug": {
              "description": "The package slug, which becomes the record key. A profile record carries no slug of its own.",
              "maxLength": 512,
              "type": "string"
            },
            "validateOnly": {
              "default": false,
              "description": "Check the record and write nothing. Still requires authentication, as every procedure does.",
              "type": "boolean"
            }
          },
          "required": [
            "slug",
            "record"
          ],
          "type": "object"
        }
      },
      "output": {
        "encoding": "application/json",
        "schema": {
          "properties": {
            "cid": {
              "format": "cid",
              "type": "string"
            },
            "uri": {
              "description": "The record written. Absent when validateOnly was set.",
              "format": "at-uri",
              "type": "string"
            },
            "valid": {
              "description": "Always true; an invalid record is an error, not a result.",
              "type": "boolean"
            }
          },
          "required": [
            "valid"
          ],
          "type": "object"
        }
      },
      "type": "procedure"
    }
  },
  "id": "at.happyproto.registry.publishProfile",
  "lexicon": 1
}

Validate Record

Validate a record against at.happyproto.registry.publishProfile

Validation Options
Treat any remaining unresolved references as valid

Metadata

DID
did:plc:mo7vq4jbioxwafy5zkcc3eux
CID
bafyreig2mz7pis7bz4himik7y3towyehv3vb2h2pky4qoacc6f7yodswwi
Indexed At
2026-10-19 18:20 UTC
AT-URI
at://did:plc:mo7vq4jbioxwafy5zkcc3eux/com.atproto.lexicon.schema/at.happyproto.registry.publishProfile

Similar Lexicons

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • Replace a package profile the caller has already published, held to the rules publishProfile applies. This is how a publisher edits a profile: it writes to the caller's own repo as them, where com.atproto.repo.putRecord…

  • Create or update a plugin project in the caller's repo. The first call writes the site.standard.publication, the at.happyproto.registry.project and the software.release.project, in that order, so each is indexed after w…

  • Publish a version of a plugin to the caller's repo. Writes a software.release.manifest carrying the artifact, the changelog as a site.standard.document when one is given, the software.release.version, and the channel na…

Lexicon Garden

@