canonical: https://jentic.com/apis/superheroapi.com/superhero-api

# SuperHero API

The SuperHero API provides quantified data on superheroes and villains from various comic book universes. Access detailed information including power stats, biography, appearance, work, connections, and images for over 700 characters. The API exposes 8 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get complete character data, get character power stats. Covers 8 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for media and content only.

## Capabilities

- Get complete character data
- Manage media data programmatically
- Integrate SuperHero API into automated workflows
- Query and filter SuperHero API records by parameters
- Monitor SuperHero API operational status and events

## Use cases

### Media and Content Operations

Use the SuperHero API to perform media operations programmatically. The API provides 8 endpoints covering core functionality including get complete character data, get character power stats, get character biography.

Example prompt: Call GET /{id} to get complete character data

### Automated Characters Management

Automate characters operations by combining multiple SuperHero API endpoints. Agents can get character power stats and then get character biography in a single workflow.

Example prompt: Call GET /{id}/powerstats to get character power stats, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SuperHero 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 apiKey tokens manually.

Example prompt: Search Jentic for 'get complete character data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/{id}` | Get complete character data |
| GET | `/{id}/powerstats` | Get character power stats |
| GET | `/{id}/biography` | Get character biography |
| GET | `/{id}/appearance` | Get character appearance |
| GET | `/{id}/work` | Get character work information |
| GET | `/{id}/connections` | Get character connections |
| GET | `/{id}/image` | Get character image |
| GET | `/search/{name}` | Search characters by name |

## Key resources

- **Characters** — Retrieve superhero and villain character data
- **Search** — Search for characters by name

## Why Jentic

- **Setup:** Wiring the SuperHero API by hand means placing your access token in the request as a query parameter and building the host path around it, then handling retries yourself. Through Jentic you install once, import the SuperHero API from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** The SuperHero API puts the character id in the URL path (/{id}, /{id}/powerstats), so a rule can pin your agent to one character: it can read that character's details and nothing else. Every operation here is a read, so the agent only ever fetches data you allow it to reach.
- **Credential handling:** Your SuperHero API access token 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.
- **Discovery method:** Agents search Jentic by intent such as 'get complete character data' or 'search a hero by name', and Jentic returns the matching SuperHero API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the SuperHero API use?

The SuperHero API uses an API key passed in the `access-token` query. 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 complete character data with the SuperHero API?

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

### What are the rate limits for the SuperHero 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 complete character data through Jentic?

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

### How many endpoints does the SuperHero API have?

The SuperHero API exposes 8 endpoints covering characters, search operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SuperHero API operations and credentials your agent can use. Every endpoint here is a read that carries the character id in the URL path, such as GET /{id} and GET /{id}/powerstats, so you can pin the agent to a single character and let it fetch only that character's details, power stats, biography, or image. The agent can never write data or reach a character you have not allowed.