FruxonDocs

Organization Settings

General config, profile, tokens, billing, and pricing visibility

The Settings page is your organization's control center. Most operational configuration lives here, organized into clear sections.

General

Organization identity and branding.

  • Organization name — the human label shown in the sidebar and to invitees.
  • Slug — used in URLs and (when you make agents public) in shareable links.
  • Website — optional, used in invite emails and the public agent profile.
  • Logo — optional, surfaces in participant-channel messages and invitation flows.

Profile

Per-user (not per-organization).

  • Display name and avatar
  • Email and password
  • Notification preferences

Team Management

Invite, role-manage, and remove members. Full coverage in Team & Roles.

API access

Organization-scoped, scoped access tokens for server-to-server access — split into personal access tokens (fx_pat_…, authenticate as you) and service-account tokens (fx_sat_…, authenticate as a workload identity). Mint with a preset (Observer, Operator, Developer, Maintainer, Admin) or hand-pick scopes; rotate with optional scope/expiry overrides; every issuance and rotation is audited. Tokens are sent in the Authorization: Bearer header.

Quick start:

  1. Settings → Personal access tokens → Generate token.
  2. Pick a preset (or scopes), name it (prod-server, ci-evals, support-zendesk-bot), set an optional expiry.
  3. Copy the secret — it's shown once.
curl -X POST "https://api.fruxon.com/v1/tenants/{tenant}/agents/{agent}:execute" \
  -H "Authorization: Bearer $FRUXON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"parameters": {"topic": "the EU AI Act"}}'

See the Tokens guide for the full scope vocabulary, rotation semantics, audit history, MCP auto-mint, and the inbound:deliver flow for webhooks and Agent Network inbound routes.

Treat tokens like passwords. Don't commit them to git, don't paste them in Slack, don't share them across environments. Rotate on any suspicion.

Usage

Real-time view of what your organization is consuming:

  • Tokens — by provider, by model, by agent, by day.
  • Requests — API and Agent Network traffic volume.
  • Storage — knowledge base size.
  • Plan utilization — current period vs allowance.

Use Usage to spot the agent or model that's eating your budget before the bill arrives.

Billing

Plan, payment method, invoices. Admins can:

  • Upgrade or downgrade
  • Update card / billing email
  • Download invoices
  • See current period totals and projected month-end

Model Pricing

A read-only view of the per-model token rates Fruxon uses to compute cost. Useful for back-of-envelope math when picking a model for a step.

Evaluation Metrics

Define the rubrics your evaluations score against. See Evaluations.

Next steps

On this page