Registration creates your app’s identity on Orceum. You complete this process in the Orceum Developer Studio. Upon creation, you receive an app_id (needed for OAuth and tracking) and an orceum_webhook_secret (used to verify the lifecycle webhooks Orceum sends to your app).
Save your Orceum Webhook Secret (orc_sk_...) immediately after creation. It is shown only once. This secret is used exclusively to verify lifecycle webhooks (like when a user installs your app).This is different from the whs_* token you use to sign events you send to Orceum. See Webhooks.

​
Creating an App

Go to the Orceum Developer Studio and click Create App. You will be asked to select your app type:

​
Native App

For apps where you host the HTTP endpoint that Orceum calls. You will need to provide:
  • Name: Display name of your app.
  • Description: A concise description. The AI uses this to understand what your app does broadly.
  • Authentication Method: None, API Key, or OAuth. See Authentication.
  • Endpoint URL: The base URL Orceum will POST action calls to.
  • Manifest: You paste your JSON manifest detailing your app’s actions and parameters. See The Manifest.
  • Webhook Configuration: (Optional) Provide your installation webhook URL to receive lifecycle events.

​
MCP App

For apps that expose tools via the Model Context Protocol. You will need to provide:
  • Name & Description: Display name and details.
  • Authentication Method: Usually None or OAuth.
  • MCP Server URL: The URL of your MCP endpoint.
  • Transport: Select between SSE or Streamable HTTP.
Orceum connects to your MCP server, discovers your tools automatically via the protocol, and generates the manifest for you. See MCP Apps for the full setup guide.

​
Skill

For lightweight automations or scripts running in Orceum’s managed sandbox. You upload a code bundle (a ZIP file or GitHub repository link) containing a SKILL.md file. Orceum parses the bundle, extracts the manifest, and provisions the sandbox. No deployment or endpoint URL is required on your end.

​
Required Fields Summary

When creating any app, pay close attention to these fields:
​
Name
string
required
Display name of your app. Shown to users in the marketplace and conversation UI.
​
Description
string
required
A concise, user-facing description. Crucially, this is also used by the assistant to understand your app’s overall purpose before inspecting its individual actions.
​
Authentication Method
string
required
None, API Key, or OAuth. Determines the installation flow for users.

​
After Registration

  1. Copy your App ID: You need this if you are configuring OAuth redirect URIs.
  2. Save your Webhook Secret: Store orc_sk_... securely; it will not be shown again.
  3. Set up OAuth (if applicable): Register the Orceum redirect URI with your provider: 
    https://api.orceum.com/v1/apps/{app_id}/oauth/callback
  4. Publish your App: Your app starts in a PENDING state. To make it discoverable in the store, you must publish it.

Installation Flow

How users install your app and grant credentials

Publishing Your App

Move from PENDING to ACTIVE for marketplace listing