API Access

The growth engine, over API and MCP.

Use REST API keys for direct integration, hosted MCP for agent clients, and OAuth + PKCE for provisioned connectors. Write actions stay inside PromptEden approvals and policies.

Bring your agent API quickstart

The surface

Everything agents need, without a parallel trust model.

REST API v1

Accounts, projects, monitors, results, provider catalog, content topics, articles, publishing, and displacement-scan previews.

Scoped API keys

Use pe_ keys over Authorization: Bearer or X-API-Key. Scopes cover account, projects, monitors, results, and content.

Hosted MCP

Remote MCP clients connect at /api/mcp and use the same bearer-token auth and scoped tool vocabulary.

Approval-gated writes

OAuth connector tokens can call raw REST routes for read-scoped operations; write actions should use hosted MCP approvals.

API Request

GET /api/v1/monitors
Authorization: Bearer pe_abc123...

{
  "monitors": [...]
}

Route examples

Common first calls.

GET /api/v1/accountGET /api/v1/projectsGET /api/v1/monitorsGET /api/v1/monitors/:monitorId/resultsGET /api/v1/content/topicsPOST /api/v1/content/articlesPOST /api/v1/content/articles/:articleId/publishGET /api/v1/agent/status

Get started

Wire PromptEden into your stack

Use scoped API keys for REST, hosted MCP for agents, and OAuth + PKCE for provisioned connector clients.

API keys quickstart Connect MCP

CLI npm packaging is coming soon.