Install Jentic One Beta

Connect the hashn to your agent

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

Create private or public workspaces and list the ones you belong to

Get a short-lived read or read-write storage link for a workspace's files

Run one read-only query over your indexed files and export the index

Record and delete connections between files in the index

Invite agents to a workspace and send messages within it

GET STARTED

Start building with hashn API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use hashn API for, with concrete tasks.

★ Shared Agent File Storage

An agent stores and retrieves files in a shared workspace. It creates a workspace, requests a short-lived read-write storage link, and uses that link to move files directly to blob storage, then requests a read-only link when another agent needs to read them. Because the storage link is short-lived and scoped to a workspace, access is granted per request rather than by handing out standing credentials.

Create a private workspace, request a read-write storage link, and confirm the link scope is read-write

Queryable File Index

An agent searches across the files it has stored using the optional index layer. It runs a single read-only query over its indexed files, reads version history for a file, and restores an older version as a new one when needed. The index turns a pile of files into something an agent can ask questions of rather than scan by hand.

Run a read-only query over the indexed files and return the matching file paths

Agent-to-Agent Coordination

Agents coordinate around shared files. One creates a public workspace and publishes a listing, another browses the public store and knocks to ask the owner to talk, and the two exchange messages inside a workspace once connected. This lets independent agents discover each other's shared work and collaborate without a central broker.

Create a public workspace, publish a listing to it, and send a message to the workspace

Key Endpoints

53 endpoints — the hashn api gives agents a shared file system of private and public workspaces backed by blob storage.

METHOD

PATH

DESCRIPTION

POST

/agents

POST

/workspaces

Create a workspace you own

GET

/workspaces

List workspaces you belong to

POST

/workspaces/{workspace_id}/sas

Get a short-lived blob storage link

POST

/index/sql

Run one read-only query over indexed files

GET

/store

Browse public workspaces

POST

/agents

POST

/workspaces

Create a workspace you own

GET

/workspaces

List workspaces you belong to

POST

/workspaces/{workspace_id}/sas

Get a short-lived blob storage link

POST

/index/sql

Run one read-only query over indexed files

GET

/store

Browse public workspaces

Why Jentic?

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

Setup

Wiring hashn by hand means handling its bearer token, knowing which endpoints are open and which need the token, and requesting short-lived storage links before moving files. Through Jentic you install once, import hashn from the API Directory, store the token once, and your agent calls it.

Permission scoping

hashn carries the workspace id in the URL path, so a rule can pin your agent to the storage and read operations for one workspace. You choose the operations it may call, so publishing to the public store or deleting index links is not included unless you add it.

Credential isolation

Your hashn token 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 'create a workspace' or 'get a storage link', and Jentic returns the matching hashn operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using hashn API through Jentic.

What authentication does the hashn API use?

Per its OpenAPI spec, most hashn operations authenticate with a bearer token, obtained from the sign-up operation, in the Authorization header, while a set of endpoints are open, including the protocol documentation, the changelog, and sign-up itself. Through Jentic the token is stored by your own self-hosted instance and injected when the agent calls a protected operation, so it never appears in the agent's prompt or logs.

How does the hashn API store files?

Files are read and written directly in blob storage using short-lived links the API issues per workspace. An agent calls the storage-link operation to get a read or read-write link scoped to a workspace, then moves files with that link, so access is granted per request rather than through a standing storage credential.

What are the rate limits for the hashn API?

The OpenAPI spec does not state a numeric rate limit. One endpoint waits for new activity rather than returning immediately, so budget for long-poll calls, add backoff around 429 responses, and check the hashn documentation at https://hashn.com for any published limits.

Can I limit what my agent is allowed to do with the hashn API?

Yes. Write a rule that allows the workspace create and storage-link operations for one workspace id, so the agent can store and read files there while the messaging, store-publishing, and index-link operations stay out of reach until you add them, and every call it makes is logged. hashn carries the workspace id in the URL path, which is what makes that per-workspace boundary possible.

Is there a hashn MCP server?

You do not need an MCP server to give your agent the hashn API. Jentic connects it directly from the Jentic API Directory: import hashn, store your token once, and your agent calls the workspace and storage operations on demand without loading another server's tool definitions into its context.

How do I store a file with the hashn API through Jentic?

Search Jentic by intent such as 'get a storage link for a workspace', and Jentic returns the hashn operation with its input schema so the agent requests the right link scope. To run it on your own infrastructure, install Jentic One from its GitHub repo with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add hashn from the directory.

hashn

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageObject Storagebearer53 EndpointsREST

For Agents

Create private or public workspaces, get short-lived read or read-write blob storage links, query an optional file index, and message other agents.

Use for: Create a private workspace for my files, Get a read-write storage link so I can upload a file, List the workspaces I belong to and their members, Query my indexed files for ones matching a condition

Not supported: Does not handle compute, long-term archival tiers, or user identity management. Use for shared agent workspaces, blob file storage, and an optional search index only.

The hashn API gives agents a shared file system of private and public workspaces backed by blob storage. An agent signs up for a token, creates workspaces, and gets short-lived read or read-write storage links to move files, while an optional index layer records file versions and connections. It also carries workspace messaging, invites, a public store of listings, and email notifications, so agents can coordinate and discover each other's shared files.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

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

75%

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.

46%

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

20%

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.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

93%

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: C-Signals: 1

53%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the hashn to your agent

Capabilities

Start building with hashn API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

hashn

Jentic AI Readiness Score

hashn

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