Install Jentic One Beta

Connect the PoetryDB API to your agent

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

List all authors

Get poems by author (partial match)

Search poems by title (partial match)

Use Cases

Patterns agents use PoetryDB API for, with concrete tasks.

★ Identity and Authentication Operations

Use the PoetryDB API to perform identity auth operations programmatically. The API provides 9 endpoints covering core functionality including list all authors, get poems by author (partial match), get specific fields from poems by author.

GET STARTED

Start building with PoetryDB API

Explore with Jentic One

View OpenAPI Document

Automated Author Management

Automate author operations by combining multiple PoetryDB API endpoints. Agents can get poems by author (partial match) and then get specific fields from poems by author in a single workflow.

Call GET /author/{author} to get poems by author (partial match), then verify the result

AI Agent Integration via Jentic

AI agents discover and call PoetryDB API 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 'list all authors', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — poetrydb is a free api for internet encyclopaedia of poetry.

METHOD

PATH

DESCRIPTION

GET

/author

List all authors

GET

/author/{author}

Get poems by author (partial match)

GET

/author/{author}/{outputFields}

Get specific fields from poems by author

GET

/title

List all poem titles

GET

/title/{title}

Search poems by title (partial match)

GET

/lines/{lines}

Search poems by line content

GET

/linecount/{linecount}

Get poems with exact line count

GET

/random

Get a random poem

GET

/author

List all authors

GET

/author/{author}

Get poems by author (partial match)

GET

/author/{author}/{outputFields}

Get specific fields from poems by author

GET

/title

List all poem titles

GET

/title/{title}

Search poems by title (partial match)

GET

/lines/{lines}

Search poems by line content

GET

/linecount/{linecount}

Get poems with exact line count

GET

/random

Get a random poem

Why Jentic?

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

Setup

Wiring the PoetryDB API by hand still means coding against its poetrydb.org paths and assembling author, title, and line queries yourself even though it needs no auth. Through Jentic you install once, import the PoetryDB API from the API Directory, and your agent calls it with no credential to manage.

Permission scoping

PoetryDB puts the author, title, and line selectors in the URL path (/author/{author}, /title/{title}), so a rule can pin your agent to lookups for one author. Every operation here is read-only, so the agent's allowed set is simply the queries you grant it.

Credential isolation

This API needs no credential, so there is nothing for the agent to hold; if you later add a secret, your own Jentic One instance stores it encrypted and injects it at execution time. Nothing sensitive enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list all authors' or 'get a random poem', and Jentic returns the matching PoetryDB operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PoetryDB API through Jentic.

What authentication does the PoetryDB API use?

The PoetryDB API 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 list all authors with the PoetryDB API?

Yes. Use the GET /author endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the PoetryDB API?

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 list all authors through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all authors'. Jentic returns the matching PoetryDB API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the PoetryDB API have?

The PoetryDB API exposes 9 endpoints covering author, linecount, lines operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which PoetryDB operations the agent may call, and every endpoint here is read-only, so the agent's allowed set is simply the queries you grant it. PoetryDB puts the author, title, and line selectors in the URL path, such as /author/{author} and /title/{title}, so a rule can pin the agent to lookups for a single author or restrict it to title searches while blocking the broad /author or /title listings. You control this scope entirely from your self-hosted instance.

PoetryDB API

Name: PoetryDB API
Brand: PoetryDB API
Availability: InStock

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationnone9 EndpointsREST

For Agents

Programmatically list all authors, get poems by author (partial match). Covers 9 operations.

Use for: I need to all authors, I want to poems by author (partial match), Search for specific fields from poems by author, Find all all poem titles

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

PoetryDB is a free API for internet encyclopaedia of poetry. Search and retrieve poems by author, title, lines, and linecount. The API exposes 9 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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: D+Signals: 4

42%

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.

50%

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.

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

54%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PoetryDB API to your agent

Capabilities

Use Cases

Start building with PoetryDB API

Key Endpoints

Why Jentic?

Related APIs

FAQs

PoetryDB API

Jentic AI Readiness Score

PoetryDB 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