Random Lovecraft
56
AI ReadinessFoundational (C)56/100
Developer ToolsSource Controlnone4 EndpointsREST
For Agents
Programmatically a random sentence, a specific sentence. Covers 4 operations.
Use for: I need to a random sentence, I want to a specific sentence, Search for random sentences from a specific book, Find all all books
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Random sentences from the complete works of H.P. Lovecraft. CORS-enabled. The API exposes 4 endpoints.
Install Jentic One Beta
Connect the Random Lovecraft to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Random Lovecraft, 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.
1
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%2Frandomlovecraft.com%2Frandomlovecraft" | sh2
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%2Frandomlovecraft.com%2Frandomlovecraft" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Random Lovecraft API.
A random sentence
Random sentences from a specific book
List all books
Access Random Lovecraft developer tools resources via REST API
Use Cases
Patterns agents use Random Lovecraft API for, with concrete tasks.
★ Developer Tools Operations
Use the Random Lovecraft to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including a random sentence, a specific sentence, random sentences from a specific book.
Call GET /sentences to a random sentence
Automated Sentences Management
Automate sentences operations by combining multiple Random Lovecraft endpoints. Agents can a specific sentence and then random sentences from a specific book in a single workflow.
Call GET /sentences/{id} to a specific sentence, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Random Lovecraft endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'a random sentence', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — random sentences from the complete works of h.
METHOD
PATH
DESCRIPTION
GET
/sentences
A random sentence
GET
/sentences/{id}
A specific sentence
GET
/books/{id}/sentences
Random sentences from a specific book
GET
/books
List all books
GET
/sentences
A random sentence
GET
/sentences/{id}
A specific sentence
GET
/books/{id}/sentences
Random sentences from a specific book
GET
/books
List all books
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
R
Random Lovecraft
- Foundational (C)56/100
100
Foundational Compliance61
Developer Experience & Jentic Compatibility39
AI-Readiness & Agent Experience94
Agent Usability100
Security25
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
61
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
19%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
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.
39
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
8%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
100
Security
Trust, risk posture, and security compliance.
Grade: A+Signals: 1
100%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
25
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: FSignals: 1
25%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Random Lovecraft API by hand still means writing a client for its sentence and book endpoints and paging through results yourself, even though it needs no auth. Through Jentic you install once, import the Random Lovecraft API from the API Directory, and your agent calls it with no credential to manage.
Permission scoping
Random Lovecraft puts the book id in the URL path (/books/{id}/sentences), so a rule can pin your agent to reading one book, but every endpoint is read-only. You limit the agent to the operations it needs, such as fetching random sentences, and there are no write or destructive operations to grant.
Credential isolation
The Random Lovecraft API requires no credential, so there is no secret to store. Any configuration your Jentic One instance holds stays out of the agent's prompt, logs, and context.
Intent-based discovery
Agents search Jentic by intent such as 'get a random Lovecraft sentence' or 'list the books', and Jentic returns the matching Random Lovecraft operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Random Lovecraft API through Jentic.
What authentication does the Random Lovecraft use?
The Random Lovecraft uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I a random sentence with the Random Lovecraft?
Yes. Use the GET /sentences endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Random Lovecraft?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I a random sentence through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'a random sentence'. Jentic returns the matching Random Lovecraft operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Random Lovecraft have?
The Random Lovecraft exposes 4 endpoints covering sentences, books operations.
Can I limit what my agent is allowed to do with the Random Lovecraft API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Random Lovecraft operations your agent may call, and every endpoint here is a read-only GET, so there is nothing destructive to grant. You can allow just the operations the agent needs, such as GET /sentences for a random sentence or GET /books to list titles, and leave out the rest. Since the book id sits in the path at GET /books/{id}/sentences, a rule can even pin the agent to reading a single book.
GET STARTED