# AgentLive.Events > Built for agents. Made for fans. - Skill file: https://api.agentlive.events/SKILL.md - MCP server (Streamable HTTP, same Bearer key): https://api.agentlive.events/mcp - OpenAPI: https://api.agentlive.events/openapi.json - Get a key: POST https://api.agentlive.events/v1/agents. Returns a new API key once. Send it as a Bearer token on every call. The optional label is your agent's name. ## Tools - search_events (GET /v1/events): Search the ticket catalog by keyword, location (city, for example Los Angeles, or near with latitude,longitude), dates, category, performer or venue. Returns events with date, venue, the lowest all-in price per ticket, and whether tickets exist. - get_event (GET /v1/events/{id}): Event detail plus venue information: rules, child rules, parking, public transportation, directions and will call. - get_seating_overview (GET /v1/events/{id}/seating): Seating options for an event and quantity, in at most 12 areas. When the venue map names levels, sections are grouped by level (for example Field, Lower, Club, Upper or Suites); otherwise by area of the venue, such as Sections 100s when most sections are numbers, or sections that share the start of their name. If that gives more than 12 areas, small areas are combined. If there are still too many, single sections go into one area named Other sections, fewest listings first, and grouped areas join it only when there are 12 or more of them. Each area has the number of listings, the lowest all-in price per ticket, and sections, the section names in that area; pass one of those names as section to get_listings. listingCount is the total number of listings. omittedAreasCount is how many areas were folded into Other sections, and it is 0 when there is no Other sections area. The response also has the low, average and high all-in price per ticket for that quantity, the venue layout and a map page. eventNotes, when present, are notes supplied with the event's ticket list; read them to your human word for word. Use it before get_listings, and ask your human whether the view or the budget matters more. When price comparison is on, each area also has comparisonStatus next to priceComparison: cheaper_found, none_cheaper, no_match, pending or not_checked, and sellersChecked (StubHub, SeatGeek and Vivid Seats covered by the capture, empty when not_checked). - get_listings (GET /v1/events/{id}/listings): Live listings for an event: section, row, seats, quantities you can buy, all-in price per ticket, delivery, seller notes and notices, and a quality score. seating has the map links, rowDepth and levelGuess. seating.viewFromSectionUrl, when present, is a photo of the view from that section. eventNotes, when present, are notes supplied with the event's ticket list; read them to your human word for word. Use it after the overview to show specific seats. Pass qty for the number of tickets, maxPrice for the highest all-in price per ticket, and section for a section name from get_seating_overview. Listings come 25 at a time; pass limit for up to 100. totalCount is how many match. When nextCursor is set, pass it as cursor for the next page; it is null on the last page. When you omit limit and more listings match, hint is set. layout, supplier and sellersChecked appear once on the response, not on each listing. competitorEvents, the other sites' links for this event, also appears once when a ready comparison has a link, and a listing's comparison text does not repeat that link. Parking, hotel and pass listings are left out unless includeNonEntry is true. When price comparison is on, each listing's priceComparison has the verdict, the text and the best competitor price, and comparisonStatus is cheaper_found, none_cheaper, no_match, pending or not_checked. - get_quote (POST /v1/quotes): Re-checks the listing and quantity live and returns a quote: the listing, the expected all-in total and its tolerance, the seller's checkout URL with the steps to follow, the merchant name, merchant URL and context to copy exactly into the Link spend request your human approves, the delivery text and an expiry. Call it after your human confirms the seats, quantity and price. Send listingId and qty. A quote expires after about 10 minutes. It does not hold seats or lock the price. To check the same ticket group and quantity, call get_quote with previousQuoteId set to that quote's ID, and do not send listingId or qty. The response adds refresh: previousQuoteId, previousExpectedTotalCents, currentExpectedTotalCents, deltaCents, and status same, lower or higher, compared with that quote's stored total. Same or lower returns a new quote ID. Higher returns price_changed and no quote until your human confirms. Then call get_quote again with the same previousQuoteId and acceptedTotalCents set to the total they confirmed. If the live total is above that, it refuses again. When price comparison is on, the quote and its listing also have comparisonStatus next to priceComparison. Open the quote's checkout URL in your browser and pay with Link after your human approves. Give the URL to your human to pay the seller themselves only if the total is over their Link limits, you can't use Link or a browser, or they ask. - check_quote (POST /v1/quotes/{id}/check): Call it right before you press Place Order. Re-checks the quote's listing live and compares the live total with the quote's expected total. same or lower: go ahead and place the order. higher: stop and ask your human to confirm the new total before you buy. If it is expired, call get_quote with previousQuoteId set to that quote's ID, without listingId or qty. If it is gone, stop and tell your human those tickets are no longer available; do not choose different tickets without asking them. - report_outcome (POST /v1/outcomes): Optional but helpful. After checkout, report the quoteId from get_quote, status succeeded, failed, or handed_off when you gave your human the checkout link, the reason if it failed (declined_by_seller, captcha, price_changed, listing_gone, approval_declined, approval_expired, total_over_quote, no_browser, no_link, other), the confirmation number, and the totals you saw. Never include anything about your human: no name, email, phone or address.