Splash 360

French vendor of point-of-sale and management software for collective catering — company restaurants, school and institutional canteens. The product line covers a smart till, self-service ordering kiosks and kiosk software, Wifi Order, a Kitchen Display System, a back-office management layer, a coin handler, and loyalty through a YouFid integration. NO PUBLIC API SURFACE: the company sells and deploys into catering operators directly, and publishes no developer portal, API documentation or machine-readable contract. That is the absence of a PUBLIC interface, not the absence of APIs — a till, a kiosk and a kitchen display exchanging orders are API-driven by construction, but those interfaces reach customers through deployment and integration work rather than a public developer program.

Splash 360 is profiled on the APIs.io network. Tagged areas include Point-of-Sale, Collective Catering, Food Service, Restaurant Technology, and Kiosk.

Splash 360’s developer surface includes engineering blog and 1 more developer resources.

🌐 Visit website 📡 Source on GitHub
4.6/100 minimal Agent 0/100 human only Full breakdown ↓
scored 2026-08-20 · rubric v0.12.0
0 APIs
Point-of-SaleCollective CateringFood ServiceRestaurant TechnologyKioskKitchen DisplayLoyaltyBack OfficeFranceHospitality

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-20 · rubric v0.12.0
Composite quality — 4.6/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.5 / 20
Access Clarity 0.0 / 20
Operational Transparency 0.0 / 13
Contract Governance 0.0 / 12
Discoverability 4.1 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/splash360: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

Resources

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: splash360
name: Splash 360
description: 'French vendor of point-of-sale and management software for collective catering — company restaurants, school
  and institutional canteens. The product line covers a smart till, self-service ordering kiosks and kiosk software, Wifi
  Order, a Kitchen Display System, a back-office management layer, a coin handler, and loyalty through a YouFid integration.
  NO PUBLIC API SURFACE: the company sells and deploys into catering operators directly, and publishes no developer portal,
  API documentation or machine-readable contract. That is the absence of a PUBLIC interface, not the absence of APIs — a till,
  a kiosk and a kitchen display exchanging orders are API-driven by construction, but those interfaces reach customers through
  deployment and integration work rather than a public developer program.'
url: https://raw.githubusercontent.com/api-evangelist/splash360/refs/heads/main/apis.yml
created: '2026-08-19'
modified: '2026-08-19'
specificationVersion: '0.23'
tags:
- Point-of-Sale
- Collective Catering
- Food Service
- Restaurant Technology
- Kiosk
- Kitchen Display
- Loyalty
- Back Office
- France
- Hospitality
tags_raw:
- Point of Sale
- Collective Catering
- Food Service
- Restaurant Technology
- Kiosk
- Kitchen Display
- Loyalty
- Back Office
- France
- Hospitality
apis: []
common:
- type: Website
  url: https://splash360.fr
- type: Blog
  url: https://splash360.fr/blog
maintainers:
- FN: Splash 360
  url: https://splash360.fr
x-evidence:
  round: '2026-08-19'
  admitted_from: Add-API parked queue, submission splash-360-fdc34922, gate confidence 3, reason no_consumable_surface.
  why_listed_not_dropped: no_consumable_surface is not sufficient grounds to drop. The question is whether this is a real
    company on a domain it owns, and it is. splash360.fr returns 200 with 223,583b and a real product site; an invented path
    returns a genuine 404, so the host discriminates. A valid company with no public API gets listed and scores low — the
    low score is the point, and it is what gives the vendor something to act on.
  dev_surface_probed_2026_08_19: /api, /developers, /developpeurs, /docs, /openapi.json, /apis.json and /llms.txt all return
    404. Probed with a browser user-agent, so these are real absences and not a bot-protection artifact masking them.
  wording: Recorded as no PUBLIC API surface rather than no APIs. Tills, kiosks and kitchen displays exchanging orders are
    API-driven by construction; those interfaces simply do not reach a public developer program.