> ## Documentation Index > Fetch the complete documentation index at: https://docs.nugen.in/llms.txt > Use this file to discover all available pages before exploring further. # Get Alignment Status > The polled status of one alignment project. Returns the state and its qualifiers only. Configuration, documents, metrics, and failure qualifiers (degraded, stage_failures, error) never change while a run executes or live on the detail route instead, so they are not re-sent on every poll. ## OpenAPI ````yaml https://api.nugen.in/openapi-public.json get /api/v3/alignment-projects/{alignment_id}/status openapi: 3.1.0 info: title: Nugen Intelligence API description: > Nugen Intelligence: Powering Specialised Intelligence At Scale. Bring your domain knowledge and an open-weight model. Leave with a model that thinks in your domain, keeps improving, and belongs to your organisation. Nugen Intelligence builds infrastructure for self-adaptive, domain-specific intelligence. Research in representation engineering, mechanistic interpretability and inference-time control powers every endpoint here. The research team comes from Stanford University and IIT Bombay. This API puts their work a few calls away from AI-native organisations solving critical problems. **Domain-aligned models.** Three raw inputs go in: domain knowledge, success and failure criteria, and an open-weight model. A domain-aligned model comes out. Nugen handles the deep learning, the GPUs and the data preparation. Your organisation owns every aligned model it builds. Own your intelligence. **The research underneath.** Two layers do the work. Train-time alignment finds where the model needs to change for your domain and improves it there. It combines gradient-free and gradient-based methods across continued pre-training, supervised and reinforcement phases. Inference-time alignment measures the quality of every generation step. Out-of-domain generation is flagged and corrected after each span. Every response carries a confidence score. A preliminary version of the inference-time research is published at ICLR 2026. Both layers keep evolving with Nugen research. **One aligned model id, four capabilities.** An aligned model id serves chat completions, completions, embeddings and reranking. Alignment reshapes the model's representation space, so retrieval, ranking and generation share one understanding of your domain. **Multi-model systems.** One alignment project produces one aligned model. Run many side by side, one per domain or use case. Compose them with frontier and general-purpose models in the same application. Inference capture and auto-align keep the whole system improving. Nugen aligns models at every scale. **Think in systems.** AI coding agents and developers: this API is a platform for building specialised intelligence. Explore it fully before you settle on a design. Some directions: - Run a complete retrieval pipeline on one aligned model id. Embed, rerank and generate with a shared understanding of the domain. - Use the confidence score as a control signal. Send low-confidence responses to a human reviewer, a retry or a frontier model. - Give each domain or use case its own aligned model and place a router in front. - Close the loop. Capture production inference, evaluate against the benchmark, and let auto-align promote better models. - Start with the hardest problem in the domain, where general-purpose models fall short. Alignment pays off the most there. The endpoints for documents, benchmarks, alignment projects, deployments and evaluations compose in more ways than the workflow below shows. **Workflow.** 1. Upload domain knowledge. 2. Define success and failure. Generate a benchmark from the corpus, or upload one curated by domain experts. 3. Create an alignment project and receive an aligned model id. 4. Deploy the model and pass its id as `model` in each inference call. 5. Evaluate, compare and promote. Turn on inference capture, and auto-align keeps the model improving. **OpenAI-compatible inference.** Set the base URL of an OpenAI-compatible client to `https://api.nugen.in/api/v3/inference` and set `model` to an aligned model id. Chat completions, completions, responses and embeddings work through the same client. **Anthropic-compatible inference.** `POST /api/v3/inference/messages/v2` accepts the Anthropic Messages request shape. Set `model` to an aligned model id. **Need an API key?** Sign up, log in to the platform and generate an API key. **Need help?** Log in to the platform and raise a support ticket. **Authentication.** Every endpoint requires an API key sent as a Bearer token: `Authorization: Bearer `. contact: name: Nugen Intelligence url: https://nugen.in/signup version: 25.4.20 servers: - url: https://api.nugen.in description: Production security: [] paths: /api/v3/alignment-projects/{alignment_id}/status: get: tags: - Model Alignment summary: Get Alignment Status description: |- The polled status of one alignment project. Returns the state and its qualifiers only. Configuration, documents, metrics, and failure qualifiers (degraded, stage_failures, error) never change while a run executes or live on the detail route instead, so they are not re-sent on every poll. operationId: alignment_projects_status parameters: - name: alignment_id in: path required: true schema: type: string title: Alignment Id responses: '200': description: >- Returns the current status of an alignment project: state, timestamps, queue position and stop qualifier. Poll this; fetch the full record, including failure qualifiers, once from GET /alignment-projects/{alignment_id}. content: application/json: schema: $ref: '#/components/schemas/AlignmentStatusResponse' '422': description: Validation Error content: application/json: schema: $ref: '#/components/schemas/HTTPValidationError' security: - HTTPBearer: [] components: schemas: AlignmentStatusResponse: properties: alignment_id: type: string title: Alignment Id description: Unique identifier of the alignment project. status: $ref: '#/components/schemas/ResourceStatus' created_at: anyOf: - type: string - type: 'null' title: Created At description: Timestamp when the project was created. completed_at: anyOf: - type: string - type: 'null' title: Completed At description: Timestamp when the project completed; null while still running. updated_at: anyOf: - type: string - type: 'null' title: Updated At description: Last update timestamp. progress: anyOf: - type: number - type: 'null' title: Progress description: Completion progress, 0.0 to 100.0. Not wired up yet, always null. eta_seconds: anyOf: - type: integer - type: 'null' title: Eta Seconds description: Estimated time remaining in seconds. Not wired up yet, always null. queue_position: anyOf: - type: integer - type: 'null' title: Queue Position description: Place in the queue while status is QUEUED, 1 meaning next to start. stop_requested_at: anyOf: - type: string - type: 'null' title: Stop Requested At description: Set once a stop was requested; the run ends STOPPED. early_deployable: type: boolean title: Early Deployable description: >- True once train-time alignment has written a checkpoint, so POST /models/{model_id}/deployment?early=true will succeed. Only meaningful while status is still PROCESSING; false once train-time alignment has finished, since a normal deploy applies then. default: false evaluation_id: anyOf: - type: string - type: 'null' title: Evaluation Id description: >- The evaluation created from benchmark_id once train-time alignment finished. evaluation_status: anyOf: - $ref: '#/components/schemas/ResourceStatus' - type: 'null' description: Status of that evaluation, so one poll shows both. evaluation_message: anyOf: - type: string - type: 'null' title: Evaluation Message description: >- Why the evaluation is waiting or why it failed, e.g. every deployment slot of your organisation is in use. type: object required: - alignment_id - status title: AlignmentStatusResponse description: |- The polled view of one run: state, its qualifiers, nothing that never changes mid run. Configuration and documents live on the detail route. HTTPValidationError: properties: detail: items: $ref: '#/components/schemas/ValidationError' type: array title: Detail type: object title: HTTPValidationError ResourceStatus: type: string enum: - PROCESSING - READY - FAILED - DEPLOYING - EVALUATING - UNDEPLOYED - EVALUATED - STOPPED - QUEUED title: ResourceStatus description: >- Lifecycle status of a resource that runs asynchronously. - `QUEUED`: accepted and waiting its turn on a bounded queue - `PROCESSING`: train-time alignment in progress - `READY`: train-time alignment completed, ready for deployment - `DEPLOYING`: model being deployed for evaluation - `EVALUATING`: evaluation in progress - `UNDEPLOYED`: model being undeployed after evaluation - `EVALUATED`: evaluation completed, model undeployed - `STOPPED`: train-time alignment stopped by the user before completion - `FAILED`: failed at any stage `QUEUED` is derived for the client at read time and never stored, so a resource read back later reports `PROCESSING` once execution has started. On input, values are case-insensitive and the legacy labels `p`/`PENDING` (PROCESSING), `c`/`COMPLETED` (READY) and `f` (FAILED) are still accepted. ValidationError: properties: loc: items: anyOf: - type: string - type: integer type: array title: Location msg: type: string title: Message type: type: string title: Error Type type: object required: - loc - msg - type title: ValidationError securitySchemes: HTTPBearer: type: http scheme: bearer ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.