Introduction
PrompTessor developer documentation
Build prompt workflows with the PrompTessor REST API, connect AI clients through MCP, and receive signed webhook events.
Verified against the implementation ·
Choose an integration
PrompTessor exposes one account and credit balance through three complementary integration surfaces. Use REST for application code, MCP for AI clients and agents, and webhooks for asynchronous notifications.
| Surface | Best for | Authentication | Production endpoint |
|---|---|---|---|
| REST API | Backends, scripts, products, and automations | Bearer API key or OAuth | https://api.promptessor.com/v1 |
| MCP | ChatGPT, Claude, Codex, coding agents, and MCP clients | OAuth only | https://mcp.promptessor.com/mcp |
| Webhooks | Operation, usage, and publishing events | Signed HTTPS deliveries | Your public HTTPS endpoint |
Requirements
- A verified PrompTessor account.
- An active paid plan. Free accounts cannot use the Public API or remote MCP.
- An API key for REST requests, or an OAuth-capable MCP client for MCP.
- A public HTTPS endpoint if you want to receive webhooks.
One shared product state
API and MCP activity uses the same PrompTessor account, monthly usage, add-on balance, history, and Prompt Library as the web product.
Service endpoints
| Purpose | URL |
|---|---|
| REST base URL | https://api.promptessor.com/v1 |
| OpenAPI document | https://api.promptessor.com/v1/openapi.json |
| Hosted API reference | https://api.promptessor.com/v1/docs |
| Remote MCP server | https://mcp.promptessor.com/mcp |
| OAuth issuer | https://auth.promptessor.com |
| OAuth metadata | https://auth.promptessor.com/.well-known/oauth-authorization-server |
| MCP protected-resource metadata | https://mcp.promptessor.com/.well-known/oauth-protected-resource |
Recommended first path
- 1
Create credentials
Open Workspace → API & MCP. Create a scoped API key for REST, or let your MCP client start the OAuth flow.
- 2
Read your capabilities
Call GET /capabilities before enabling features. grantedScopes (also available through the backward-compatible scopes field) contains the permissions held by the current credential; availableScopes contains every scope supported by the platform.
- 3
Run one safe request
Generate a prompt with a unique Idempotency-Key, or connect MCP and call get_usage.
- 4
Add production controls
Record X-Request-Id, respect rate-limit headers, retry idempotently, and verify webhook signatures before processing events.