Lucky Cart

Lucky Cart is a French MarTech company specializing in retail media and smart commerce for grocery and consumer-goods retailers. It combines first-party transactional data with e-retail media, machine learning, and AI to power personalized shopper engagement, gamified promotions, and the monetization of retailer audiences at scale. Lucky Cart works with major French grocery retailers and CPG brands to activate transactional data into targeted advertising, loyalty, and measurable campaigns. Its integration surface is a set of HTTP APIs consumed through three first-party SDKs published on GitHub — a shopper-event ingest, a promotional banner displayer, a cart-to-ticket endpoint that mints the post-purchase game, and a hosted game experience. Lucky Cart publishes no OpenAPI, no developer portal and no self-service signup: API keys are issued manually by its integration team to contracted retailers, and its Help Centre is access-restricted.

Lucky Cart is listed with 6 APIs on the APIs.io network. Tagged areas include Company, Retail Media, MarTech, E-Commerce, and Advertising.

Lucky Cart’s developer surface includes support, engineering blog, documentation, authentication, and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

26.0/100 emerging ▬ flat Agent 5/100 human only Front door AI 3/6 light Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

6 APIs

Company Retail Media MarTech E-Commerce Advertising Personalization Loyalty Consumer Packaged Goods Grocery Promotions GamificationShopper MarketingFirst-Party Data France

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 26.0/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 6.1 / 17

Access Clarity 6.0 / 17

Operational Transparency 0.3 / 11

Contract Governance 1.9 / 10

Discoverability 6.1 / 9

Regulatory Posture 4.4 / 15

Agent readiness — 5/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 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 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/lucky-cart/"><img src="https://apis.io/badge/lucky-cart/card.svg" alt="Lucky Cart on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 35.7 — up to +12.9 composite points
Access Clarity scores 35.5 — up to +12.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/lucky-cart/apis.yml: open an issue on github.com/api-evangelist/lucky-cart to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 6

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

Lucky Cart Core API

The core Lucky Cart API. POST /cart/ticket submits a validated shopping cart — cart identifier, shopper identifier, gross and net amounts, and product lines — and Lucky Cart det...

Lucky Cart Shopper Events API

Event ingest for shopper behaviour on a retailer storefront. A single POST /event endpoint accepts {shopperId, siteKey, eventName, payload}, where eventName is a Lucky Cart even...

Lucky Cart Shopper Experience API

Returns the set of Lucky Cart experiences currently available to a given shopper. GET /experiences takes shopperId, siteKey and an experienceType filter as query parameters and ...

Lucky Cart Game Experience API

Grants access to the gamified post-purchase experiences a shopper has earned. GET /game-experiences-access takes shopperId, siteKey and a count parameter capping how many experi...

Lucky Cart Displayer API

