Evetech EVE Swagger Interface

Name: EVE Swagger Interface API
Brand: EVE Swagger Interface
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent Deliveryoauth2206 EndpointsREST

For Agents

Read EVE Online characters, corporations, alliances, mail, assets, and market data through 206 ESI endpoints authenticated via EVE SSO.

Use for: I need to look up an EVE Online character's affiliation, Retrieve all alliances I am tracking with my EVE SSO token, List the contacts attached to my EVE corporation, Get the icon assets for a specific EVE alliance

Not supported: Does not handle in-game purchases, account billing, or PLEX redemption - use for read-only and scoped game-state operations through ESI only.

Jentic publishes the only available OpenAPI specification for EVE Swagger Interface, keeping it validated and agent-ready. The EVE Swagger Interface (ESI) is the public API for the MMO game EVE Online, exposing 206 endpoints that cover characters, corporations, alliances, contacts, market data, in-game mail, and assets. Agents can read live game state for an authenticated character or query universe-wide reference data such as alliance membership, contact lists, and corporation icons. ESI uses EVE SSO OAuth2 for any character-scoped operation.

Jentic One on Github View OpenAPI Document

Install Jentic One Beta

Connect the EVE Swagger Interface to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EVE Swagger Interface, 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%2Fevetech.net%2Fevetech" | sh

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%2Fevetech.net%2Fevetech" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 EVE Swagger Interface API.

Look up alliance membership, icons, and contact lists across the EVE universe

Retrieve a character's affiliation, contacts, and in-game mail when authorised via EVE SSO

Query corporation membership, structure, and operational data scoped to a member token

Fetch labels and structured contact lists for alliances, corporations, and characters

GET STARTED

Start building with EVE Swagger Interface API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use EVE Swagger Interface API for, with concrete tasks.

★ Third-Party EVE Online Tooling

Players build out-of-game tools (asset trackers, fleet finders, market dashboards) by reading live state through ESI. The 206-endpoint surface gives those tools structured access to characters, corporations, alliances, mail, and contacts. With an EVE SSO OAuth2 token scoped to the right character, an agent can populate dashboards in seconds rather than scraping the in-game client.

GET /characters/{character_id}/ with an EVE SSO token to fetch the character's corporation and alliance, then GET /alliances/{alliance_id}/ for full alliance details

Corporation and Alliance Intel

Diplomats and corp leaders pull live alliance and corporation rosters to track defections, recruit new pilots, and broker treaties. ESI exposes /alliances/{alliance_id}/corporations/, /alliances/{alliance_id}/contacts/, and /alliances/{alliance_id}/contacts/labels/ for structured reads, letting an agent diff today's roster against yesterday's snapshot in one call each.

GET /alliances/{alliance_id}/corporations/ each hour, diff against the last snapshot, and post any joiners or leavers to a Discord webhook

EVE SSO-Authenticated Agent Workflows

Agents that act on behalf of a single pilot (mail readers, contract bots, market notifiers) authenticate via EVE SSO OAuth2 and receive scoped tokens that ESI validates per call. The same token pattern unlocks character-, corporation-, and alliance-scoped endpoints, with scopes determining exactly which of the 206 endpoints an agent may call.

Exchange an EVE SSO authorization code for a scoped access token, then call GET /characters/{character_id}/ and downstream character-scoped endpoints with that token

AI Agent EVE Assistant via Jentic

An AI assistant for EVE pilots wires Jentic-discovered ESI operations into a chat interface, so a player can ask 'who is in alliance X?' and the agent calls /alliances/{alliance_id}/corporations/ without the player ever touching ESI directly. Jentic handles search, schema loading, and execution for each query.

Use Jentic search 'list eve online alliance corporations' to find GET /alliances/{alliance_id}/corporations/, load schema, and execute with the alliance ID from the player's prompt

Key Endpoints

206 endpoints — jentic publishes the only available openapi specification for eve swagger interface, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/alliances/

List all alliances

