Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Geek Jokes 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%2Fsameerkumar.website%2Fsameerkumar-website" | shStep 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%2Fsameerkumar.website%2Fsameerkumar-website" | 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.
What an agent can do with Geek Jokes API.
Get a random geek joke
Manage identity auth data programmatically
Integrate Geek Jokes API into automated workflows
Query and filter Geek Jokes API records by parameters
Monitor Geek Jokes API operational status and events
GET STARTED
Patterns agents use Geek Jokes API for, with concrete tasks.
★ Identity and Authentication Operations
Use the Geek Jokes API to perform identity auth operations programmatically. The API provides 1 endpoints covering core functionality including get a random geek joke.
Call GET /api to get a random geek joke
Data Retrieval and Monitoring
Query Geek Jokes API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary Geek Jokes API endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call Geek Jokes 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 'get a random geek joke', load the operation schema, and execute with Jentic-managed credentials
1 endpoints — a simple api that returns random geek and programming jokes.
METHOD
PATH
DESCRIPTION
/api
Get a random geek joke
/api
Get a random geek joke
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Geek Jokes API by hand means reading the reference to find its single endpoint on geek-jokes.sameerkumar.website and handling retries yourself. Through Jentic you install once, import Geek Jokes from the API Directory, and your agent calls it with no credential to manage.
Permission scoping
The Geek Jokes API exposes a single read-only operation, so a rule limits the agent to the operation it needs: fetching a random joke. No other operations exist for it to reach.
Credential isolation
The Geek Jokes API needs no credential, so there is nothing to store; your own Jentic One instance calls it directly and no secret enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a random geek joke', and Jentic returns the matching Geek Jokes operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Geek Jokes API through Jentic.
What authentication does the Geek Jokes API use?
The Geek Jokes 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 get a random geek joke with the Geek Jokes API?
Yes. Use the GET /api endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Geek Jokes 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 get a random geek joke through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get a random geek joke'. Jentic returns the matching Geek Jokes API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Geek Jokes API have?
The Geek Jokes API exposes 1 endpoints for identity auth operations.
Can I limit what my agent is allowed to do with the Geek Jokes API?
Yes. Jentic One is self-hosted, so you run it and your own rules decide which operations and credentials the agent may use. The Geek Jokes API exposes a single read-only operation, GET /api, which fetches a random joke, so you can scope the agent to just that call and it can reach nothing else. Because no other operations exist and the API needs no credential, the agent is confined to fetching jokes.
For Agents
Programmatically get a random geek joke. Covers 1 operations.
Use for: I need to a random geek joke, Find available identity auth operations, Get the current status of Geek Jokes API resources, List all records from Geek Jokes API
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
A simple API that returns random geek and programming jokes. No authentication required. The API exposes 1 endpoints.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>