Brightloom
Brightloom is a San Francisco customer data and customer intelligence platform for restaurant and retail brands. It began as Eatsa, the automated quinoa-bowl restaurant chain, and rebranded to Brightloom in 2019 when Starbucks licensed select components of its Digital Flywheel customer engagement software to the company, took an equity stake and a board seat alongside a $30M round. The product unifies point-of-sale, loyalty, ecommerce and marketing data into a single customer view, reports on data health, runs AI-driven hyper-segmentation and anomaly detection over that data, and recommends the next campaign and audience a brand should target. Brightloom was sold as an end-user SaaS with prebuilt connectors to common POS, loyalty and marketing platforms rather than as a developer platform, and it published no public API reference, developer portal, SDK or machine-readable specification. The company now appears defunct: the last dated item on its own press page is December 2022, the entire operating estate it once held TLS certificates for is gone from DNS — api.brightloom.com, api-prd/api-dev, the cgp.brightloom.com application, its auth0-cgp Auth0 tenant, and the status, support and knowledgebase hosts all NXDOMAIN — brightloom.com publishes no MX record, and only the frozen marketing site remains, with its /about/ page defaced by injected search-spam.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Brightloom the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Brightloom scores 5.0/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Brightloom's operating estate has been decommissioned — Certificate Transparency shows it ran api.brightloom.com, api-prd/api-dev, the cgp.brightloom.com Customer Growth Platform app, an auth0-cgp Auth0 tenant, and status/support/knowledgebase hosts, and all sixteen of those hostnames now return NXDOMAIN while brightloom.com carries no MX record, leaving only a marketing site frozen at its December 2022 press release whose own nav links (/how-it-works/, /integrations/, /sign-up/) 404 and whose /about/ page serves injected Indonesian gambling search-spam.
This is an honest zero, not a gap in our research. Brightloom does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://www.brightloom.com/→ HTTP 200https://www.brightloom.com/integrations/→ HTTP 404https://www.brightloom.com/sign-up/→ HTTP 404https://www.brightloom.com/openapi.json→ HTTP 404https://www.brightloom.com/graphql→ HTTP 404https://www.brightloom.com/.well-known/agent-card.json→ HTTP 404https://www.brightloom.com/.well-known/api-catalog→ HTTP 404https://api.brightloom.com/openapi.json→ HTTP 0https://crt.sh/?q=%25.brightloom.com→ HTTP 200
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Brightloom's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/brightloom/"
title="Brightloom on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/brightloom.svg"
alt="Brightloom Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/brightloom/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/brightloom/"
title="Brightloom on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/brightloom/card.svg"
alt="Brightloom Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Brightloom
Each block below is one kind of artifact we hold for Brightloom. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Brightloom — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 5
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/brightloom · machine-readable index on apis.io
This is an independent, third-party profile of Brightloom, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.