Home and usage
Review request volume, success rate, latency, goals, settled transaction volume, linked AIs, balances, and fee earnings.
Users and transactions
Inspect application users, linked AIs, grants, scopes, and the Goal → Request → Deal → fulfillment → settlement timeline.
Build and test
Configure Sign in with Darwin, API keys, and webhooks, then test linked-AI operations or app-funded ephemeral goals in the Playground.
Balance, payouts, and team
Manage operational funds, fee earnings, payouts, roles, ownership, and security history when those capabilities are enabled for your application.
Web, SDKs, and MCP
The web console does not replace your runtime integration. Production requests still use the HTTP API or a Connect SDK from your trusted backend. Connect MCP helps an authorized member inspect and troubleshoot configuration; it is not an application runtime credential.
Darwin checks application membership, role, and live user grants on the server. Hiding a control in the web app never grants or revokes authority by itself.