Install Jentic One Beta

Connect the harvis.dev API to your agent

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

Create sites and list the account's sites newest first

Replace every file of a site in one deploy, or add and overwrite individual files

Rename a site or change its web address

Read a site's form submissions, export them as CSV, and mark them read

Manage account API keys and rotate a site's deploy token

GET STARTED

Start building with harvis.dev API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use harvis.dev API for, with concrete tasks.

★ Programmatic Site Deploys

An agent publishes and updates a static site without a dashboard. It creates the site, deploys the full set of files, and later replaces individual files when only part of the site changes. Because a full deploy and a partial file add are separate operations, the agent picks the cheapest update for each change instead of redeploying everything.

Create a site, deploy its files, then add a single overwritten file without touching the rest of the site

Form Submission Pipeline

An agent collects and processes the form submissions a hosted site receives. It lists submissions newest first, reads a submission, exports the set as CSV for downstream tools, and marks unread ones as read once handled. Keeping submissions as a per-site resource lets the agent run an inbox-style workflow against each site.

List a site's submissions, export them as CSV, and mark the unread ones as read

Credential and Token Rotation

An agent keeps a site's deploy credentials current. It lists the account's API keys, creates a new one for a scoped automation, and rotates a site's deploy token so an old token stops working immediately. Running rotation through the API lets an agent respond to a rotation schedule without manual dashboard steps.

Create a new API key, rotate the deploy token for a site, and confirm the site is still reachable

Key Endpoints

23 endpoints — the harvis api hosts static sites and deploys files to them over http.

METHOD

PATH

DESCRIPTION

GET

/api/v1/sites

List the account's sites

POST

/api/v1/sites

Create a site from a folder of files

POST

/api/v1/sites/{id}/deploy

Replace every file of a site

GET

/api/v1/sites/{id}/submissions

List a site's form submissions

POST

/api/v1/sites/{id}/deploy-token

Issue a new deploy token for a site

POST

/api/v1/keys

Create an API key

GET

/api/v1/sites

List the account's sites

POST

/api/v1/sites

Create a site from a folder of files

POST

/api/v1/sites/{id}/deploy

Replace every file of a site

GET

/api/v1/sites/{id}/submissions

List a site's form submissions

POST

/api/v1/sites/{id}/deploy-token

Issue a new deploy token for a site

POST

/api/v1/keys

Create an API key

Why Jentic?

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

Setup

Wiring Harvis by hand means handling its bearer API key, tracking per-site deploy tokens, and choosing between a full deploy and a partial file add. Through Jentic you install once, import Harvis from the API Directory, store the key once, and your agent calls it.

Permission scoping

Harvis puts the site id in the URL path, so a rule can pin your agent to the deploy and submission operations for one site. You choose the operations it may call, so destructive ones like site deletion or submission purging are not included unless you add them.

Credential isolation

Your Harvis 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 'deploy a static site' or 'read form submissions', and Jentic returns the matching Harvis operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using harvis.dev API through Jentic.

What authentication does the Harvis API use?

Per its OpenAPI spec, the Harvis API accepts a bearer API key, prefixed hvs_, in the Authorization header, or a session cookie for dashboard-originated calls. Through Jentic the bearer key is stored by your own self-hosted instance and injected when the agent calls an operation, so it never appears in the agent's prompt or logs.

Can I deploy a static site with the Harvis API?

Yes. An agent creates a site, then deploys with an operation that replaces every file of the site, or adds and overwrites individual files to leave the rest in place. There is also a deploy-from-zip operation and a per-site deploy token it can rotate when a credential needs replacing.

What are the rate limits for the Harvis API?

The OpenAPI spec does not state a numeric rate limit. Add retry and backoff around 429 responses when deploying or polling submissions, and check the Harvis documentation at https://harvis.dev for any published limits.

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

Yes. Write a rule that allows the deploy and submission read operations for one site id, so the agent can publish and read submissions for that site while the site-delete and key operations stay out of reach, and every call it makes is logged. Harvis carries the site id in the URL path, which is what makes that per-site boundary possible.

Is there a Harvis MCP server?

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

How do I deploy a site with the Harvis API through Jentic?

Search Jentic by intent such as 'deploy a static site', and Jentic returns the Harvis deploy operation with its input schema so the agent sends the right files. 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 Harvis from the directory.

harvis.dev API

AI ReadinessFoundational (D+)49/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsCi Cdbearer, apiKey23 EndpointsREST

For Agents

Create and manage static sites, deploy files or a zip to them, rotate deploy tokens, and read, export, and mark a site's form submissions.

Use for: Create a new site from a folder of files, Deploy an updated set of files to one of my sites, List all sites on my account, Export a site's form submissions as CSV

Not supported: Does not handle domain registration, server-side runtimes, or builds from a source repository. Use for hosting static sites, deploying files, and reading form submissions only.

The Harvis API hosts static sites and deploys files to them over HTTP. An agent lists and creates sites, replaces every file of a site in one deploy or adds and overwrites individual files, renames a site or changes its web address, and imports a single page from a known source. It also reads a site's form submissions, exports them as CSV, marks them read, and manages the account's API keys and per-site deploy tokens.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

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

100%

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.

50%

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

35%

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.

57%

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

55%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the harvis.dev API to your agent

Capabilities

Start building with harvis.dev API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

harvis.dev API

Jentic AI Readiness Score

harvis.dev 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