Fever

Fever is a global live-entertainment discovery and ticketing platform that helps millions of people find events, activities and experiences in their city, and gives venues and partners the tools to sell and analyze tickets. For developers Fever exposes two public surfaces: an official Model Context Protocol (MCP) server over its real-time global event catalog (tools search_cities and search_events, OAuth 2.0 with PKCE), and a partner-facing Reporting API delivering in-depth event sales data (orders, tickets, financials, plan and session details) for CRM, BI, data-warehouse and ERP integration. Fever is backed by Accel and General Catalyst.

Fever publishes 5 API contracts indexed on the APIs.io network, including Authentication API, FeverZone API, Order Items API, and 2 more. Tagged areas include Company, Consumer, Live Entertainment, Event, and Ticketing.

Fever’s developer surface includes documentation, API reference, authentication, support, and 18 more developer resources.

🌐 Visit website 📡 Source on GitHub

33.1/100 thin ▬ flat Agent 56/100 agent ready Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-09 · rubric v0.23.0

AccessSelf serve

2 published contracts 1 MCP Servers

Company Consumer Live Entertainment Event Ticketing Experience Reporting MCP

Kin Score

Kin Score How this is scored →
scored 2026-10-09 · rubric v0.23.0

Composite quality — 33.1/100 · thin

Contract Quality 8.5 / 19

Developer Ergonomics 3.8 / 15

Access Clarity 3.2 / 15

Operational Transparency 2.8 / 10

Contract Governance 0.4 / 9

Discoverability 5.6 / 8

Regulatory Posture 3.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 56/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/fever: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

Fever Authentication API

This endpoint is used to authenticate a user. It requires a username and password to be passed in the request body. If the user is authenticated successfully, a token is returne...

Fever FeverZone API

