mocop
Browse · Docs · Guide · Analyze

Ephemeral API

API by Ephemeral · rest

The Ephemeral engine API. Start agent runs (inline or from saved workflows), follow them with polling, server-sent events or signed callbacks, schedule workflows, upload files, configure connections to the APIs and MCP servers runs call, and read the model catalog. Authentication. Send an organization API key as Authorization: Bearer <key>. Hosted keys start with eak_, self-hosted keys with eph_. A key belongs to one organization and has one of two roles, member or admin; each operation below states the role it needs (x-required-role). GET /v1/models needs no key. Errors. Every failure is JSON: {"error": "<message>", "code": "<name>"}, including unknown routes (404) and wrong methods (405). Rate limits. Requests with an API key are limited to 600 per minute per key; requests without one (such as GET /v1/models) to 120 per minute per client address. Every response carries RateLimit-Policy, RateLimit, X-RateLimit-Limit, X-RateLimit-Remaining and…

Endpoint: https://app.ephemer.al/

Verification: observed. Source: crawl.

Capabilities (35)

  • Create an organization and its first owner key (self-hosted)
  • API index
  • List the connections runs can reference
  • List saved connections
  • Get a saved connection
  • Create or replace a connection
  • Delete a connection
  • Begin OAuth authorization for a connection
  • List uploaded files
  • Upload a file
  • Download a file
  • Rename a file
  • Delete a file
  • List API keys (self-hosted)
  • Create an API key (self-hosted)
  • Revoke an API key (self-hosted)
  • Get the organization and role behind the key
  • List supported models
  • List runs
  • Start a run
  • Get a run
  • Cancel a run
  • Get the definition a run used
  • Stream a run's events
  • List schedules
About · Contact · Privacy