BETA
Docs · Account & Billing

Manage your
access to Axle Keys.

The Account page is where users manage profile settings, billing, credits, AI connectors, agent permissions, collaboration, and Showroom ownership. Studio is where models are created — Account is where the user and access rules are managed.

Open Account →All docs →
ProfileBilling & creditsAI connectorsAgent permissionsCollaborationSecurityBest practices
Profile

Your account identity
across Axle Keys.

Profile information can affect how your work appears on public surfaces. Studio projects are private, but Exhibition models and Showroom pages may display account information.

Profile settings

  • —Name and email
  • —Username or public slug
  • —Avatar or logo
  • —Short bio
  • —Business or organization name
  • —Public contact preferences
  • —Service area, if relevant
  • —Website and social links

Where your identity may appear publicly

  • —Exhibition models — creator attribution
  • —Showroom pages — business or creator name
  • —Shared links and public product pages
  • —Published examples and System contributions
  • —Future comments, remixes, and community features

Before publishing, review which name, business, or owner information will be visible.

Billing & credits

Pricing and usage
live in Account.

A public pricing page may come later when plans are ready to be explained clearly. For now, billing and credit details are managed through Account.

Billing settings

  • —Current plan and subscription status
  • —Payment method
  • —Invoices, receipts, billing history
  • —Usage charges
  • —Plan limits
  • —Upgrade, downgrade, or cancellation

Credits and what they cover

Credits apply to actions that require compute, AI, storage, or export processing. The exact credit model may change as Axle Keys develops.

  • —AI model calls and model generation
  • —Model repair and validation jobs
  • —Export jobs and file conversions
  • —Large imports
  • —MCP/API usage
  • —Advanced agent workflows

The Account page should make usage understandable before credits are spent.

Usage history

Usage history helps users see how their account resources are being spent. A useful usage record shows date/time, project name, action type, credits used, agent or tool used, and success or failure. AI and geometry workflows can cost money — users should be able to understand what happened.

Account owners should review usage history regularly, especially when agents, API keys, or collaborators are active.

AI connectors & MCP

Connect the tools
and services you use.

AI connectors and MCP/API access let external tools and agents work with your Axle Keys projects. Both should be configured carefully.

AI connector settings

  • —Provider selection
  • —API keys or OAuth connection
  • —Default model
  • —Spending limits
  • —Approval settings
  • —Enabled workflows
  • —Project access
  • —Usage tracking

A connected AI service may receive project context, prompts, files, model code, parameters, or screenshots. Only connect services you understand and trust.

MCP and API access settings

  • —MCP access status
  • —API keys
  • —Connected agents
  • —Allowed tools and project scopes
  • —Read/write permissions
  • —Approval requirements
  • —Credit limits
  • —Revoke access
  • —Access logs
Agent permissions

Agents should only have
the access they need.

Read-onlySafest

The agent can inspect project information but cannot change anything.

  • —Read active model and parameters
  • —Read files and validation report
  • —Inspect version history
Draft accessRecommended default

The agent can create proposed changes but cannot make them live.

  • —Create model drafts
  • —Prepare parameter changes
  • —Stage file changes
  • —Create export plans
Modify accessControlled

The agent can make controlled changes to the live model.

  • —Update parameters
  • —Promote validated drafts
  • —Upload files
  • —Create exports and run jobs
Publish accessExplicit only

The agent can affect public visibility. Should usually require explicit user approval.

  • —Publish to Exhibition
  • —Update a Showroom product
  • —Unpublish a model
  • —Change public descriptions
Account accessTightly controlled

The agent can affect account-level settings. These actions should always be tightly controlled.

  • —Billing and API keys
  • —Plan changes
  • —Permission changes
  • —Connected tools
Read Agents & Skills →
Collaboration & Showroom ownership

Teams, organizations,
and public pages.

Physical object workflows often involve many people. Collaboration features are part of the larger Axle Keys direction.

Collaboration
○ Coming

Future settings for shared projects, project roles, owner/admin/member access, edit/export/publish permissions, approval workflows, and billing ownership. Goal: make it clear who can see, edit, publish, or spend credits on a project.

Organizations
○ Coming

Account structure for shops and teams — organization profile, team members, member roles, billing owner, shared projects, Showroom ownership, API keys, agent permissions, usage limits, project templates, and shop-specific standards.

Showroom ownership
● Account-managed

A Showroom page is public-facing but managed through an owner account. Account controls: Showroom slug, business name, logo, contact details, product list, inquiry routing, admin users, publishing permissions, and public visibility.

Read Showroom docs →
Security & privacy

Know what's private
and protect your account.

Security best practices

  • —Use a secure password
  • —Protect connected email accounts
  • —Do not share API keys publicly
  • —Revoke unused connectors
  • —Limit agent access to what's needed
  • —Review usage history regularly
  • —Remove old collaborators
  • —Check public visibility before publishing
  • —Avoid uploading sensitive files unless necessary

If you believe your account has been compromised, contact Axle Keys →

Information that may become public

Studio projects are private by default. Information becomes public when you publish to Exhibition, create a Showroom page, share a public link, or expose public profile information.

Before publishing, review:

  • —Project and file visibility
  • —Account name and business name
  • —Public description and model preview
  • —Public parameters
  • —Third-party content
  • —Client information

Best practices,
troubleshooting, and more.

● Best practices

Manage your account well

  • —Keep your profile current — public models and Showroom pages use it
  • —Review billing before heavy workflows — AI, exports, and validations consume credits
  • —Use limited permissions — give agents and collaborators only what they need
  • —Revoke unused connectors — disconnect tools, API keys, or agents no longer needed
  • —Check public identity before publishing — make sure the right name appears
  • —Monitor usage history — helps identify unexpected spending or agent activity
● Troubleshooting

Common issues

  • —Can't access Studio — check login status, plan access, browser session, billing status
  • —Credits used unexpectedly — check usage history, connected agents, MCP/API activity, recent exports or validations
  • —Showroom information is wrong — check profile info, Showroom owner settings, public slug, business details
  • —Agent has too much access — review connected agents, permissions, API keys, and MCP access; revoke when needed

Your account is
your access layer.

Profile, billing, connectors, permissions, and Showroom — all managed in one place. Keep it current and you'll know exactly what's private, what's public, and what agents can reach.

Open Account →Get help →