Let your fans create the hype and see your reach explode.
Every vote, reaction and achievement is a share card for link previews and a story for Instagram, from a single API.
Every vote, reaction and achievement is a share card for link previews and a story for Instagram, from a single API.
Every template produces OG link previews and Instagram-ready story cards, wherever fans share.
Fan votes, predicts, or unlocks an achievement. Your backend fires one API call. HypeCard renders a personalised card and returns a short link the fan can share immediately.
Register your org once. HypeCard connects to your sports data provider, detects lineup confirmations and kick-off events, then renders and caches cards automatically. The URL never changes.
Connect your sports data feed once. HypeCard watches for lineup confirmations arriving before kick-off, then renders and caches the card. Serve the same URL at any point - pre-match, post-confirmation, post-match - and always get the current state.
RosterCache. Short-name overrides per org. 1-hour in-memory TTL.max-age=60 pre-confirmation, jumps to 300s on lineup lock. Same URL, CloudFront handles it.opta or sportmonks. Override per-request with ?source=..jpg/.png or a live HTML card using the hypecard-ddc-v1 PostMessage protocol.No image generation infrastructure. No CDN to configure. No crawler handling to figure out.
Write HTML with {{variableName}} placeholders. Inline your styles. We render at 1200x630 (OG) or 1080x1920 (Story) with support for gradients, custom fonts, and layered layouts. Set format: "story" for Instagram-ready 9:16 cards.
One API call with your fan's data. We fill the template, render it asynchronously, and hand you back a short link. Poll once – it's usually ready in under a second.
Post the link on Twitter, WhatsApp, LinkedIn, anywhere. Social crawlers automatically fetch the OG image and render a rich preview card. No extra setup.
When a fan taps the link, they're redirected straight back to your platform. Attribution parameters are automatically appended so you know exactly which share drove each visit.
Pick a template, fill in the variables, get a live share link.
templateId used for all subsequent operations. Templates are versioned, you never edit HTML in place, you add a new version.1200x630 (OG) or 1080x1920 (Story). Use {{variable}} tokens. Inline all CSS for fast renders.organisationId: "_system"). System templates are always visible to every org.status: "pending" immediately. Poll GET /v1/shares/:id until status === "ready". The format field selects which template format to render: og (1200×630) or story (1080×1920). Defaults to og.status === "ready". Inline-CSS templates: 3–5s. Google Fonts: up to ~30s. Once ready, shareUrl and renderArtifactId are populated.shareUrl returns 404 immediately after deletion.Share cards your fans create, and cards that generate themselves from live match data. Design once, render instantly, share everywhere.
HypeCard exposes a full MCP (Model Context Protocol) endpoint. Point any Claude or OpenAI-compatible agent at /mcp and it can browse templates, generate custom HTML, create shares, and return preview URLs – no human in the loop.