This guide follows the exact path a developer takes in the Abstraxn Dashboard before writing any code.

​
End-to-end dashboard flow

​
1) Create an account

  1. Go to dashboard.abstraxn.com and sign up or sign in.
  2. Complete onboarding (plan selection, billing if applicable).

​
2) Create an application

  1. From the dashboard, create a new application (for example Rooba AMOY in your project list).
  2. Abstraxn issues an application API key (Kong key-auth). This single key is used across Wallets, Bundler, Relayer, Paymaster, and Agent Kit.
You do not need a separate “Agent Kit signup.” The agentic tenant is tied to your application.

​
3) Automatic service provisioning

When an application is created, Abstraxn automatically provisions the platform stack for that app: You do not manually enable each service before using Agent Kit. The Agentic Stack menu appears under Configurations for every provisioned app. Optional: you can still open Register New Agent Kit to set a display name if your UI shows a registration step; the underlying agent_apps row is created during app provisioning.

​
4) Open Agentic Stack in the sidebar

In the left sidebar:
  1. Select your application from the app dropdown.
  2. Expand Configurations.
  3. Open Agentic Stack (BETA).
Sub-pages:

​
5) Overview — API key and MCP

The Overview page is where you copy credentials for backend and MCP clients. MCP configuration (for Cursor or other MCP hosts):
Use View documentation on Overview once linked to these docs. Keep the API key out of frontend bundles and git.

​
6) All agents — monitor your fleet

Agents appear here after your backend calls @abstraxn/agent-kit createAgent() (or Agent Kit REST POST /agents). The dashboard does not create agents by itself.
Agents with Autonomous enabled show an orange warning in the detail panel. Review interaction policies before enabling.
Click a row to open the agent panel with two tabs:

​
Identity tab (ERC-8004)

Shows whether the agent is registered on-chain and surfaces trust metadata for operators:
  • Global agent identifier — portable CAIP-style id after registration.
  • Per-chain registrations — on-chain agent id, owner address, identity registry, transaction hash, and block explorer links.
  • Controllers and wallets — EVM/Solana addresses linked to the agent.
Registration is initiated from your backend (SDK registerAgentIdentity or Kit identity/prepare + confirm), not from the dashboard alone. Supported identity chainId values are listed in ERC-8004 agent identity.

​
Activity log tab

Audit trail of MCP tool calls for that agent — tool name, status (ok, error, payment_required, etc.), duration, and expandable request/response details. Useful for debugging LLM tool loops and x402 retries. Logs populate after the agent runs MCP tools through your integration with the correct agent_id.

​
7) Tools — MCP catalog

The Tools page calls MCP tools/list with your application API key and shows the live catalog your LLM can invoke. Names and count change as Agent Kit is updated — the UI always reflects the latest server response. Use View Schema on each card when wiring arguments in your LLM or backend. See MCP tools reference and x402 payments for execution details.

​
8) Plan limits

Agent counts depend on your plan (Pricing):

​
Next steps

Abstraxn CLI

npm i -g @abstraxn/cli — login and chat with MCP tools from your terminal.

5-minute smoke test

Verify API key + MCP with curl before writing app code.

Credentials

Application key vs wallet accessKey.

SDK quickstart

Install @abstraxn/agent-kit, create agents, store the wallet access key.