Projects

For: Platform operators setting up spend attribution and budget tracking by organizational unit.

Providers | Provider Pricing | Credentials | Workloads | Policies | Projects |


Projects are named identifiers that group AI usage across workloads for attribution, analytics, and budget monitoring. Requests tagged with a project appear in spend breakdowns and budget reports grouped by that project.

Navigation: console.axemere.ai/projects

Axemere Console — Projects

Table of Contents


What Projects Are

A project is an immutable ID paired with a human-readable name. Projects are used to:

Projects are organization-scoped and available across all workloads.


Creating a Project

  1. Click New Project.
  2. Enter a Project ID: a short, lowercase slug that will appear in request headers and analytics (e.g., billing-service, ml-experiments). The ID cannot be changed after creation.
  3. Enter a Project Name: a human-readable display name.
  4. Optionally add a Description.
  5. Click Create.

If you land on the Projects page via a link from elsewhere in the console (e.g. discovering an unregistered project ID in traffic), the New Project form may open pre-filled with that ID and a derived name — review and adjust before saving.


Editing and Deleting Projects

  • Edit: Click the Edit (pencil) icon next to a project to update its display name or description. The ID cannot be changed.
  • Delete: Click the Delete (trash) icon and confirm. Deleting a project does not delete historical records tagged with that project ID; they will show the bare ID without a name.
  • Columns (Name, Project ID, Created, Last used) are sortable — click a header to sort, click again to reverse.

Search: Use the search box to filter the project list by name or ID when you have many projects.


Default Project

One project can be marked default for the org (the star icon on a project row, or "Set as default" in its menu). This is a display/UX convenience elsewhere in the console (e.g. pre-selecting a project in pickers) — it does not change how requests without an explicit project tag are attributed or reported; those still appear as unattributed.


Tagging Requests with a Project

Pass the project ID as a request header:

X-Axemere-Project: billing-service

Or encode it in the proxy URL path (supported on some SDK configurations). See Identity and Attribution for the full attribution header reference.


Viewing Project Data

Project data flows into several analytics views:

  • Analytics → Spend — "By Project" tab shows requests, cost, and tokens per project
  • Govern → Budgets — per-project spend vs. configured monthly limits
  • Attribution — project dimension alongside workloads, accounts, and customers
  • Records — filter execution records by project

Related: | Analytics → Spend | Govern → Budgets | Policies