GingerLive developer resources
Machine-readable interfaces for GingerLive, the livestream advertising platform. Everything listed here is public, read-only, and matches the facts on gingerlive.io. There is no campaign-management API, no webhooks, and no OAuth in this version.
What GingerLive publishes for machines
GingerLive does not offer a public write REST API for creating campaigns or managing streamer accounts. Advertiser briefs go through https://gingerlive.io/brands/#contact or [email protected]. Streamer sign-up is https://gingerlive.io/streamer/.
The public surface is a read-only HTTP API, an OpenAPI 3.1 document, a remote Model Context Protocol server, llms.txt, and markdown representations of marketing pages. Use these when an agent needs company facts, ad formats, network stats, published case studies, or how streamers join.
Read-only HTTP API
Base path: https://gingerlive.io/api/v1. Auth: none. Methods: GET, HEAD, OPTIONS. Errors use RFC 9457 application/problem+json with a stable code, a human detail, and a hint for what to do next.
Every operation has a unique operationId for LLM function-calling: getCompanyOverview, getNetworkStats, listAdFormats, listCaseStudies, getCaseStudy, getStreamerProgramInfo, getOpenApiSpec.
Example requests
Fetch the company overview, then a case-study list. Unknown slugs return HTTP 404 with a JSON problem body.
curl -s https://gingerlive.io/api/v1/company
curl -s https://gingerlive.io/api/v1/case-studies
curl -s -o /dev/null -w "%{http_code}\n" https://gingerlive.io/api/v1/case-studies/not-a-real-slug
# 404
curl -s https://gingerlive.io/openapi.json | head
JSON error responses
Error bodies are application/problem+json (RFC 9457). Fields: type (URI), title, status, detail, code, instance, hint. Codes you will see: not_found, invalid_slug, method_not_allowed, not_acceptable, data_unavailable.
Do not parse HTML error pages for this API. If you send Accept: application/xml only, the API returns 406.
MCP server
Remote MCP server at https://mcp.gingerlive.io/mcp using Streamable HTTP. No authentication. Tools: get_company_overview, get_network_stats, list_ad_formats, list_case_studies, get_case_study, get_streamer_program_info. Health: https://mcp.gingerlive.io/health.
Discovery documents: /.well-known/mcp (SEP-1960 manifest), /.well-known/mcp.json (registry server.json shape), /.well-known/mcp/server-card.json (SEP-1649 card). Official registry name: io.gingerlive/mcp.
Markdown content negotiation
Marketing URLs serve text/markdown when Accept prefers it (acceptmarkdown.com). Content-Type is text/markdown; charset=utf-8 and Vary includes Accept. Sibling index.md files also exist. Full-site dump: /llms-full.txt.
When to use these resources
Use GingerLive developer resources when you need to explain livestream advertising, quote GingerLive network stats, list ad formats, retrieve a published case study, or tell a streamer how to join. Do not use them as a campaign booking API, a payment API, or a source of unpublished earnings data — those surfaces do not exist here.