Niuro public API

Quickstart

No API key is required. Request the live collection directly:

curl --fail-with-body \
  --header 'Accept: application/json' \
  https://niuro.io/api/v1/jobs/

A successful response contains success: true and a jobs array. Poll responsibly and treat a role missing from the latest successful response as unavailable. Open a one-role JSON response to verify the endpoint from the current origin.

Contracts and discovery

• OpenAPI 3.1 description for typed clients and function tooling.
• Public Jobs API guide for the human-readable contract.
• RFC 9727 API catalog for service discovery.
• llms.txt for the agent-readable site map and when-to-use guidance.

Errors and recovery

The versioned API returns RFC 9457 Problem Details as application/problem+json. Every problem includes a stable code, HTTP status, detail, instance path, and resolution link without exposing internal diagnostics.

Invalid request

A 400 means a query parameter is invalid; a 405 means the route received an unsupported method.

Route not found

Unknown paths under /api/ return a JSON 404 with a recovery link to this portal.

Job not found

A job 404 means the role is closed, unavailable, or does not exist. Recover through the current roles directory or the versioned jobs feed.

Jobs temporarily unavailable

A 503 is not a closed-role signal. Honor Retry-After and try the current roles directory again later.

Rate limits

The Worker enforces a 100-request, 60-second quota per client IP at each Cloudflare location. Responses publish RateLimit-Policy, quota metadata, and Retry-After on 429. Cloudflare's distributed counters are eventually consistent, so agents must treat the headers as throttling guidance rather than a global capacity guarantee.

Versioning and deprecation

The stable contract uses URL-path versioning at /api/v1/. Additive fields can appear within v1, so clients must ignore unknown properties. Breaking changes use a new major path such as /api/v2/.

Niuro documents a deprecation before emitting the standardized Deprecation header and provides at least 90 days before a published Sunset date. Read the API lifecycle policy. The v1 endpoint is current, so it emits neither lifecycle header today.

Scope

There is no separate sandbox because the public endpoint is read-only and carries no authentication. There are no public endpoints for browsing candidates, reading private evidence, or submitting applications. For a company hiring need, use the self-serve intake. For a current role, follow its publicUrl.

Agent-readable pages

Use the clean Markdown mirrors when page copy, rather than live role data, answers the task:

• Companies page in Markdown
• Talent page in Markdown
• FAQ in Markdown