Relish is a consumer product operated at hellorelish.com and backed by Bullpen Capital, added to the API Evangelist network as a venture-portfolio lead. Live enrichment probing found the marketing site sitting behind a bot/captcha challenge and marked noindex, with no developer, API, or documentation subdomains resolving, no first-party GitHub organization, no published SDK packages, and no machine-readable well-known files. No public API surface was discovered during enrichment; the only verified technical artifact is a domain-security posture probe (TLS 1.3, SPF and DMARC present, no HSTS/DNSSEC/CAA records).
Relish is profiled on the APIs.io network. Tagged areas include Company, Consumer, Venture Backed, Bullpen Capital, and No Public API.
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.
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 github.com/api-evangelist/relish: open an issue to ask a question, or submit a pull request to add artifacts.
Submit an artifact on GitHub — free →Manage your own listing — the Influence plan, $499/mo →
aid: relish
deliveryModel:
model: unknown
open_source: false
commercial: false
callable_host: false
label: Delivery model not determined — needs a product licence on record
confidence: low
source:
- none
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source:
- url: https://hellorelish.com
status: 301
note: declared website redirects to https://www.DropCatch.com/domain/hellorelish.com — a different registrable domain
(hellorelish.com -> dropcatch.com), possible rename or acquisition (probed 2026-09-03, roadmap#169)
generated: '2026-07-22'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/relish.png
name: Relish
description: Relish is a consumer product operated at hellorelish.com and backed by Bullpen Capital, added to the API Evangelist
network as a venture-portfolio lead. Live enrichment probing found the marketing site sitting behind a bot/captcha challenge
and marked noindex, with no developer, API, or documentation subdomains resolving, no first-party GitHub organization, no
published SDK packages, and no machine-readable well-known files. No public API surface was discovered during enrichment;
the only verified technical artifact is a domain-security posture probe (TLS 1.3, SPF and DMARC present, no HSTS/DNSSEC/CAA
records).
url: https://raw.githubusercontent.com/api-evangelist/relish/refs/heads/main/apis.yml
x-api-posture: no-product-api
x-api-posture-basis: observed
x-api-posture-note: No public API surface was discovered during enrichment; the only verified technical artifact is a domain-security
posture probe (TLS 1.3, SPF and DMARC present, no HSTS/DNSSEC/CAA records).
x-type: company
x-source: vc-portfolio
x-backed-by:
- bullpen-capital
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Consumer
- Venture Backed
- Bullpen Capital
- No Public API
apis: []
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: DomainSecurity
url: security/relish-domain-security.yml
- type: Website
url: https://hellorelish.com
x-enrichment:
date: '2026-07-21'
status: minimal
artifacts_added: 1
pass: local-v1
Discovery needs no key. Ratings and market analysis are Pro.
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.