Browse prompts
that work.
A public registry of tested, versioned prompts. Fork, customize, and ship — with eval results on every prompt.
How it works
The registry acts as a phone book for PLP servers, enabling discovery and protocol-level redirects.
Vendors Register
PLP server operators register their endpoint with the registry using the CLI or API.
Compliance Check
Automated tests verify the server implements PLP correctly. Verified vendors get a trust badge.
Clients Discover
Applications query the registry to find vendors, or use plp:// URLs that redirect automatically.
Browse & Discover
Search prompts by name, category, or tags. Filter by provider compatibility and quality score.
Fork & Customize
NewOne-click fork any public prompt. Customize variables, sections, and logic — then ship your version.
Quality Indicators
NewEval results displayed on every public prompt. See assertion pass rates, test suite coverage, and version history before you fork.
Protocol Redirects
Short URLs that resolve to any PLP server. Use plp://vendor/prompt instead of full URLs.
Registry API
Programmatic access to the vendor directory. Build tools that discover PLP servers automatically.
Open & Decentralized
No lock-in. The registry points to servers you control. Switch providers anytime.
Protocol redirects
Use short, memorable URLs that resolve to any registered PLP server.
# Instead of remembering full URLs...
https://api.acme-prompts.com/v1/prompts/customer-support
# Use a protocol redirect:
plp://acme/customer-support
# The registry resolves it automaticallyPublish your prompts
Register your PLP-compliant server. Ship prompts with eval results attached so others can trust what they fork.
# Install the CLI
npm install -g @plp/registry-cli
# Register your server
plp-registry register --name acme --url https://api.acme-prompts.com
# Run compliance tests
plp-registry verify --name acme