Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Rick and Morty 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%2Frickandmortyapi.com%2Frickandmortyapi" | 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%2Frickandmortyapi.com%2Frickandmortyapi" | 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 Rick and Morty API.
Search characters by name, status, species, type, and gender, with paged results
Fetch one character by id, or several at once with a comma-separated list of ids
Find locations by name, type, or dimension and read who lives there
Look up episodes by name or by episode code such as S01E01
Batch-fetch several episodes or locations in a single request by id list
GET STARTED
Patterns agents use Rick and Morty API for, with concrete tasks.
★ Agent tutorial and test target with no credential
Developers building or testing an agent need a stable, public API that returns realistic nested data without signup. Through Jentic the agent searches by intent, such as 'find a Rick and Morty character by name', gets the listCharacters operation with its input schema, and calls it without any key to configure. Because the data is read-only, a test run cannot change anything upstream.
Call GET /character with name 'rick' and status 'alive', then return the name, species, and origin of each character on the first page
Fan wiki and trivia app data
Fan sites and trivia games need character, episode, and location facts they can trust. GET /character returns characters with status, species, gender, origin, location, and the episodes they appear in, while GET /episode/{id} returns air date, episode code, and the characters in it. The comma-separated id endpoints such as GET /character/{ids} load a whole cast list in one call.
Fetch GET /episode with episode 'S01E01', collect the character ids from its characters list, and load them in one call via GET /character/{ids}
Teaching REST pagination and filtering
Courses on REST APIs use the Rick and Morty API because it shows paging and query filters on small, friendly data. List endpoints accept a page parameter and return an info block with counts and next and previous links, and filters such as gender on characters or dimension on locations narrow results. Students can practice with no account or key.
Page through GET /location from page 1 until there is no next page and count how many locations have type 'Planet'
9 endpoints — jentic publishes the only available openapi specification for rick and morty api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/character
List characters with filters
/character/{id}
Get a character by id
/character/{ids}
Get multiple characters by ids
/location
List locations with filters
/episode
List episodes with filters
/episode/{id}
Get an episode by id
/character
List characters with filters
/character/{id}
Get a character by id
/character/{ids}
Get multiple characters by ids
/location
List locations with filters
/episode
List episodes with filters
/episode/{id}
Get an episode by id
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Rick and Morty API by hand means following its page-based list paging and building comma-separated id paths for batch lookups. Through Jentic you install once, import the Rick and Morty API from the API Directory, and your agent calls it with no credential to configure.
Permission scoping
Every operation is a read, and the character, location, and episode ids sit in the URL path, so a rule can pin your agent to the lookups it needs, such as character search and character by id, and withhold the rest. None of the operations change data.
Credential isolation
The Rick and Morty API serves public data and needs no credential, so there is no secret for your agent to see or mishandle. Calls still run through your own Jentic One instance, which logs them.
Intent-based discovery
Agents search Jentic by intent such as 'find a Rick and Morty character by name' or 'get an episode by code', and Jentic returns the matching operation with its input schema, including enum filters like status and gender.
Alternatives and complements available in the Jentic catalogue.
Specific to using Rick and Morty API through Jentic.
Why is there no official OpenAPI spec for Rick and Morty API?
The Rick and Morty API does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Rick and Morty 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.
What authentication does the Rick and Morty API use?
None. The spec declares no security schemes, and the API is public: every operation is a GET that needs no key, token, or account. Through Jentic there is nothing to configure before your agent calls it.
Can I fetch several characters in one request with the Rick and Morty API?
Yes. GET /character/{ids} takes a comma-separated list of character ids, such as 1,2,3, and returns them together. The same pattern works for locations with GET /location/{ids} and for episodes with GET /episode/{ids}.
What are the rate limits for the Rick and Morty API?
The OpenAPI spec does not specify rate limits. Check the official documentation at https://rickandmortyapi.com/documentation for current guidance, and cache results since the data rarely changes.
Is there a Rick and Morty API MCP server?
You don't need an MCP server to give your agent the Rick and Morty API. Jentic connects it directly from the API Directory: import it and your agent calls the character, location, and episode operations on demand, without another server's tool definitions in its context.
Can I limit what my agent is allowed to do with the Rick and Morty API?
Yes. Write a rule that allows only GET /character and GET /character/{id} for a character-lookup agent, and it can search and read characters but not page through locations or episodes. Every call it makes is logged, which helps when you use the API as a test target.
How do I filter Rick and Morty characters by status?
Pass the status query parameter to GET /character with one of alive, dead, or unknown. You can combine it with name, species, type, and gender, and step through results with page.
Know of an official OpenAPI document? Contribute it →
For Agents
Look up Rick and Morty characters, locations, and episodes by id or filter, such as characters by status and species or episodes by code, with no credential needed.
Use for: Find all characters named Rick who are still alive, Get the details of character 1, List every location in the Dimension C-137, Get the episode with code S03E07
Not supported: Does not stream episodes, host video, or cover other TV shows. Use for reading Rick and Morty character, location, and episode data only.
Jentic publishes the only available OpenAPI specification for Rick and Morty API, keeping it validated and agent-ready. The Rick and Morty API serves the characters, locations, and episodes of the Rick and Morty TV show as public, read-only JSON with no authentication. Characters can be filtered by name, status, species, type, and gender, locations by name, type, and dimension, and episodes by name or episode code such as S01E01. Each resource can be fetched by a single id or by a comma-separated list of ids in one request, and list results are paged with a page parameter.
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>