Selects and returns the promotional banner to render for a given page context. The route encodes the whole selection key in the path — /{siteKey}/{shopper}/banner/{platform}/ {p...

Lucky Cart Promo Matching API

The promo-matching and creative-delivery host used by the JavaScript SDK. It serves the same banner selection routes as the displayer — /{siteKey}/{shopper}/banner|banners/{subs...

Lucky Cart API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Lucky Cart Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Lucky Cart Rate Limits

0 limits

RATE LIMITS

Security Posture 2

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

Lucky Cart Authentication

apiKey/custom-hmac-signature · 3 schemes

SECURITY

Lucky Cart Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Login

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Conventions

Components

Conformance

Lifecycle

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Compliance

Compliance

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Plans

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: lucky-cart
name: Lucky Cart
description: 'Lucky Cart is a French MarTech company specializing in retail media and smart commerce for grocery and consumer-goods
  retailers. It combines first-party transactional data with e-retail media, machine learning, and AI to power personalized
  shopper engagement, gamified promotions, and the monetization of retailer audiences at scale. Lucky Cart works with major
  French grocery retailers and CPG brands to activate transactional data into targeted advertising, loyalty, and measurable
  campaigns. Its integration surface is a set of HTTP APIs consumed through three first-party SDKs published on GitHub — a
  shopper-event ingest, a promotional banner displayer, a cart-to-ticket endpoint that mints the post-purchase game, and a
  hosted game experience. Lucky Cart publishes no OpenAPI, no developer portal and no self-service signup: API keys are issued
  manually by its integration team to contracted retailers, and its Help Centre is access-restricted.'
url: https://raw.githubusercontent.com/api-evangelist/lucky-cart/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  license_evidence:
    not_product:
    - lucky-cart/lucky-cart-ios
    - lucky-cart/luckycart-js-sdk
  open_source: unknown
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: low
  source:
  - pricing
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: none-published
  onboarding: sales
  trial: false
  try_now: false
  public: false
  label: Enterprise sales only
  confidence: high
  source:
  - https://www.luckycart.com/en/contact
  - https://github.com/lucky-cart/luckycart-js-sdk#initialization
  generated: '2026-08-12'
  method: searched
image: https://cdn.prod.website-files.com/68c2baa88e31954e039031a7/68d2e246b13b0428fe573013_lucky-cart-share.avif
x-type: company
x-source: vc-portfolio
x-backed-by:
- partech
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-12'
tags:
- Company
- Retail Media
- MarTech
- E-Commerce
- Advertising
- Personalization
- Loyalty
- Consumer Packaged Goods
- Grocery
- Promotions
- Gamification
- Shopper Marketing
- First-Party Data
- France
tags_raw:
- Company
- Retail Media
- MarTech
- E-Commerce
- Advertising
- Personalization
- Loyalty
- CPG
- Grocery
- Promotions
- Gamification
- Shopper Marketing
- First-Party Data
- France
apis:
- aid: lucky-cart:core-api
  name: Lucky Cart Core API
  description: 'The core Lucky Cart API. POST /cart/ticket submits a validated shopping cart — cart identifier, shopper identifier,
    gross and net amounts, and product lines — and Lucky Cart determines whether a game can be generated, returning a ticket
    plus the device-specific intro image and game URL. This is the only signed endpoint: the request body carries auth_ts,
    auth_key, auth_v "2.0" and auth_sign, an HMAC-SHA256 digest of the timestamp keyed by the site secret. Game data is read
    back at /{siteKey}/game/{cartId} or /{siteKey}/game/cust/{shopperId}, optionally suffixed with the device. Cart ingestion
    is asynchronous, so the read returns the literal error "Cart not found" until it completes and clients poll on a bounded
    attempt budget.'
  humanURL: https://github.com/lucky-cart/luckycart-js-sdk#send-the-current-transaction
  baseURL: https://api.luckycart.com
  tags:
  - Transaction
  - Promotions
  - Gamification
  tags_raw:
  - Transactions
  - Promotions
  - Gamification
  properties:
  - type: Authentication
    url: authentication/lucky-cart-authentication.yml
  - type: Conventions
    url: conventions/lucky-cart-conventions.yml
  - type: SourceCode
    url: https://github.com/lucky-cart/luckycart-js-sdk
- aid: lucky-cart:shopper-events-api
  name: Lucky Cart Shopper Events API
  description: Event ingest for shopper behaviour on a retailer storefront. A single POST /event endpoint accepts {shopperId,
    siteKey, eventName, payload}, where eventName is a Lucky Cart event such as pageViewed or cartValidated and the payload
    carries the page context — pageType, pageId, storeType and storeId. Events are what make a shopper eligible for banner
    selection and for a game experience, so the event call precedes every banner or experience read in the documented integration
    workflow. The service is versioned in the URI path at /v1 and accepts an empty response body on success.
  humanURL: https://github.com/lucky-cart/lucky-cart-ios#pageviewed-event
  baseURL: https://shopper-events.luckycart.com/v1
  tags:
  - Event
  - Analytics
  - Shopper Marketing
  tags_raw:
  - Events
  - Analytics
  - Shopper Marketing
  properties:
  - type: Authentication
    url: authentication/lucky-cart-authentication.yml
  - type: SourceCode
    url: https://github.com/lucky-cart/lucky-cart-ios
- aid: lucky-cart:shopper-experience-api
  name: Lucky Cart Shopper Experience API
  description: Returns the set of Lucky Cart experiences currently available to a given shopper. GET /experiences takes shopperId,
    siteKey and an experienceType filter as query parameters and answers with the experiences that shopper is eligible for.
    Used by the web SDK to decide what to surface to a returning shopper independently of a specific cart. Versioned in the
    URI path at /v1. No pagination is offered on the collection.
  humanURL: https://github.com/lucky-cart/luckycart-js-sdk
  baseURL: https://shopper-experience.luckycart.com/v1
  tags:
  - Experience
  - Personalization
  tags_raw:
  - Experiences
  - Personalization
  properties:
  - type: Authentication
    url: authentication/lucky-cart-authentication.yml
  - type: SourceCode
    url: https://github.com/lucky-cart/luckycart-js-sdk
- aid: lucky-cart:game-experience-api
  name: Lucky Cart Game Experience API
  description: Grants access to the gamified post-purchase experiences a shopper has earned. GET /game-experiences-access
    takes shopperId, siteKey and a count parameter capping how many experiences to return, and answers with the game experiences
    and the template each should be rendered with. The mobile SDKs call this after a cartValidated event to decide which game
    to present. Versioned in the URI path at /v1. The count parameter is the only collection-bounding mechanism — there is
    no cursor or offset.
  humanURL: https://github.com/lucky-cart/lucky-cart-ios#configuration
  baseURL: https://game-experience-api.luckycart.com/v1
  tags:
  - Gamification
  - Loyalty
  - Experience
  tags_raw:
  - Gamification
  - Loyalty
  - Experiences
  properties:
  - type: Authentication
    url: authentication/lucky-cart-authentication.yml
  - type: SourceCode
    url: https://github.com/lucky-cart/lucky-cart-ios
- aid: lucky-cart:displayer-api
  name: Lucky Cart Displayer API
  description: Selects and returns the promotional banner to render for a given page context. The route encodes the whole
    selection key in the path — /{siteKey}/{shopper}/banner/{platform}/ {pageType}/{format} for a single promotion, or /banners/
    for every matching promotion — with pageId, store and store_type as optional query parameters for finer targeting such
    as store-local promotions. Platform distinguishes desktop, mobile and webmobile inventory. The response carries the image
    URL, the click-through URL, the campaign identifier and the campaign name. This host is unversioned.
  humanURL: https://github.com/lucky-cart/lucky-cart-ios#request-the-banner-data
  baseURL: https://displayer.luckycart.com
  tags:
  - Retail Media
  - Advertising
  - Banners
  properties:
  - type: Authentication
    url: authentication/lucky-cart-authentication.yml
  - type: Components
    url: components/lucky-cart-components.yml
  - type: SourceCode
    url: https://github.com/lucky-cart/lucky-cart-ios
- aid: lucky-cart:promo-matching-api
  name: Lucky Cart Promo Matching API
  description: The promo-matching and creative-delivery host used by the JavaScript SDK. It serves the same banner selection
    routes as the displayer — /{siteKey}/{shopper}/banner|banners/{subset}/ {pageType}/{format} where subset is desktop, mobile
    or webmobile — and additionally serves the creative itself and the click-through redirect at /{campaignId}/{customer}/image
    and /{campaignId}/{customer}/jump. Those two per-campaign, per-customer URLs are how impression and click attribution
    are bound to an individual shopper. Unversioned; answers 204 at its root.
  humanURL: https://github.com/lucky-cart/luckycart-js-sdk#display-banners
  baseURL: https://promomatching.luckycart.com
  tags:
  - Retail Media
  - Advertising
  - Attribution
  properties:
  - type: Components
    url: components/lucky-cart-components.yml
  - type: SourceCode
    url: https://github.com/lucky-cart/luckycart-js-sdk
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/lucky-cart-domain-security.yml
- type: Website
  url: https://www.luckycart.com/
- type: Support
  url: https://www.luckycart.com/contact
- type: Blog
  url: https://www.luckycart.com/actualites
- type: PrivacyPolicy
  url: https://www.luckycart.com/politique-de-confidentialite
- type: TermsOfService
  url: https://www.luckycart.com/mentions-legales
- type: GitHubOrganization
  url: https://github.com/lucky-cart
- type: Documentation
  url: https://github.com/lucky-cart/luckycart-js-sdk#readme
- type: Login
  url: https://app.luckycart.com/
- type: Packages
  url: packages/lucky-cart-packages.yml
- type: SDKs
  url: packages/lucky-cart-packages.yml
- type: Authentication
  url: authentication/lucky-cart-authentication.yml
- type: Conventions
  url: conventions/lucky-cart-conventions.yml
- type: Components
  url: components/lucky-cart-components.yml
- type: Conformance
  url: conformance/lucky-cart-conformance.yml
- type: Compliance
  url: https://www.luckycart.com/en/certifications
- type: Lifecycle
  url: lifecycle/lucky-cart-lifecycle.yml
- type: Plans
  url: plans/lucky-cart-plans-pricing.yml
- type: RateLimits
  url: rate-limits/lucky-cart-rate-limits.yml
- type: LLMsTxt
  url: llms/lucky-cart-llms.txt
x-enrichment:
  date: '2026-08-12'
  status: enriched
  artifacts_added: 10
  pass: local-v1

Lucky Cart API — frequently asked questions

Does Lucky Cart have an API?

Yes. APIs.io lists 6 APIs from Lucky Cart, including Lucky Cart Core API, Lucky Cart Shopper Events API and Lucky Cart Shopper Experience API, and 3 more.

How do I authenticate with the Lucky Cart API?

Lucky Cart uses bearer-token authentication (apiKey/custom-hmac-signature · 3 schemes). The details are profiled on APIs.io as Lucky Cart Authentication.

Is the Lucky Cart API ready for AI agents?

Lucky Cart has a Kin Score of 26.0 out of 100 (emerging) and an Agent Readiness score of 5.0 (human-only), scored by API Evangelist on 2026-11-06.

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/lucky-cart"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/lucky-cart/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.