These endpoints provide an interface to extract the data available in FeverZone reports. The delay of the data is less than 15 minutes from reality. The route `/feverzone/sales-...

Fever Order Items API

These endpoints enable to access order-item data. ## Filtering Options The endpoint supports filtering by: | Parameter | Type | Description | |-----------|------|-------------| ...

Fever Plans API

The goal of the Plan endpoint is to provide all information about the plans/events/experiences/listings organised by a partner. The delay of the data is less than 10 minutes fro...

Fever Sessions API

The goal of the Session Endpoint is to provide all information about the session (or ticket types) of a plan. The delay of the data is less than 10 minutes from reality. ## Requ...

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Fever - Reporting Authentication API

OPEN COLLECTION

Fever - Reporting Authentication FeverZone API

OPEN COLLECTION

Fever - Reporting Authentication Order Items API

OPEN COLLECTION

Fever - Reporting Authentication Plans API

OPEN COLLECTION

Fever - Reporting Authentication Sessions API

OPEN COLLECTION

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Fever MCP Server

Official Fever MCP server exposing Fever's global live-entertainment event catalog to MCP-compatible clients (Claude Desktop, Cursor, Windsurf, Claude Code). Data is real-time, ...

MCP SERVER

Rate Limits 1

Documented rate limits and quota policies.

Fever Rate Limits

2 limits

RATE LIMITS

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Fever Reporting Api Overlay

2 actions · update · fever-reporting-api-openapi-original.json

UNRECORDED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Fever Authentication

oauth2 · 2 schemes

SECURITY

Fever Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Fever Agentic Access

13 operations · 2 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

MCPServer

WellKnown

LLMsTxt

AgenticAccess

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

Lifecycle

Conformance

DataModel

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

RateLimits

RateLimits

StatusPage

StatusPage

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: fever
name: Fever
description: 'Fever is a global live-entertainment discovery and ticketing platform that helps millions of people find events,
  activities and experiences in their city, and gives venues and partners the tools to sell and analyze tickets. For developers
  Fever exposes two public surfaces: an official Model Context Protocol (MCP) server over its real-time global event catalog
  (tools search_cities and search_events, OAuth 2.0 with PKCE), and a partner-facing Reporting API delivering in-depth event
  sales data (orders, tickets, financials, plan and session details) for CRM, BI, data-warehouse and ERP integration. Fever
  is backed by Accel and General Catalyst.'
url: https://raw.githubusercontent.com/api-evangelist/fever/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- accel
- general-catalyst
x-tier: stub
x-tier-reason: portfolio-lead
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
image: https://feverup.com/_astro/og-image-fever.PfP_3GVw.jpg
tags:
- Company
- Consumer
- Live Entertainment
- Event
- Ticketing
- Experience
- Reporting
- MCP
tags_raw:
- Company
- Consumer
- Live Entertainment
- Events
- Ticketing
- Experiences
- Reporting
- MCP
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
apis:
- aid: fever:fever-authentication-api
  name: Fever Authentication API
  description: 'This endpoint is used to authenticate a user. It requires a username and password to be passed in the request
    body. If

    the user is authenticated successfully, a token is returned in the response body. This token is used to authenticate the

    user in subsequent requests.


    ⚠️ The token expiration time is **30 minutes**. After that time, the user will need to authenticate again to get a new
    token.'
  humanURL: https://developer.feverup.com/en/
  baseURL: https://data-reporting-api.prod.feverup.com/v1
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/fever-authentication-api-openapi.yml
  - type: Documentation
    url: https://developer.feverup.com/en/
  - type: APIReference
    url: https://data-reporting-api.prod.feverup.com/v1/redoc
  - type: Authentication
    url: authentication/fever-authentication.yml
- aid: fever:fever-feverzone-api
  name: Fever FeverZone API
  description: 'These endpoints provide an interface to extract the data available in FeverZone reports. The delay of the
    data

    is less than 15 minutes from reality. The route `/feverzone/sales-by-reseller` allows the user to get a sales summary

    by reseller and can be aggregated by venues/ticket types.


    ## Model documentation


    #### Sales


    This endpoint returns a summary of the sales, aligned with FeverZone Sales Summary report. It allows to filter by

    `plan_ids`, `purchase_date` and `event_date`, and also specify the `currency` of the report.


    <details>

    <summary><b>📄 <code>/feverzone/sales-summary</code> response entity model</b></summary>


    | Column Name            | Description                                                                                                                                                                                                                                                                                                                                                                         |
    Example value |

    |------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|

    | `currency`             | ISO3 currency of the order monetary field.                                                                                                                                                                                                                                                                                                                                          |
    EUR           |

    | `orders`               | Metric representing the number of unique transactions (count) made, where each order may include
    multiple tickets and add-ons.                                                                                                                                                                                                                                                      |
    100           |

    | `tickets_sold`         | Metric representing the number (sum) of entry tickets sold, excluding any complimentary tickets
    issued (invitations) and add-ons. This value shows the total number of entry tickets, representing the primary sales volume.                                                                                                                                                        |
    200           |

    | `addons_sold`          | Metric representing the number (sum) of add-ons sold, excluding complimentary invitations.
    Indicates the total number of add-ons purchased.                                                                                                                                                                                                                                         |
    50            |

    | `ticket_invitations`   | Metric representing the number (sum) of complimentary tickets issued at no charge for the user.
    Issuing invitations may have fees.                                                                                                                                                                                                                                                  |
    10            |

    | `addons_invitations`   | Metric representing the number (sum) of complimentary add-ons issued at no charge. Issuing
    add-ons may have fees.                                                                                                                                                                                                                                                                   |
    5             |

    | `ticket_gross_revenue` | Metric representing the revenue generated exclusively from the sale of entry tickets. It''s
    the sum of `tickets_sold` multiplied by their ticket price. It shows the financial contribution of ticket sales to the
    total revenue.                                                                                                                                                    |
    1200.00       |

    | `addon_gross_revenue`  | Metric representing the revenue generated from the sale of additional items or services, such
    as merchandise or premium experiences (a.k.a. add-ons). It''s the sum of `addons_sold` multiplied by their add-on price.
    It indicates the contribution of supplementary products or services to total revenue.                                                                         |
    356.34        |

    | `total_gross_revenue`  | Metric representing the total amount of revenue generated from ticket sales and add-ons, including
    surcharge, and before any discounts are applied. It equals to `ticket_gross_revenue` + `addon_gross_revenue` + `surcharge`.
    Indicates the overall financial performance, showing the total revenue collected from sales and additional charges before
    considering any discounts. | 1556.34       |

    | `ticket_surcharge`     | Metric representing the surcharges applied specifically to entry ticket sales. It''s the sum
    of `tickets_sold` multiplied by their surcharge per ticket. It provides details on the extra fees associated with entry
    ticket purchases.                                                                                                                                               |
    56.34         |

    | `addon_surcharge`      | Metric representing the surcharges applied specifically to add-ons. It''s the sum of `addons_sold`
    multiplied by their surcharge per add-on. It shows the extra fees collected from add-on purchases.                                                                                                                                                                                |
    0.00          |

    | `surcharge`            | Metric representing the sum of additional booking fees applied to the order at checkout. It''s
    the sum of `ticket_surcharge` and `addon_surcharge`. It represents extra charges collected.                                                                                                                                                                                           |
    56.34         |

    | `discount`             | Metric representing the total value of all discounts applied through promo codes or special
    offers. It''s the sum of all discounts applied, and it''s represented with a negative value. It indicates the amount of
    revenue that has been reduced due to promotional efforts.                                                                                                         |
    -100.00       |

    | `user_payment`         | Metric representing the total revenue collected after discounts. It is computed as the `total_gross_revenue`
    + `discounts`. It reflects actual revenue paid by customers.                                                                                                                                                                                                           |
    1456.34       |


    </details>


    <details>

    <summary><b>📄 <code>/feverzone/sales-by-ticket-type</code> response entity model</b></summary>


    | Column Name            | Description                                                                                                                                                                                                                                                                                                                                                                         |
    Example value |

    |------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------|

    | `currency`             | ISO3 currency of the order monetary field.                                                                                                                                                                                                                                                                                                                                          |
    EUR           |

    | `ticket_type`          | Type of ticket sold.                                                                                                                                                                                                                                                                                                                                                                |
    Adult         |

    | `tickets_sold`         | Metric representing the number (sum) of entry tickets sold, excluding any complimentary tickets
    issued (invitations) and add-ons. This value shows the total number of entry tickets, representing the primary sales volume.                                                                                                                                                        |
    200           |

    | `addons_sold`          | Metric representing the number (sum) of add-ons sold, excluding complimentary invitations.
    Indicates the total number of add-ons purchased.                                                                                                                                                                                                                                         |
    50            |

    | `ticket_invitations`   | Metric representing the number (sum) of complimentary tickets issued at no charge for the user.
    Issuing invitations may have fees.                                                                                                                                                                                                                                                  |
    10            |

    | `addons_invitations`   | Metric representing the number (sum) of complimentary add-ons issued at no charge. Issuing
    add-ons may have fees.                                                                                                                                                                                                                                                                   |
    5             |

    | `ticket_gross_revenue` | Metric representing the revenue generated exclusively from the sale of entry tickets. It''s
    the sum of `tickets_sold` multiplied by their ticket price. It shows the financial contribution of ticket sales to the
    total revenue.                                                                                                                                                    |
    1200.00       |

    | `addon_gross_revenue`  | Metric representing the revenue generated from the sale of additional items or services, such
    as merchandise or premium experiences (a.k.a. add-ons). It''s the sum of `addons_sold` multiplied by their add-on price.
    It indicates the contribution of supplementary products or services to total revenue.                                                                         |
    356.34        |

    | `total_gross_revenue`  | Metric representing the total amount of revenue generated from ticket sales and add-ons, including
    surcharge, and before any discounts are applied. It equals to `ticket_gross_revenue` + `addon_gross_revenue` + `surcharge`.
    Indicates the overall financial performance, showing the total revenue collected from sales and additional charges before
    considering any discounts. | 1556.34       |

    | `ticket_surcharge`     | Metric representing the surcharges applied specifically to entry ticket sales. It''s the sum
    of `tickets_sold` multiplied by their surcharge per ticket. It provides details on the extra fees associated with entry
    ticket purchases.                                                                                                                                               |
    56.34         |

    | `addon_surcharge`      | Metric representing the surcharges applied specifically to add-ons. It''s the sum of `addons_sold`
    multiplied by their surcharge per add-on. It shows the extra fees collected from add-on purchases.                                                                                                                                                                                |
    0.00          |

    | `surcharge`            | Metric representing the sum of additional booking fees applied to the order at checkout. It''s
    the sum of `ticket_surcharge` and `addon_surcharge`. It represents extra charges collected.                                                                                                                                                                                           |
    56.34         |

    | `discount`             | Metric representing the total value of all discounts applied through promo codes or special
    offers. It''s the sum of all discounts applied, and it''s represented with a negative value. It indicates the amount of
    revenue that has been reduced due to promotional efforts.                                                                                                         |
    -100.00       |

    | `user_payment`         | Metric representing the total revenue collected after discounts. It is computed as the `total_gross_revenue`
    + `discounts`. It reflects actual revenue paid by customers.                                                                                                                                                                                                           |
    1456.34       |


    </details>


    <details>

    <summary><b>📄 <code>/feverzone/sales-by-reseller</code> response entity model</b></summary>


    | Column Name                    | Description                                                    | Example value                        |

    |--------------------------------|----------------------------------------------------------------|--------------------------------------|

    | `reseller.id`                  | ID of the reseller                                             | 607f50e3-666f-4b2e-9620-38aabf6d9m10
    |

    | `reseller.name`                | Name of the reseller                                           | Reseller name                        |

    | `reseller.email`               | Email of the reseller                                          | test@reseller.com                    |

    | `reseller.type`                | Type of reseller                                               | AGENCY                               |

    | `reseller.contact_language`    | Language that the reseller uses for communications             | es_ES                                |

    | `reseller.accepts_comms`       | If reseller accepts communications or not                      | YES                                  |

    | `ticket_type`                  | Ticket type by reseller                                        | Agencia \| Tarifa
    Básica             |

    | `venue_name`                   | Venue name by reseller                                         | Palacio Real de Madrid               |

    | `tickets_sold`                 | Tickets sold by reseller and aggregated dimensions applicable  | 1000                                 |

    | `gross_revenue`                | Gross revenue by reseller and aggregated dimensions applicable | 10000                                |


    </details>'
  humanURL: https://developer.feverup.com/en/
  baseURL: https://data-reporting-api.prod.feverup.com/v1
  tags:
  - FeverZone
  properties:
  - type: OpenAPI
    url: openapi/fever-feverzone-api-openapi.yml
  - type: Documentation
    url: https://developer.feverup.com/en/
  - type: APIReference
    url: https://data-reporting-api.prod.feverup.com/v1/redoc
  - type: Authentication
    url: authentication/fever-authentication.yml


# --- truncated at 32 KB (77 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/fever/refs/heads/main/apis.yml

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/fever"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/fever/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/fever/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.