Install Jentic One Beta

Connect the AIStoryHub API to your agent

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

Generate prose and revise text against an instruction with the AI writing operations

Run a human-grit pass and score a chapter or passage for AI tells from 0 to 100

Create and update stories, chapters, and scenes, with exact-span edits and deterministic find and replace

Maintain world-building entries and pin a story's Voiceprint to keep a consistent voice

GET STARTED

Start building with AIStoryHub API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AIStoryHub API for, with concrete tasks.

★ Agent-Assisted Drafting and Self-Check

An agent writing a chapter can generate prose from the story's outline, revise it against an instruction, run a human-grit pass to roughen machine-smooth text, and then score the result for AI tells before saving. Because the self-check returns a 0 to 100 score, the agent can gate publishing on a threshold and revise again if the passage reads as machine-written. This turns raw generation into a reviewed draft without the agent leaving the manuscript.

Generate a scene from a story's outline, revise it for pacing, run the grit pass, then score it for AI tells and save the chapter only if the score clears a set threshold.

Managing a Story Bible and World

A long manuscript stays consistent when its facts live in structured entries: the API manages a story's bible fields including the outline, world-building entries for people, places, and lore, and a Story Rules library the author can apply. Voiceprints pin the intended voice for a story so later generation matches it, and durable memories persist details across sessions. An agent uses these to keep continuity across many chapters.

Create a world-building entry for a new character, add a Story Rule about their speech, and pin a Voiceprint so later generated scenes match the voice.

Precise, Deterministic Manuscript Edits

When an agent must change wording without disturbing the rest, it can apply an edit that replaces one exact, unique text span in a chapter, or run a deterministic find and replace across one chapter or the whole manuscript. Because the edits are exact and deterministic, the change is auditable and will not silently rewrite nearby text. This suits automated copy edits and consistent renames across a book.

Rename a character across the whole manuscript with a deterministic find and replace, then verify a specific chapter with an exact-span apply-edit.

Key Endpoints

40 endpoints — the aistoryhub api drafts, revises, and edits long-form fiction and manages the manuscript around it from outside the app.

METHOD

PATH

DESCRIPTION

POST

/stories

Create a story

POST

/stories/{id}/chapters

Create a chapter or scene

POST

/stories/{id}/chapters/{chapterId}/apply-edit

Replace one exact, unique text span in a chapter

POST

/ai/generate

Generate prose

POST

/ai/revise

Revise text against an instruction

POST

/ai/self-check

Score a chapter or passage for AI tells from 0 to 100

POST

/voiceprints

Create a Voiceprint

GET

/skills/{slug}/export

Download a skill as a Claude Code SKILL.md file

POST

/stories

Create a story

POST

/stories/{id}/chapters

Create a chapter or scene

POST

/stories/{id}/chapters/{chapterId}/apply-edit

Replace one exact, unique text span in a chapter

POST

/ai/generate

Generate prose

POST

/ai/revise

Revise text against an instruction

POST

/ai/self-check

Score a chapter or passage for AI tells from 0 to 100

POST

/voiceprints

Create a Voiceprint

GET

/skills/{slug}/export

Download a skill as a Claude Code SKILL.md file

Why Jentic?

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

Setup

Wiring the AIStoryHub API by hand means creating a scoped bearer token under Settings, sending Authorization: Bearer ash_ on every call, and tracking which scope each operation needs since write access does not imply read access. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls the story, chapter, and AI operations.

Permission scoping

AIStoryHub puts the story id in the URL path (/stories/{id}), so a rule can pin your agent to one story and the operations you pick: it can read and append chapters to that story and nothing else. The token itself is scoped so write access does not imply read access, and you choose the operations the agent may call, so destructive ones like chapter or Story Rule deletion are not included unless you add them.

Credential isolation

Your AIStoryHub scoped 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 'generate a scene from the outline' or 'score a chapter for AI tells', and Jentic returns the matching AIStoryHub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using AIStoryHub API through Jentic.

What authentication does the AIStoryHub API use?

Per its OpenAPI spec the AIStoryHub API uses an HTTP bearer scheme: you create a scoped token under Settings, Developer API and send it as Authorization: Bearer ash_... on every request. Each operation requires one scope listed via the x-required-scope extension, and scopes are explicit, so a write scope does not grant read access.

Can I generate and revise prose with the AIStoryHub API?

Yes. The AI operations generate prose from a story's context, revise text against an instruction, run a human-grit pass to roughen machine-smooth writing, return structured editorial notes on a chapter, and score a passage for AI tells from 0 to 100. You can chain them to produce a reviewed draft rather than raw output.

What are the rate limits for the AIStoryHub API?

The OpenAPI spec does not publish numeric rate limits for the AIStoryHub API. For current limits and the full per-operation scope list, check the developer documentation at https://aistoryhub.co/developers.

How do I draft a chapter with the AIStoryHub API through Jentic?

Import the AIStoryHub API from the Jentic API Directory, then have your agent search by intent such as 'generate a scene from the outline' and Jentic returns the generate operation with its input schema. The agent generates the prose, revises it, scores it for AI tells, and saves the chapter. 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 AIStoryHub API?

Yes. AIStoryHub carries the story id in the URL path, so write a rule that allows only one story and the read and chapter-append operations, and your agent can draft into that story but cannot delete chapters, Story Rules, or Voiceprints. The token's own scopes reinforce this, since write access does not imply read access, and every call it makes is logged.

Is there an AIStoryHub MCP server?

You don't need an MCP server to give your agent the AIStoryHub API. Jentic connects it directly from the API Directory: import it, store your scoped token once, and your agent calls the story, chapter, and AI operations on demand without loading another server's tool definitions into its context.

How does the AIStoryHub API keep a story's voice consistent?

You create Voiceprints in a library and pin one to a story, so later generation targets that voice, and you can clear or change the pinned Voiceprint at any time. Combined with the Story Rules library and durable memories, this keeps characters, lore, and tone consistent across many chapters.

AIStoryHub API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyAI/MLLanguage Modelsbearer40 EndpointsREST

For Agents

Generate and revise long-form fiction and manage the manuscript behind it. Create stories, chapters, scenes, world-building, Voiceprints, Story Rules, and memories; make exact-span edits; and run AI generation, editorial, grit, and AI-tell self-check passes over text.

Use for: Generate the next scene of a story from its outline, Revise a passage to tighten the pacing, Score a chapter for AI tells before publishing, Create a new story and add its first chapter

Not supported: Does not publish or host a public reading site, process payments, or manage audiobooks. Use for drafting, revising, and managing long-form fiction manuscripts only.

The AIStoryHub API drafts, revises, and edits long-form fiction and manages the manuscript around it from outside the app. Its AI operations generate prose, revise text against an instruction, run a human-grit pass, return structured editorial notes on a chapter, and score a passage for AI tells. Alongside them it manages stories and their bible, chapters and scenes, world-building entries, Voiceprints that pin a story's voice, a Story Rules library, and durable named memories. Exact-span edits and deterministic find and replace let an agent change text precisely, and a skills listing can export a skill as a Claude Code SKILL.md file.

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

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.

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

39%

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.

62%

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

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the AIStoryHub API to your agent

Capabilities

Start building with AIStoryHub API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

AIStoryHub API

Jentic AI Readiness Score

AIStoryHub 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