Install Jentic One Beta

Connect the Daystruct API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Daystruct API, 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%2Fdaystruct.ai%2Fdaystruct" | 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%2Fdaystruct.ai%2Fdaystruct" | 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 Daystruct API.

Read provenance-backed facts, historical observations, aliases, and relationships for an entity

Look up software compatibility claims, vulnerability exposure, and support lifecycle from versioned databanks

Discover capabilities on the network and acquire a version-pinned source kit with its downloadable artifact

Resolve capability bundles with version-pinned members and check that a set of capabilities works together

GET STARTED

Start building with Daystruct API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Daystruct API for, with concrete tasks.

★ Grounding an AI Agent in Verified Evidence

An AI agent connected to Daystruct through Jentic can resolve canonical facts and their provenance before answering, rather than relying on unsourced recall. It can read an entity's facts, aliases, and relationships and trace each claim to its source, so the agent's output cites where a value came from. Resolved values are presented as best-supported current interpretations, which the agent can surface honestly instead of as absolute truth.

Read the canonical facts and provenance for a given entity id, then summarise the answer with the source behind each value

Software Vulnerability and Support Checks

Daystruct's versioned databanks let a developer or agent resolve which known vulnerabilities affect a specific package version, whether a product version is still supported as of now, and how software compatibility claims line up. This turns scattered software evidence into direct lookups for dependency review and upgrade planning without scraping advisories by hand.

Resolve the exposure for version 2.14.1 of a named package and report any known vulnerabilities that affect it

Acquiring Reusable Capability Kits

Developers can discover capabilities published on the Daystruct network, inspect a capability profile by any of its names, and acquire a specific source implementation version with a downloadable artifact. Bundles resolve their version-pinned members, and compatibility checks and verified locks confirm a chosen set works together before it is pulled into a project.

Look up a capability profile by name, acquire its latest inspected version, and download the source artifact for this account

Developer-Owned Agent Identity Registration

Daystruct lets developers register durable agent identities linked to an API key and declare the capabilities each identity supports. Registered agents are declarations only and are not routable, so this manages identity and capability metadata rather than dispatching work. Identities can be listed, read, and updated under the same key that created them.

Register a new developer agent identity with its declared capabilities, then read it back to confirm the link to the API key

Key Endpoints

82 endpoints — the daystruct api provides read-only access to provenance-backed evidence about entities, including canonical facts, historical observations, relationships, and the sources behind each claim.

METHOD

PATH

DESCRIPTION

GET

/api/v1/entities/{id}/facts

List canonical facts and provenance for an entity

GET

/api/v1/databanks/{slug}/exposure

Resolve vulnerabilities affecting a package version

GET

/api/v1/software/claims

Query version-scoped software compatibility claims

GET

/api/v1/capabilities

List capabilities published on the network

POST

/api/v1/capabilities/{ref}/acquire

Acquire an inspected source implementation version

POST

/api/v1/compat/check

Check whether a set of capabilities works together

POST

/api/v1/agents/register

GET

/api/v1/events

Consume the durable canonical change feed

GET

/api/v1/entities/{id}/facts

List canonical facts and provenance for an entity

GET

/api/v1/databanks/{slug}/exposure

Resolve vulnerabilities affecting a package version

GET

/api/v1/software/claims

Query version-scoped software compatibility claims

GET

/api/v1/capabilities

List capabilities published on the network

POST

/api/v1/capabilities/{ref}/acquire

Acquire an inspected source implementation version

POST

/api/v1/compat/check

Check whether a set of capabilities works together

POST

/api/v1/agents/register

Why Jentic?

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

Setup

Wiring Daystruct by hand means handling its bearer API-key auth plus basic operator credentials for the monitor surface, its scoped permissions, and its per-call pricing quotes. Through Jentic you install once, import Daystruct from the API Directory, store the key once, and your agent calls it.

Permission scoping

Daystruct is mostly read-only evidence, and its write paths (registering agent identities, submitting requests, acquiring paid capabilities) are separate operations. A rule can let your agent read entities, facts, and databanks while identity registration and capability acquisition stay out of its reach. You choose the operations it may call, so nothing that spends credits runs unless you add it.

Credential isolation

Your Daystruct API 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 'look up vulnerabilities for a package version' or 'read an entity's provenance', and Jentic returns the matching Daystruct operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Daystruct API through Jentic.

Is there a Daystruct MCP server?

Daystruct exposes an MCP endpoint of its own, but you don't need to wire up a separate MCP server to use it from your agent. Jentic connects Daystruct directly from the API Directory: import it, store your API key once, and your agent calls the evidence, databank, and capability operations, discovered on demand so no extra tool definitions bloat its context.

Can I limit what my agent is allowed to do with Daystruct?

Yes. Write a rule that allows the evidence and databank read operations but not agent registration or capability acquisition, so the agent can ground its answers in provenance-backed facts without spending credits or changing your account, and every call it makes is logged.

What authentication does the Daystruct API use?

Per its OpenAPI spec, the Daystruct API uses a bearer API key in the ds_live_ format for registered-agent and request operations, with HTTP basic operator credentials for the monitor refinery surface. Public evidence reads are allowed without a key, and keys are scoped in the developer portal. Through Jentic the key is stored encrypted by your own Jentic One instance and injected only at call time.

Can I look up software vulnerabilities with the Daystruct API?

Yes. The databank exposure operation resolves which known vulnerabilities affect a specific version of a package, the vulnerability lookup reads one vulnerability by its identifier, and the support operation reports whether a product version is still supported as of now. These are read-only lookups against version-scoped databanks.

What are the rate limits for the Daystruct API?

The OpenAPI spec does not specify request-rate limits; instead it publishes per-call prices and a margin-policy quote through the pricing operation, and request operations return a credit quote before you commit. Check the developer portal at daystruct.ai/portal for current pricing and quota details.

How do I ground my agent in provenance-backed evidence through Jentic?

Call the entity facts operation to read canonical values and their sources, or the databank operations for software and vulnerability questions, then have the agent cite each source in its answer. In Jentic, search for 'look up provenance-backed evidence about an entity', store your API key once, and the agent runs the read. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Daystruct API

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsPackage Registrybearer, basic82 EndpointsREST

For Agents

Read provenance-backed facts about entities, look up software vulnerabilities and compatibility, and acquire version-pinned capability kits. Manages developer-owned agent identities across 82 endpoints.

Use for: Look up the canonical facts and provenance for an entity, Find which known vulnerabilities affect a specific version of a package, Check whether a set of capabilities works together, I want to acquire a capability source kit and download its artifact

Not supported: Does not route tasks to agents, dispatch jobs, or execute capabilities for you. Use for reading provenance-backed evidence and acquiring versioned capability kits only.

The Daystruct API provides read-only access to provenance-backed evidence about entities, including canonical facts, historical observations, relationships, and the sources behind each claim. It resolves software compatibility, vulnerability exposure, and support-lifecycle questions from versioned databanks, and lets developers discover, acquire, and version-pin reusable capability kits with verified compatibility locks. It also manages developer-owned agent identities linked to an API key; registered capabilities are declarations only, as the API has no task-dispatch surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C+Signals: 4

89%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

50%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

47%

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: FSignals: 4

39%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

51%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

89%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

35%

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: CSignals: 1

53%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Daystruct API to your agent

Capabilities

Start building with Daystruct API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Daystruct API

Jentic AI Readiness Score

Daystruct API

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