canonical: https://jentic.com/apis/evemarketer.com/evemarketer-marketstat # EVEMarketer Marketstat API Jentic publishes the only available OpenAPI specification for EVEMarketer Marketstat API, keeping it validated and agent-ready. The EVEMarketer Marketstat API returns aggregated buy and sell order statistics for items in EVE Online, the spaceship MMO. It is API-compatible with the historical EVE-Central Marketstat endpoint, returning min, max, average and volume figures filtered by typeID, regionlimit, usesystem and hours. Both XML and JSON response formats are available, with no authentication required for read access. ## For AI agents Fetch EVE Online market price statistics (min, max, average, volume) for items by typeID, region or solar system in JSON or XML. ## Scope Does not handle character data, contracts, or in-game messaging - use for retrieving aggregated EVE Online market price statistics only. ## Capabilities - Retrieve market statistics for one or more items by typeID across the entire universe - Limit market statistics to a specific region by regionlimit parameter - Limit market statistics to a single solar system using the usesystem parameter - Filter recent market activity by an hours parameter to focus on fresh data - Choose JSON output via the `/marketstat/json` endpoint for programmatic consumers - Use the legacy XML output for compatibility with EVE-Central tooling ## Use cases ### Trade route price discovery Compare the buy price in one region against the sell price in another to identify profitable trade routes for haulers. Two GET `/marketstat/json` calls with different regionlimit values return the figures needed to compute the spread, and the volume field indicates how much liquidity exists at each end. Implementation takes under an hour. Example prompt: GET `/marketstat/json` with typeID and regionlimit set to The Forge, then again with regionlimit set to Domain, and compute the buy-low / sell-high spread. ### Market trend dashboard Build a dashboard that tracks min, max and average prices for a watchlist of items over time by polling the JSON endpoint at a fixed interval. Each datapoint stored locally lets the dashboard render simple price-history charts without scraping the EVE Online client. Example prompt: GET `/marketstat/json` hourly for each typeID in the watchlist, append min/max/avg/volume to a local time-series store, then expose it via a chart endpoint. ### Industrial sourcing decisions An EVE Online industrialist decides whether to mine a mineral or buy it from the market by checking the current sell price and volume. A single GET /marketstat with the mineral's typeID and the industry hub regionlimit returns enough data to drive the build-vs-buy decision. Example prompt: GET /marketstat?typeID=34®ionlimit=10000002 (The Forge), then return whether the average sell price is below the player's mining yield. ### Agent-driven market lookups via Jentic An AI agent assistant for an EVE Online corporation answers price questions by calling the EVEMarketer Marketstat API through Jentic. Because the endpoint is unauthenticated, Jentic adds reliability features such as retries and rate-limit handling without needing to manage credentials. Example prompt: Search Jentic for 'fetch EVE Online market statistics', load the schema for GET `/marketstat/json`, and execute with the typeID parsed from the player's question. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/marketstat/json` | Fetch market statistics in JSON | | POST | `/marketstat/json` | Fetch market statistics in JSON via POST for large typeID lists | | GET | `/marketstat` | Fetch market statistics in XML | | POST | `/marketstat` | Fetch market statistics in XML via POST | ## Key resources - **marketstat** — Aggregated buy and sell order statistics for EVE Online items ## Why Jentic - **Setup:** Wiring the EVEMarketer Marketstat API by hand means finding the /ec base URL, choosing between the GET and POST marketstat forms, and handling typeID and regionlimit parameters yourself. Through Jentic you install once, import the EVEMarketer Marketstat API from the API Directory, and your agent calls it with no credential to manage. - **Permission scoping:** EVEMarketer Marketstat is unauthenticated and read-only, carrying typeID and regionlimit as parameters rather than a resource you own, so scope the agent to the marketstat operations it needs. You choose which operations are allowed, so nothing beyond reading market statistics runs unless you add it. - **Credential handling:** EVEMarketer Marketstat needs no credential, so there is nothing to store; Jentic still applies uniform policies such as rate limiting and retries at execution time, with no secret ever in the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'fetch EVE Online market statistics', and Jentic returns the matching GET `/marketstat/json` operation with its typeID and regionlimit schema so the agent calls the right endpoint without browsing community wikis. ## Related APIs - **EVEMarketer Marketstat API (alt index)** — Identical surface, indexed under a different api_slug for legacy aggregator compatibility - **Salesforce API** — Cross-reference EVE corporation data into a CRM-like system for guild operations - **HubSpot Account Info** — Track external community engagement metrics in a CRM tool that also surfaces market lookups ## FAQ ### Why is there no official OpenAPI spec for EVEMarketer Marketstat API? EVEMarketer is a community-maintained service that succeeded EVE-Central, and it does not publish an OpenAPI artefact. Jentic generates and maintains this spec so that AI agents and developers can call EVEMarketer Marketstat API 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 EVEMarketer Marketstat API use? None. The /marketstat and `/marketstat/json` endpoints are openly accessible without an API key. Through Jentic the endpoint is still proxied so retries and rate-limit handling are uniform across other tools the agent uses. ### Can I get prices for multiple items in one call? Yes. The typeID query parameter can be repeated, and POST `/marketstat/json` accepts a body for very large typeID lists when the URL would otherwise become unwieldy. ### What are the rate limits for the EVEMarketer Marketstat API? Rate limits are not declared in the spec. EVEMarketer is community-funded, so polite use is expected - cache aggressively for typeIDs and regions that you query repeatedly. Through Jentic, retries and exponential backoff are applied by default. ### How do I look up an EVE Online price through Jentic? Use the Jentic search query 'fetch EVE Online market statistics', which resolves to GET `/marketstat/json.` Run pip install jentic, load the operation, and execute with the typeID and optional regionlimit. ### Is the JSON output identical to the legacy EVE-Central format? It is almost identical. EVEMarketer documents itself as 'almost compatible' with EVE-Central's Marketstat API, so most EVE-Central clients work with minor field-name adjustments. ### Can I limit what my agent is allowed to do with the EVEMarketer Marketstat API? Yes. Because you run Jentic One yourself, your own rules decide which operations the agent may call, so you can allow only the marketstat reads it needs, such as GET `/marketstat/json`, and leave the POST variants or XML endpoints out. The EVEMarketer Marketstat API is unauthenticated and read-only, carrying typeID and regionlimit as parameters rather than a resource you own, so nothing beyond fetching aggregated market statistics runs unless you add it. This keeps the agent scoped to price lookups and never lets it reach beyond the operations you have approved.