EnderDash

Choose an integration

Select the API or identity flow that matches your application.

Match the interface to the goal

GoalInterfaceIdentity or credential
Read or change dashboard resources from a scriptHTTP APIUser API key or dashboard session
Let an AI client inspect resources and edit knowledge draftsMCPAccount OAuth token with MCP scopes
Sign users into another application with a dashboard accountAccount OAuthRegistered account OAuth client
Sign users in with an identity proved on a game serverGame OAuthOrganization-owned game OAuth client
Integrate a plugin in the agent's JVMJava and Kotlin APILoaded in-process API provider
Collect a hosted form and validate it in a pluginPlayer verificationAuthenticated agent and a registered plugin handler

Keep the credentials separate

An agent key associates one agent with one server record. It does not authenticate HTTP requests, identify a player, or act as an OAuth client secret.

A dashboard-account identity and a game-account identity have different issuers, claims, registries, and tokens. Signing in through either does not grant organization membership or server access.

Start with a small check

For a script, create a user key and list servers. For an AI client, connect it to MCP and list accessible organizations before asking for any change.

For sign-in, configure an OIDC library from the correct discovery document and register an exact callback URI. Use the separate OAuth walkthrough before handling production accounts.

For a plugin, first retrieve the provider and read apiVersion. Then add a verification handler if the plugin needs hosted forms.

Live agent operations use a separate transport

The HTTP API documents dashboard procedures. It is not a general remote shell or a replacement for the browser-to-agent protobuf transport. Check the generated operation before assuming a live panel action is available over HTTP.

Was this page helpful?

Send a quick note if anything is missing or unclear.

Last updated on

On this page