FreshToHome
FreshToHome (Freshtohome Foods Private Limited) is a Bangalore-headquartered direct-to-consumer e-commerce company selling fresh, antibiotic-residue-free fish, seafood, poultry, mutton, ready-to-cook and heat-and-eat food. Founded in 2015 by Shan Kadavil, Mathew Joseph and Jayesh Jose, it runs its own farm-and-boat-to-doorstep cold chain, sourcing from thousands of fishermen and farmers and delivering across cities in India and the United Arab Emirates. The company sells through its website and its consumer iOS and Android apps. It publishes an llms.txt at its web root but operates no public developer program, API reference, or machine-readable API contract.
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 FreshToHome the way a machine reads it — 3 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 — FreshToHome scores 11.3/100 (minimal), with a separate agent-readiness read of 3/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
FreshToHome is a direct-to-consumer food e-commerce business, not a software vendor, and it markets no API: there is no developer host (developers., docs., apis. all NXDOMAIN), no developer link anywhere in the site navigation or footer, no GitHub organization, and no client library on npm, PyPI, RubyGems, crates.io or Packagist. The one API host that does resolve, api.freshtohome.com, is the private backend for its own consumer web and mobile apps — it answers every path, including every /.well-known/ path and every OpenAPI/Swagger/GraphQL location, with HTTP 400 {"success":"error","message":"No token provided."}, and no public reference for it is published anywhere. The single machine-readable document the company does serve is a genuine hand-authored llms.txt at the web root, captured verbatim in llms/, and it describes seven product categories and the support and legal pages — it names no API.
This is an honest zero, not a gap in our research. FreshToHome 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.freshtohome.com/llms.txt→ HTTP 200https://api.freshtohome.com/openapi.json→ HTTP 400https://www.freshtohome.com/openapi.json→ HTTP 404https://www.freshtohome.com/graphql→ HTTP 404https://www.freshtohome.com/.well-known/agent-card.json→ HTTP 404https://api.github.com/orgs/freshtohome→ HTTP 404
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 FreshToHome'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/freshtohome/"
title="FreshToHome on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/freshtohome.svg"
alt="FreshToHome Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/freshtohome/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/freshtohome/"
title="FreshToHome on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/freshtohome/card.svg"
alt="FreshToHome 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 FreshToHome
Each block below is one kind of artifact we hold for FreshToHome. 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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Freshtohome Rate Limits
RATE LIMITSSecurity 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 FreshToHome — 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
Access & Security 1
Authentication, authorization, and security posture
Operate 3
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
← All providers · Data indexed from github.com/api-evangelist/freshtohome · machine-readable index on apis.io
This is an independent, third-party profile of FreshToHome, 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.