Salt Labs
Salt Labs is the New York company behind Salt, an employee rewards and loyalty benefit for hourly and frontline workers. Founded in 2022 by Jason Lee and founding members of DailyPay, Salt turns time worked into a points-based asset: an employee earns one Salt for every hour on the job through the Salt Rewards mobile app, and redeems accumulated Salt for merchandise, travel, experiences, education benefits, and investment products such as stock and treasury bonds. Salt is sold to employers across transportation, contact centers, hospitality, and parking services as a retention and engagement program modeled on airline miles and credit-card points. Salt Labs was acquired by Chime Financial in June 2024 and now operates as "Salt, a Chime Company", with founder Jason Lee leading the Chime Enterprise business unit. Salt Labs publishes no public developer program, API reference, or machine-readable contract; its only machine-readable first-party surface is the Atlassian Statuspage at status.saltlabs.com, which exposes public JSON and RSS availability feeds for the Salt App Backend.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Salt Labs the way a machine reads it — 2 machine-readable artifacts, 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 — Salt Labs scores 13.4/100 (emerging), 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
Salt Labs ships an employee-facing mobile rewards app and an employer program sold through a demo form; its full 30-URL sitemap has no developer, docs or API section, no api./developer./ docs. subdomain resolves, and every contract-discovery path on www.saltlabs.com and app.saltlabs.com returns a discriminating 404 — the only machine-readable thing it publishes is the Atlassian Statuspage JSON feed at status.saltlabs.com.
This is an honest zero, not a gap in our research. Salt Labs 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.saltlabs.com/sitemap.xml→ HTTP 200https://www.saltlabs.com/openapi.json→ HTTP 404https://app.saltlabs.com/api/v1/openapi.json→ HTTP 404https://www.saltlabs.com/.well-known/agent-card.json→ HTTP 404https://status.saltlabs.com/api/v2/summary.json→ 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-01 · rubric v0.18.0
Put this on your own site. The badge is drawn live from Salt Labs'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/salt-labs/"
title="Salt Labs on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/salt-labs.svg"
alt="Salt Labs Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/salt-labs/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/salt-labs/"
title="Salt Labs on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/salt-labs/card.svg"
alt="Salt Labs 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 Salt Labs
Each block below is one kind of artifact we hold for Salt Labs. 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.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
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 Salt Labs — 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.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/salt-labs · machine-readable index on apis.io
This is an independent, third-party profile of Salt Labs, 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.