Read and operate PromptEden through REST.

Use a pe_ API key to list projects and monitors, fetch captured answers, and inspect monitoring results from your own agent loop.

API keys quickstart Agent platform overview

List monitors

curl https://app.prompteden.com/api/v1/monitors \
  -H "Authorization: Bearer pe_..." \
  -H "Accept: application/json"

Capabilities

Scoped keys

Keys are scoped for account, project, monitor, and result routes. Pass them as Authorization: Bearer pe_... or X-API-Key.

Monitors and results

List monitors, fetch captured AI responses, inspect providers, and pull the proof data behind Eden's work.

MCP writes and approvals

OAuth connector write attempts on raw REST are blocked. With an API key, local stdio project, monitor, and analytics writes call REST directly. The nine content-agent tools appear only when content agents are enabled for the team; reads require content:read and writes require content:write. Content reads and writes run through hosted MCP, including from local stdio. Every content write returns an approval_required proposal with a browser link for an owner/admin decision. Among the public local tools, hosted create_monitor and analytics_add_property_host return approval proposals with a deepLinkUrl; other project and analytics writes in that local list are disabled on hosted MCP. See the MCP connection docs.

Agent-readable surfaces

Accuracy

PromptEden monitors AI visibility and helps you inspect brand mentions, competitors, and cited sources. Use Eden or your own agent to understand the evidence. Content creation with Eden is available to every team.

Build with PromptEden