Bluesky Services to the Community

Mirror of plc.directory

We run a mirror of plc.directory. This is implemented using bsky-watch/plc-mirror. The mirror follows the export log of the PLC directory and replays the operations onto a local database. The exposed API implements DID lookups only, no audit log, export, etc. If the database lags behind the latest operations by too much, the server refuses to handle requests.

There are currently no rate limits and no uptime guarantees. Please be considerate, though: We just run this for fun and might stop if it ever gets too expensive.

You can query the mirror at plc-mirror.bsky.leobalduf.com for a DID at

curl -s "https://plc-mirror.bsky.leobalduf.com/<did>"

For example:

curl -s "https://plc-mirror.bsky.leobalduf.com/did:plc:nggqjgdkqhytcag6x7fhiyuv" | jq .

which should return something like:

{
  "@context": [
    "https://www.w3.org/ns/did/v1",
    "https://w3id.org/security/multikey/v1",
    "https://w3id.org/security/suites/secp256k1-2019/v1"
  ],
  "alsoKnownAs": [
    "at://leobalduf.bsky.social"
  ],
  "id": "did:plc:nggqjgdkqhytcag6x7fhiyuv",
  "service": [
    {
      "id": "#atproto_pds",
      "serviceEndpoint": "https://verpa.us-west.host.bsky.network",
      "type": "AtprotoPersonalDataServer"
    }
  ],
  "verificationMethod": [
    {
      "controller": "did:plc:nggqjgdkqhytcag6x7fhiyuv",
      "id": "did:plc:nggqjgdkqhytcag6x7fhiyuv#atproto",
      "publicKeyMultibase": "zQ3shoMrXu5Yx1xjeHdpSD94TxYFZPKK64Fs52BE2jqKWxvnh",
      "type": "Multikey"
    }
  ]
}