AI-agent onboarding
Use the Artax onboarding wizard for AI agents.
Create an account, verify it, issue a devnet sandbox key, and add funding when you are ready for paid mainnet-beta usage.
Use the guided flow
The wizard uses the live account APIs to create the account, continue verification in the browser, inspect onboarding state, issue a devnet sandbox key, and point to funding or execution upgrades when they are needed. Start on devnet first, then add a separate mainnet-beta environment and key to the same project workspace for live traffic.
Step 1
Create the account shell
Start the account setup path. The first project environment and sandbox key still arrive only after verification completes.
Step 2
Complete verification
Paste a recovery token, request a fresh verification step, or open the focused verify-email page when you want the dedicated completion flow.
Step 3
Inspect the live account setup
Use the session-backed path after verification, or paste an existing account API key to load the current onboarding, overview, project, key, and funding reads through one refresh.
Live wizard state
Load or create an account
Create an account, complete verification, or paste an existing account key to inspect the live account setup.
Access mode
Discovery only
No account is loaded yet. Discovery and docs remain available before the live bootstrap path starts.
Agent state
Discovery Only
Current AI-agent onboarding state from the onboarding response.
Trust tier
Not loaded
Current trust-tier posture stays explicit throughout the guided flow.
Authority posture
No machine authority yet
No active machine authority is available to summarize yet.
Project workspace
Not ready yet
Verification completion creates the first project environment unless you intentionally create a different project first.
Sandbox key
Not issued yet
The devnet sandbox key is the current machine credential for advisory-first use.
Active projects
0
Project inventory is loaded from the current project routes.
Active API keys
0
API-key inventory is loaded from the current key routes.
Funding path
Not loaded
Load live state to inspect the funded-advisory upgrade path.
Available balance
Not loaded
Prepaid balance starts at zero and only expands through the USDC funding path.
Account status
Not created
Pending verification, sandbox-ready, and higher-authority states stay explicit.
Email path
Not started
Verification delivery stays explicit so the wizard does not imply unsupported inbox behavior.
Current onboarding progression
These steps are derived from the current onboarding state plus live verification, project, key, and funding status.
1. Discovery and validation
completeQuickstart, Developers, and this onboarding wizard show how to create an account, verify it, issue a devnet sandbox key, and add funding when needed.
2. Verification and project environment
currentVerification is still pending. The verification page remains available, with browser-based continuation in this environment.
3. Sandbox key issued
upcomingThe sandbox API key is issued when the verification step completes.
4. Advisory usage ready
upcomingAdvisory usage becomes available after sandbox bootstrap is fully issued.
5. Funding upgrade path
upcomingFunding instructions are available when you need expanded paid advisory use beyond the free tier.
6. Bounded execution requests
upcomingExecution requests remain outside the default path until a separate execution-request key is issued.
Allowed capability families
Load live state to inspect the current allowed capability envelope.
Current sandbox key scopes
The sandbox key scopes appear here after verification or a live onboarding-state read.
Unavailable capability families
Broader autonomous execution still remains outside the default path. The current execution-request upgrade stays separate from this wizard.
Funding instructions
Load live state to inspect the current prepaid USDC instructions.
Route sequence
The wizard stays attached to the actual current routes rather than inventing a separate orchestration backend.
POST /api/accounts
POST /api/accounts/request-email-verification
POST /api/accounts/verify-email
GET /api/account/onboarding-state
GET /api/account/overview
GET /api/projects
GET /api/api-keys
GET /api/account/funding-status
GET /api/account/funding-instructionsAccount operations available to agents
/api/accountsCreate or bootstrap the current Artax account shell.
/api/accounts/request-email-verificationRequest a fresh verification email or continue verification from this browser.
/api/accounts/verify-emailComplete the current verification stage directly when a delivered link or browser-held token is available.
/api/account/onboarding-stateRead the current onboarding state for the caller account, including verification status, first project environment, sandbox-key presence, trust tier, authority guidance, and the AI-agent display state.
/api/account/overviewRead trust tier, authority posture, capability envelope, restriction state, and current project or API-key inventory summary.
/api/projectsInspect the current project inventory and effective capability scope.
/api/api-keysInspect the current key inventory, configured scopes, effective scopes, and authority tiers.
/api/account/funding-statusRead the current funding stage, balance state, trust tier, and funded-upgrade posture.
/api/account/funding-instructionsRetrieve the current prepaid USDC funding path when expanded paid advisory use is actually needed.
/api/api-keys/funded-advisoryIssue a dedicated funded-advisory API key once credited prepaid balance exists, without widening the generic key-creation route.
Keep these boundaries attached
- The wizard handles account creation, verification, project setup, API keys, and funding steps through the live Artax account flow.
- GET /api/account/onboarding-state is read-only. It helps the wizard inspect state, but it does not replace account creation, verification, or funding operations.
- Accounts start in a scoped, advisory-first setup. Artax does not grant unrestricted autonomous execution.
- Start on devnet. When you are ready for live usage, add a separate mainnet-beta environment, key, and funding setup to the same project workspace.
- Funding stays prepaid USDC only. There is no unsecured SOL funding path or silent authority escalation.
Related current surfaces
Quickstart
Use the broader builder quickstart when you want the hosted-review, dashboard, typed integration path, and devnet-to-mainnet key sequence in one place.
Developers
Open API, SDK, hosted-review, embedded-review, and account setup guidance in one place.
Verify email
Use the verification page directly when you want the focused verification-only step.
Add funds
Follow the USDC funding path when expanded paid advisory use is actually needed.
Pricing
See what stays free on devnet and what is billed when you turn on paid mainnet-beta usage.