Request access
Product
Use cases
Docs
Resources
PricingSign inRequest access

What it does

And around it

All product

Compose. Version. Prove. Publish.

One lifecycle for every kind of AI asset.

{{ }}
Use a prompt as a toolFill a prompt like a small toolPick a prompt, fill its variables, read the finished text.

Who it is for

All use cases

Who uses a prompt library

Four ways people use it today.

Start here

Look things up

Library and the API

All docs

Documentation

Guides, the tool reference and the glossary.

Latest release0.1.0: The Prompt Verse website2026-10-17

Read

Know us

All resources

Read, ask, follow along

Notes from building Prompt Verse.

Newest postYour prompts are already software, so give them version controlA prompt that decides what your product says is code in everything but name. Four things software teams do tha

The HTTP API

The Prompt Verse HTTP API: an API key under Connect, the same library as MCP, and model routes that answer AI_DISABLED in the pre-beta.

Updated 30 October 2026 · View as Markdown

Prompt Verse has a small HTTP API for callers that do not speak MCP. It uses the same nouns as the tools on Use with your AI. There is no client library. You call it directly.

The app lists the current routes under Connect, in Advanced. That list is the one to trust if a path here and the app ever disagree.

A key#

  1. Open Connect and make a key under Keys. It is shown once. Copy it then.
  2. Send it as a bearer token: Authorization: Bearer <key>. The header x-api-key is accepted as well.
  3. Name the key after the client that uses it, and revoke it in the app when you stop using that client.

Every call with a key acts in your own workspace, after a plan check. Without a Prompt Verse plan the answer is PLAN_REQUIRED. Open the app once so the workspace exists before the first call.

Reading the marketplace (GET /api/listings) does not need a key. Everything else does.

What you can call#

Paths below are on your Prompt Verse address. A few you will use first:

CallWhat it does
GET /api/prompts?kind=Your prompts, responses and contexts
POST /api/promptsCreate one. Body includes kind and title
GET /api/prompts/:idOne document, with its tree and wrappers
PATCH /api/prompts/:idChange one you own
POST /api/prompts/:id/shareMint or revoke a link. Body: { "visibility": "unlisted" }
GET /api/search?q=&limit=Everything you own, by title, tag or text
GET /api/skills and POST /api/skillsList or create a skill
GET /api/tools and POST /api/toolsList or create an MCP tool you author
POST /api/tools/:name/callCall one of your tools by name. Body: { "input": {} }
GET /api/elements?type=Library pieces
GET /api/agents and GET /api/workflowsAgents and workflows you own
GET /api/evalsYour evals
GET /api/vcs/:entity_type/:entity_id/commitsHistory. The same family has branch, checkout, merge and tag

entity_type on the version routes is prompt, workflow or agent, as in Versions, branches and merges.

Rendering a prompt into finished text, with variables filled, is an MCP call: prompts with action render. The HTTP API returns the stored document on GET /api/prompts/:id.

What answers AI_DISABLED#

Read the prompt with GET /api/prompts/:id, or render it over MCP, and let your own AI answer it. To test, your AI reads the cases and scores them. See Testing with evals.

Publishing, installing and withdrawing on the marketplace follow The marketplace. Paid checkout is mocked until payments open, so nothing is charged.