Comicvine Gamespot ComicVine API
Agent-ready OpenAPI document · curated by JenticMediaContent DeliveryapiKey37 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Look up structured comic-book metadata - characters, issues, volumes, publishers, story arcs, and adaptations - across the full ComicVine catalogue with one API key.
Use for: Search ComicVine for a character by name, Get the full profile for a specific comic character id, List every issue in a Batman volume, Find all members of the Justice League team record
Not supported: Every operation in this specification is a GET retrieval: no user accounts, no comic purchases, no writes. Comic Vine restricts the API to non-commercial use only, and asks that you link back to Comic Vine on any page where you use its data.
Jentic publishes the only available OpenAPI specification for ComicVine API, keeping it validated and agent-ready. Comic Vine describes itself as 'The largest comic database online', with structured records for characters, issues, volumes, publishers, story arcs, teams, creators, locations, and related TV and film adaptations. Every one of the 37 operations in this specification is a GET, authenticated by an API key sent as the api_key query parameter, and each returns XML or JSON. Comic Vine states the API is strictly for non-commercial use only. Use it for fan projects, reading trackers, and AI agents that need accurate comic-book metadata across DC, Marvel, and every other publisher.
Install Jentic One Beta
Connect the ComicVine API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ComicVine 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.
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%2Fcomicvine.gamespot.com%2Fcomicvine" | 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%2Fcomicvine.gamespot.com%2Fcomicvine" | 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 ComicVine API.
Search across all resource types in one call via GET /search/
Look up a comic character profile by id via GET /character/{id}/
List or filter comic issues, volumes, and publishers
Fetch story arc, team, and concept records for cross-referencing
Retrieve creator (person) profiles and credits
Pull TV series, episodes, movies, and videos linked to comic properties
Use Cases
Patterns agents use ComicVine API for, with concrete tasks.
★ Comic Recommendation Bot
Build a recommendation experience that takes a character name, calls GET /search/ to resolve it to a character id, then walks GET /character/{id}/ and GET /issues/ filtered by character to suggest issues to read. Self-contained metadata means recommendations work without any external scraping.
Search ComicVine for 'Spider-Man', take the top character id from /search/, then call /issues/ filtered by character id and return five recent issues
Cross-Media Adaptation Lookup
When a fan asks 'what movies adapt the Watchmen comics?', call GET /story_arc/{id}/ for Watchmen and GET /movies/ to find linked films. ComicVine maintains explicit links between comic properties and TV or film adaptations, which makes it useful for comic-to-screen content discovery.
Get the story arc record for Watchmen by id and return the films listed in its movies field
Catalogue Sync for a Personal Reading Tracker
Sync a user's comic shelf into a tracking app by resolving each title to a ComicVine volume id via GET /volumes/, then pulling issues with GET /issue/{id}/ to populate cover image URLs, creators, and story arcs. The structured response is stable enough to mirror into a local database.
Resolve the volume id for 'The Sandman' via /volumes/, then fetch all issues with /issue/{id}/ and store the issue title, cover URL, and creators
AI Agent Trivia and Lore Assistant via Jentic
An AI agent connected to Jentic can answer 'who created Catwoman?' or 'list every issue Frank Miller wrote' by searching for the right ComicVine operation, loading its schema, and executing the call. Jentic stores the api_key in your Jentic One instance so the raw key never appears in agent context.
Use Jentic to search 'look up a comic book character on comicvine', load the operation, and execute a search for 'Catwoman'
Key Endpoints
37 endpoints — jentic publishes the only available openapi specification for comicvine api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/search/
Search across resource types
GET
/characters/
List comic book characters
GET
/character/{id}/
Get a single character by id
GET
/issues/
List comic book issues
GET
/volume/{id}/
Get a single volume by id
GET
/story_arc/{id}/
Get a single story arc by id
GET
/publishers/
List comic book publishers
GET
/movies/
List movies adapted from comics
GET
/search/
Search across resource types
GET
/characters/
List comic book characters
GET
/character/{id}/
Get a single character by id
GET
/issues/
List comic book issues
GET
/volume/{id}/
Get a single volume by id
GET
/story_arc/{id}/
Get a single story arc by id
GET
/publishers/
List comic book publishers
GET
/movies/
List movies adapted from comics
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ComicVine by hand means learning its API key scheme, threading the key onto every query, and parsing its paginated resource lists yourself. Through Jentic you install once, import ComicVine from the API Directory, store the key once, and your agent calls it.
Permission scoping
Every ComicVine operation in this specification is a GET and puts resource ids in the URL path (/character/{id}/, /volume/{id}/, /story_arc/{id}/), so a rule can pin your agent to lookups on those resources. You choose the operations it may call, so you can allow character and issue search while everything you leave out stays uncallable.
Credential isolation
Your ComicVine API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'look up a comic character' or 'find issues in a volume', and Jentic returns the matching ComicVine 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 ComicVine API through Jentic.
Why is there no official OpenAPI spec for ComicVine API?
ComicVine does not publish an OpenAPI specification - only the human documentation pages at comicvine.gamespot.com/api and comicvine.gamespot.com/api/documentation, neither of which mentions OpenAPI or Swagger. Jentic generates and maintains this spec so AI agents and developers can call ComicVine via structured tooling. Get started with Jentic One, the self-hosted execution layer.
What authentication does the ComicVine API use?
ComicVine uses an API key passed as a query parameter named api_key on every request. Through Jentic, the key is stored encrypted in your Jentic One instance and never enters the agent's context - the agent only sees execution results.
Can I search across characters, issues, and volumes in one call?
Yes. GET /search/ accepts a query string and a resources filter, returning matches across characters, issues, volumes, publishers, story arcs, teams, people, concepts, locations, and objects in a single response.
What are the rate limits for the ComicVine API?
Comic Vine's API terms state: 'We officially support 200 requests per resource, per hour.' It also runs velocity detection, warning that 'if too many requests are made per second, you may receive temporary blocks to resources', without publishing a per-second figure. The vendor suggests you cache responses in your app to prevent duplicated requests.
Is there a ComicVine MCP server?
You don't need an MCP server to give your agent ComicVine. Jentic connects it directly from the API Directory: import ComicVine, store your api_key once with your self-hosted Jentic One instance, and your agent calls any of the 37 operations it needs. Nothing extra loads into the agent's context, and your rules decide which operations it may call.
How do I look up a character through Jentic?
Search Jentic for 'look up a comic book character on comicvine', load the schema for GET /search/ or GET /character/{id}/, and execute. Your self-hosted Jentic One instance injects the api_key at execution time, so the agent works from the operation schema and never handles the raw credential.
Is the ComicVine API read-only?
Every one of the 37 operations in this specification is a GET, and none of them writes data. Comic Vine's own resource reference documents each resource with response filters only. Use it as a reference data source rather than a place to manage user-generated content.
Can I use the ComicVine API in a commercial product?
No. Comic Vine's API terms of use state: 'The API is strictly for non-commercial use only. Commercial use will result in your API key being revoked.' The same terms ask you to link back to Comic Vine on any page where you use its data, and not to edit, manipulate, or reproduce that data on another medium.
Can I limit what my agent is allowed to do with the ComicVine API?
Yes. Because you self-host Jentic One, your own rules decide which ComicVine operations the agent may call, so you can allow character and issue search, such as GET /search/ and GET /character/{id}/, while every operation you leave out stays uncallable. Every operation in this specification is a GET and puts resource ids in the URL path, like /character/{id}/, /volume/{id}/, and /story_arc/{id}/, so a rule can pin the agent to lookups on just the resources you approve. The API key is stored by your own instance and injected only at execution time, so the agent never sees the raw credential.
GET STARTED