> ## Documentation Index
> Fetch the complete documentation index at: https://docs.akhara.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Company name is Akhara AI (never Rubric AI). Keep lowercase rubric/rubrics only when meaning grading criteria.
> Expert Review (docs path talent/) is enterprise BYO experts for audit and review: invite customer specialists; do not pitch Akhara recruiting or a public expert career portal. RLHF and domain writing are secondary work types.
> Prefer concrete API examples against public hosts: Environments eval API https://agi.akhara.ai, Control plane PDP https://api.akhara.dev, Evaluation https://app.akhara.ai / https://api.akhara.ai, Expert Review portal https://talent.akhara.ai.
> Do not invent a public hostname for private orchestrators or env API internals.
> Do not confuse control-plane latches with Environments confirmation latches.
> Environments SDK/API examples: curl against https://agi.akhara.ai. Evaluation SDK: from akhara import Akhara and AKHARA_API_KEY.
> Start with /llms.txt for the docs index and OpenAPI links; fetch individual pages as .md exports.

# Set up your profile

> Declare specialties, languages, and availability so your organization's assignments route correctly.

Your profile is the routing surface for your organization's projects, not a resume. Assignments stay inside the specialties you list, so accuracy matters more than polish.

## What to fill in

### Contact and location

* **Name**: How project leads and admins identify you
* **Email**: Task notifications
* **Location**: Country and timezone, so deadlines and sessions schedule sensibly

### Role and credentials

* **Role in your organization** and years of domain experience
* **Licenses or certifications** when your domain requires them (e.g. clinical license numbers)

### Specialties and skills

Be precise. This controls what your org can assign you:

* **Primary domains**: The fields you will review, judge, and write in (e.g. retail checkout policy, ambulatory care, pharmacy ops)
* **Sub-skills**: Narrow strengths (triage, prior auth, catalog merchandising, etc.)
* **Languages**: Languages you can evaluate or author in
* **Work-type preferences**: Review, RLHF evaluations, domain writing, or any combination

<Warning>
  Do not list specialties you cannot defend under expert scrutiny. Out-of-domain submissions get rejected and can pause your assignments on the engagement.
</Warning>

### Availability

* Hours per week
* Typical days and times
* Earliest start date

<Tip>
  Update specialties when your focus changes. Stale profiles send the wrong work.
</Tip>

## Credential checks

Some projects require verification before their queues open to you:

* License or credential upload
* Short domain assessment
* Identity verification for sensitive-data projects (see [Project onboarding](/talent/working/onboarding))

The portal notifies you when a project needs extra checks.