canonical: https://jentic.com/apis/noctaracorp.com/noctaracorp

# Noctaracorp Noctara Human Registry

The Noctara Human Registry API checks whether a person is present and continuous by reading a consented, person-owned, append-only behavioral record. A check by the person's tag returns four claims, is_human, is_continuous, has_deviated, and stands_behind, along with provenance such as beat counts, distinct weeks, and drift observations. Claims are returned only when the person has granted the calling organization; otherwise the response is marked not visible with a pending_consent status instead of a false answer. A zero-auth demo endpoint returns a fixture record so you can see the response shape before you have a license key.

## For AI agents

Check the four Noctara claims (is_human, is_continuous, has_deviated, stands_behind) and their provenance for a person who has granted your organization access, or fetch a fixture response to learn the shape without a key.

## Scope

Does not verify government IDs, run face or document biometrics, or collect consent on the person's behalf. Use for reading consented Noctara presence and continuity claims only.

## Capabilities

- Check the is_human, is_continuous, has_deviated, and stands_behind claims for a person by their tag
- Read the provenance behind each check, including beats, distinct_weeks, sources, and drift_observations
- Tell a missing grant apart from a negative result through the visible flag and pending_consent status
- Fetch a zero-auth fixture record from the registry demo endpoint to build and test response handling

## Use cases

### Agent presence check through Jentic

An agent screening a new marketplace contributor searches Jentic for a human presence check, receives the registryCheck schema, and calls it with the contributor's tag. If visible is true it reads the four claims and their provenance; if visible is false with status pending_consent, it asks the contributor to grant access instead of treating the result as a failure.

Example prompt: Call GET `/api/v1/registry` with tag='ab12cd34'; if visible is true report is_human and is_continuous with provenance.distinct_weeks, otherwise report that consent is pending

### Continuity checks for trusted contributors

Communities and platforms that give extra trust to long-standing members can use the is_continuous claim, which the spec defines as a record spanning at least two distinct weeks, along with has_deviated, which flags a drift observation in the record. Both come with provenance so a reviewer can see what the claim rests on.

Example prompt: Call GET `/api/v1/registry` for tag='member77' and flag the member for review if has_deviated is true or provenance.drift_observations is above zero

### Prototype integration with fixture data

Before a license key is issued, developers can build their parsing and decision logic against GET `/api/v1/registry-demo`, which needs no authentication and returns a fixture record in the same RegistryResponse shape as a real check. No real person is behind the fixture.

Example prompt: Call GET `/api/v1/registry-demo` and list each field in the response with its type to generate a parser

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v1/registry` | Check the four claims for a consented person |
| GET | `/api/v1/registry-demo` | Get a zero-auth fixture response |

## Key resources

- **Registry check** — Return the four claims and provenance for a consented person identified by tag
- **Registry demo** — Return a fixture record in the real response shape, with no key required

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 90 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 52 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 81 / 100
- **View full report:** https://jentic.com/apis/noctaracorp.com/noctaracorp/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Noctara by hand means requesting a license key, sending it as a bearer token on the registry check, and handling the consent-pending response shape yourself. Through Jentic you install once, import Noctara from the API Directory, store the license key once, and your agent calls it.
- **Permission scoping:** Noctara has two operations, and the person's tag travels as a query parameter rather than a path id, so rules bound which operation your agent may call, not which person it checks. You choose the operations it may call, so live checks against real people are not included unless you add them.
- **Credential handling:** Your Noctara license key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check whether a person is human' or 'verify a consented person', and Jentic returns the matching Noctara operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Onfido API** — Document and biometric identity verification
- **Veriff API** — Identity verification sessions with document and face checks
- **Auth0 Authentication API** — User login and sessions that can sit in front of a Noctara check

## FAQ

### What authentication does the Noctara Human Registry API use?

Per its OpenAPI spec, GET `/api/v1/registry` requires a bearer license key (format noctara_lk_...), which you can request from the Noctara developers page. GET `/api/v1/registry-demo` needs no authentication. A real check also needs the person's recorded consent to your organization. Through Jentic, the license key is stored encrypted by your own Jentic One instance and injected at call time.

### What happens if the person has not granted my organization access?

The check still returns 200, but visible is false, status is pending_consent, and claims is null. The spec states this is never a false no, so treat it as missing consent, not a failed check.

### What are the rate limits for the Noctara Human Registry API?

The OpenAPI spec does not specify rate limits. Check https://noctaracorp.com/developers for current limits.

### How do I run a Noctara presence check through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add Noctara from the Jentic API Directory, and store your license key. Your agent searches for 'check whether a person is human', then calls GET `/api/v1/registry` with the person's tag. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the Noctara Human Registry API?

Yes. During development, write a rule that allows only GET `/api/v1/registry-demo`, so the agent works against fixture data and never sends a real tag. When you go live, add GET `/api/v1/registry`, and every check the agent makes is logged against that rule.

### Is there a Noctara MCP server?

You don't need an MCP server to give your agent the Noctara Human Registry API. Jentic connects it directly from the API Directory: import it, store your license key once, and your agent calls it.

### Is the is_human claim a biometric check?

No. The spec describes is_human as a presence signal over an accruing record, set from at least two beats or a measured live typing session, and states it is not a calibrated biometric. Each claim is true when evidenced, false only when evidenced negative, and null when not established.