Install Jentic One Beta

Connect the Noctara Human Registry to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Noctara Human Registry, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnoctaracorp.com%2Fnoctaracorp" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fnoctaracorp.com%2Fnoctaracorp" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Noctara Human Registry API.

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

GET STARTED

Start building with Noctara Human Registry API

Explore with Jentic One

View OpenAPI Document

★ 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.

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.

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.

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

Key Endpoints

2 endpoints — the noctara human registry api checks whether a person is present and continuous by reading a consented, person-owned, append-only behavioral record.

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

GET

/api/v1/registry

Check the four claims for a consented person

GET

/api/v1/registry-demo

Get a zero-auth fixture response

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Noctara Human Registry API through Jentic.

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.

Noctaracorp Noctara Human Registry

AI ReadinessAI-Aware (B+)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthIdentity Verificationbearer2 EndpointsREST

For 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.

Use for: I need to check whether the person behind this tag is a consenting human, Check whether a contributor's record spans more than one week, Retrieve the provenance behind a Noctara check, Find out whether a person has granted my organization access yet

Not supported: 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.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

38%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

46%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

81%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Noctara Human Registry to your agent

Capabilities

Use Cases

Start building with Noctara Human Registry API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Noctaracorp Noctara Human Registry

Jentic AI Readiness Score

Noctara Human Registry

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness