​
Workspace (organization)

When you sign up, Histeeria creates a workspace for you. Everything — API keys, decisions, evaluations, profiles — belongs to that workspace.
  • One account owns the workspace by default
  • Team members can be invited to collaborate (see Team)
  • Billing and plan tier apply at the workspace level (see Pricing tiers)

​
Agent profile vs agent_id

These are related but different:
ConceptWhere it livesPurpose
Agent profileHisteeria appNamed entity with role, description, public URL, dashboard
agent_idYour code / SDKString you send on each observe() call
Linking: When you create an API key, link it to a profile. Decisions from that key auto-associate with the profile when agent_id matches or via key linkage rules. You can run multiple agent_id values under one profile (e.g. sub-agents) or one id per profile — choose what fits your architecture.

​
Sub-agents

If you send different agent_id values under the same profile/key, Monitoring shows them as sub-agents with separate decision counts. Useful for multi-agent systems (researcher + writer + reviewer).

​
Public profiles

Profiles can be public — a shareable page showing judgment analytics and builder info. See Public profiles.

​
Multi-environment pattern

Use separate API keys per environment (dev/staging/prod) or separate workspaces. Never share production keys in client-side code. 
Production workspace
├── Profile: Customer Support Bot
│   └── agent_id: support-v2
├── Profile: Internal Ops Agent
│   └── agent_id: ops-agent
└── API keys: prod-key (linked to profiles)