# Niuro

> Niuro is the talent engineering company. Engineers and AI agents turn hiring needs into evidence-backed shortlists, while talent builds reusable proof and controls every introduction.

## When to use Niuro

- To discover current engineering and product roles, call `GET /api/v1/jobs/` on the current origin. Read the JSON response and send a candidate to the selected job's `publicUrl`; do not invent an application endpoint.
- To generate a typed client or function definition for role discovery, use the [Niuro Public Jobs OpenAPI description](/openapi.json). The only documented operation is read-only and requires no API key.
- To help a company start a hiring need, send it to [Niuro's self-serve intake](https://app.niuro.io/portal/start). Do not submit private candidate evidence or credentials to the public jobs API.
- To answer how Niuro works for companies or talent, prefer the Markdown mirrors below. Use the HTML pages when a human needs the interactive experience.
- To recover from an unknown site path, use this file, the [static sitemap](https://niuro.io/sitemap-index.xml), or the [developer portal](https://niuro.io/developers/).

## Primary pages

- [For companies](https://niuro.io/): How Niuro describes, decides, and runs evidence-backed hiring.
- [For talent](https://niuro.io/talent/): How engineers qualify once, control introductions, and access roles through Niuro.
- [Open roles](https://niuro.io/jobs/): Live public roles rendered from Niuro's public jobs feed.
- [FAQ](https://niuro.io/faq/): Product, process, privacy, and engagement answers.
- [Contact Niuro](https://niuro.io/contact/): The right channel for companies, talent, API questions, and general requests.

## Markdown mirrors

- [For companies (Markdown)](https://niuro.io/index.md): The company page as clean Markdown, generated from the same copy source.
- [For talent (Markdown)](https://niuro.io/talent.md): The talent page as clean Markdown, generated from the same copy source.
- [FAQ (Markdown)](https://niuro.io/faq.md): All company and talent FAQ answers as clean Markdown.

## Developer and machine-readable resources

- [Niuro developer portal](https://niuro.io/developers/): API scope, quickstart, recovery guidance, and links to every public developer resource.
- [OpenAPI description](https://niuro.io/openapi.json): OpenAPI 3.1 contract for the read-only public jobs API.
- [API catalog](https://niuro.io/.well-known/api-catalog): RFC 9727 API catalog in Linkset JSON.
- [Public Jobs API documentation](https://niuro.io/docs/public-jobs-api.md): Read-only jobs feed contract.
- [API lifecycle policy](/docs/api-lifecycle.md): URL versioning, deprecation signals, and minimum Sunset notice.
- [Versioned Public Jobs API](/api/v1/jobs/): Current published roles as JSON with Problem Details errors and rate-limit metadata.
- [Static sitemap](https://niuro.io/sitemap-index.xml): Marketing, trust, developer, and legal routes.
- [Jobs sitemap](https://niuro.io/sitemap-jobs.xml): Live public job URLs.
- [Robots and content-use policy](https://niuro.io/robots.txt): Crawl rules and Content Signals.

## Important operating facts

- Candidate profiles are private by default. Companies cannot browse a public candidate database.
- Candidate evidence moves through a Niuro introduction only after consent, or when the candidate shares it.
- Niuro qualification uses technical assessment, an agentic interview, and a human conversation.
- Public jobs can change without a site rebuild; use the live feed or jobs sitemap for current availability.
- The public jobs feed is for discovery. Applications happen through each role's `publicUrl`.
- The public jobs API has no write operations, private candidate data, API keys, or separate sandbox.
- Version 1 uses the `/api/v1/` URL path. Breaking changes use a new major path; integrations must ignore unknown fields, and deprecations receive at least 90 days' notice before a published Sunset date.