PLP Registry

Documentation

Learn about the Prompt Library Protocol and how to use the PLP Registry.

1What is PLP?

PLP (Prompt Library Protocol) is an open standard for storing and managing AI prompts. It provides a RESTful API specification that allows different prompt management tools to be interoperable.

Core Endpoints

PUT
/v1/prompts/{id}

Create or update a prompt

GET
/v1/prompts/{id}

Retrieve the latest version of a prompt

GET
/v1/prompts/{id}/{version}

Retrieve a specific version

DELETE
/v1/prompts/{id}

Delete a prompt

Response Format

All responses use a standardized envelope format:

{
  "id": "my-prompt",
  "content": "You are a helpful assistant...",
  "meta": {
    "version": 1,
    "createdAt": "2024-01-01T00:00:00Z",
    "updatedAt": "2024-01-01T00:00:00Z"
  }
}

For the full specification, see the PLP GitHub repository.

2What is PLP Registry?

PLP Registry is a central directory of PLP-compliant servers. It provides a unified access point and vendor-agnostic URLs for all registered prompt libraries.

Key Features

  • Vendor Discovery: Browse and search all public PLP servers
  • URL Abstraction: Use plp.pub/vendor-name instead of vendor-specific URLs
  • Compliance Testing: Automated validation that servers meet PLP requirements
  • Periodic Re-testing: Daily validation to ensure continued compliance

3How the Registry Works

1.URL Redirection

When you make a request to the registry, it returns a 307 Temporary Redirect to the vendor's actual server:

# Request
GET https://plp.pub/acme-prompts/v1/prompts/greeting

# Response
HTTP/1.1 307 Temporary Redirect
Location: https://prompts.acme.com/v1/prompts/greeting

# Your HTTP client follows the redirect automatically

2.Compliance Validation

Before activation, the registry runs compliance tests against your server:

  • Tests all required PLP endpoints
  • Validates response formats
  • Checks error handling
  • Generates compliance score (must be ≥80%)

3.Registration Flow

1

Get Installation Hash

Visit plp.pub/register to receive a unique installation hash

2

Install CLI

Run the installation command to register your vendor name

npx @plp/registry install <hash> --vendor-name "ACME"
3

Activate Server

When your server is ready, activate it for compliance testing. You can re-run this command to update your server URL or retry if activation fails.

npx @plp/registry activate https://your-server.com/v1
✓

Go Live

After passing compliance, your server is accessible at plp.pub/your-name

4Why Use the Registry?

For Vendors

  • • Increase discoverability
  • • Prove compliance publicly
  • • Simple URL for customers
  • • Free listing and validation

For Users

  • • Switch vendors easily
  • • Trust compliance badges
  • • Single integration point
  • • No vendor lock-in

Ready to Get Started?

I want to register my PLP server

Register Your Server

I want to learn about the CLI tool

For detailed CLI documentation, visit the npm package:

@plp/registry on npm

I want to implement PLP

Read the full protocol specification:

PLP Specification