Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Dog 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%2Fdog.ceo%2Fdog" | 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%2Fdog.ceo%2Fdog" | 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 Dog API.
List every available dog breed and its sub-breeds
Fetch a random dog image from all breeds
Fetch one or many random images for a specific breed
Retrieve all images for a given breed or sub-breed
Get a random image for a specific sub-breed
GET STARTED
Patterns agents use Dog API for, with concrete tasks.
★ Agent Dog Image Fetching
An AI agent building a pet-themed response or placeholder can fetch a random dog image or pull every image for a named breed from the Dog API. Because the API is free and needs no key, the agent can request images directly without a setup step.
List all breeds, then fetch a random image for a chosen breed
Breed and Sub-Breed Browser
An app showing a dog breed directory can list all breeds and their sub-breeds and then load images for each using the Dog API. The breed and sub-breed endpoints let the agent build a browsable gallery.
List the sub-breeds of a breed and retrieve all images for one sub-breed
Placeholder and Sample Images
Prototyping and testing workflows can pull one or many random dog images from the Dog API to use as sample content. The multiple-random endpoints return a batch of image URLs in a single request.
Fetch a batch of random dog images for use as placeholder content
10 endpoints — jentic publishes the only available openapi specification for the dog api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/breeds/list/all
List all breeds
/breeds/image/random
Random image from all breeds
/breeds/image/random/{count}
Multiple random images from all breeds
/breed/{breed}/images
All images from a breed
/breed/{breed}/images/random
Random image from a breed
/breed/{breed}/list
List sub-breeds
/breed/{breed}/{subBreed}/images
All images from a sub-breed
/breeds/list/all
List all breeds
/breeds/image/random
Random image from all breeds
/breeds/image/random/{count}
Multiple random images from all breeds
/breed/{breed}/images
All images from a breed
/breed/{breed}/images/random
Random image from a breed
/breed/{breed}/list
List sub-breeds
/breed/{breed}/{subBreed}/images
All images from a sub-breed
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Dog API by hand means learning its breed and sub-breed image endpoints and the random-count variants. Through Jentic you install once, import the Dog API from the API Directory, and your agent calls it.
Permission scoping
The Dog API is read-only and needs no credential, but a Jentic rule still bounds which operations your agent may call. Limit it to the image and breed-list operations it needs, and leave the rest out unless you add them.
Credential isolation
The Dog API needs no credential, so there is nothing to inject at call time. When you connect APIs that do require keys through Jentic, those keys are handled by your own Jentic One instance and never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get a random dog image' or 'list all dog breeds', and Jentic returns the matching Dog API operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Dog API through Jentic.
Why is there no official OpenAPI spec for the Dog API?
Dog CEO does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Dog API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Does the Dog API require authentication?
No. The Dog API is free and its OpenAPI spec declares no authentication, so requests need no key or token. Through Jentic the API behaves the same way, and when you add APIs that do require credentials, those are handled by your own Jentic One instance.
Can I get images for a specific breed with the Dog API?
Yes. The Dog API returns all images for a breed, a single random image, or a batch of random images, and the same operations exist for sub-breeds. You can list all breeds first to get valid breed names.
What are the rate limits for the Dog API?
The OpenAPI spec does not specify rate limits for the Dog API. Check the provider's documentation at https://dog.ceo/dog-api for current usage guidance.
Can I limit what my agent is allowed to do with the Dog API?
Yes. Even though the API needs no credential, a Jentic rule still bounds which operations your agent may call. Write a rule that allows only the image and breed-list operations the agent needs, and leave the rest out unless you add them, and every call it makes is logged.
How do I fetch a dog image with the Dog API through Jentic?
Search Jentic for 'get a random dog image' and it returns the matching Dog API operation with its input schema. Import the Dog API from the Jentic API Directory, and because it needs no credential your agent can list breeds and fetch images right away.
Is there a Dog API MCP server?
You don't need an MCP server to give your agent the Dog API. Jentic connects it directly from the API Directory: import it and your agent calls the breed and image operations with no key to manage. Nothing extra loads into the agent's context until an operation is actually used.
Know of an official OpenAPI document? Contribute it →
For Agents
Fetch open-source dog photos as image URLs: list breeds and sub-breeds, get all images for a breed, or return one or many random dog images, with no authentication.
Use for: List all dog breeds, Get a random dog image, Fetch several random dog images at once, Retrieve all images for a specific breed
Not supported: Does not handle image editing, breed facts, or user uploads. Use for fetching dog breed images and breed lists only.
Jentic publishes the only available OpenAPI specification for the Dog API, keeping it validated and agent-ready. The Dog API serves open-source dog photos as JSON image URLs. It lists every dog breed and its sub-breeds, returns all images for a breed or sub-breed, and returns a single random image or a batch of random images across all breeds. It is free and needs no authentication.
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>