GET

/alliances/{alliance_id}/

Get alliance details

GET

/alliances/{alliance_id}/contacts/

List alliance contacts

GET

/alliances/{alliance_id}/contacts/labels/

List alliance contact labels

GET

/alliances/{alliance_id}/corporations/

List corporations in an alliance

GET

/alliances/{alliance_id}/icons/

Get alliance icon URLs

GET

/characters/affiliation/

Bulk lookup character affiliation

GET

/characters/{character_id}/

Get character profile

GET

/alliances/

List all alliances

GET

/alliances/{alliance_id}/

Get alliance details

GET

/alliances/{alliance_id}/contacts/

List alliance contacts

GET

/alliances/{alliance_id}/contacts/labels/

List alliance contact labels

GET

/alliances/{alliance_id}/corporations/

List corporations in an alliance

GET

/alliances/{alliance_id}/icons/

Get alliance icon URLs

GET

/characters/affiliation/

Bulk lookup character affiliation

GET

/characters/{character_id}/

Get character profile

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the EVE Swagger Interface by hand means running the EVE SSO OAuth2 flow, refreshing bearer tokens, and mapping the right scope onto each ESI endpoint yourself. Through Jentic you install once, import the EVE Swagger Interface from the API Directory, store the OAuth client once, and your agent calls it while Jentic refreshes the token for you.

Permission scoping

ESI puts the alliance id in the URL path (/alliances/{alliance_id}/contacts/), so a rule can pin your agent to one alliance: it can read that alliance's contacts, corporations, and icons and nothing else. You choose the operations it may call, so the agent only gets the ones you place in the allowed set.

Credential isolation

Your EVE SSO OAuth client and refresh token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list eve online alliance corporations' or 'read alliance contacts', and Jentic returns the matching ESI operation with its input schema so the agent calls the right endpoint without paging through the reference docs.

FAQs

Specific to using EVE Swagger Interface API through Jentic.

Why is there no official OpenAPI spec for EVE Swagger Interface?

CCP Games does not publish a curated OpenAPI specification at this hosted location. Jentic generates and maintains this spec so that AI agents and developers can call EVE Swagger Interface via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the EVE Swagger Interface use?

ESI uses the EVE SSO OAuth2 flow (security scheme name evesso). Agents exchange an authorization code for a scoped access token; the requested scopes determine which of the 206 endpoints can be called. Through Jentic, the OAuth credentials live in your Jentic One instance.

Can I list every corporation inside an EVE alliance with the EVE Swagger Interface?

Yes. GET /alliances/{alliance_id}/corporations/ returns the full corporation list for an alliance. Pair it with /alliances/{alliance_id}/ for alliance-level details and /alliances/{alliance_id}/icons/ for branding assets.

What are the rate limits for the EVE Swagger Interface?

ESI enforces an error-rate budget rather than a flat per-second limit; sustained 4xx/5xx responses trigger temporary blocks. The spec itself does not include a numeric quota - monitor X-ESI-Error-Limit headers in production and back off when they shrink.

How do I look up an EVE character through Jentic?

Run pip install jentic, then await client.search('look up an eve online character'), client.load, client.execute. Jentic returns GET /characters/{character_id}/ with the character_id parameter wired into the input schema.

Does the EVE Swagger Interface let me read in-game mail?

Yes - ESI includes mail endpoints under the /characters/{character_id}/mail/ path family, gated behind specific OAuth2 scopes. Agents must be granted the mail-read scope at SSO consent time before those reads succeed.

Can I limit what my agent is allowed to do with the EVE Swagger Interface?

Yes. Because you run Jentic One yourself, your own rules decide which ESI operations and which EVE SSO credentials the agent may use. Since ESI carries the alliance id in the URL path, such as /alliances/{alliance_id}/contacts/, you can pin the agent to a single alliance and let it read only that alliance's contacts, corporations, and icons. You place each operation in the allowed set, so the agent can call only the endpoints you choose and nothing else.