Redirect Service

Protocol redirect handling

How Redirects Work

Any request to registry.echostash.app/:vendor-slug returns a 307 Temporary Redirect to that vendor's PLP server.

Path & Query Preservation

http
# Request:
GET registry.echostash.app/acme/prompts?limit=10

# Redirects to:
307 → https://api.acme.com/v1/plp/prompts?limit=10

Use Cases

  • Stable URLs - Share registry URLs that always point to the right server
  • Load balancing - Let vendors change their backend without breaking clients
  • Discovery - Users can find servers just by knowing the vendor slug