HungryPanda

HungryPanda (熊猫外卖) is the largest Asian food delivery platform serving overseas Chinese communities, founded in Nottingham, UK in 2017 and headquartered in London. It operates a marketplace app, a rider delivery network, the Panda Fresh Asian grocery e-commerce platform and the VouchersPanda lifestyle-deals platform across more than 80 cities in ten countries (UK, France, Italy, USA, Canada, Australia, New Zealand, Japan, South Korea and Singapore). Its API surface is a regionally partitioned merchant/partner ordering platform used by POS and middleware integrators — Deliverect, Otter, Neopos, Hubster, Menusifu, Easy Cloud and Redcat — to inject HungryPanda orders into a restaurant point of sale, push order-status updates back, and sync menus. Integration credentials (App Key, Secret Key, ShopID) are issued by HungryPanda on a partner basis; there is no public developer portal, no published specification and no self-service sign-up.

HungryPanda publishes 1 API on the APIs.io network. Tagged areas include Company, Food Delivery, Delivery, Marketplace, and Restaurants.

HungryPanda’s developer surface includes signup flow, support, engineering blog, and 10 more developer resources.

11.9/100 emerging ▬ flat Agent 3/100 human only Full breakdown ↓
scored 2026-08-25 · rubric v0.14.0
1 APIs
CompanyFood DeliveryDeliveryMarketplaceRestaurantsGroceryLogisticsE-CommerceMerchantsPoint of Sale

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-25 · rubric v0.14.0
Composite quality — 11.9/100 · emerging
Contract Quality 0.0 / 21
Developer Ergonomics 1.2 / 17
Access Clarity 4.0 / 17
Operational Transparency 0.0 / 11
Contract Governance 0.0 / 10
Discoverability 5.8 / 9
Regulatory Posture 3.8 / 15
Agent readiness — 3/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 7 / 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
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
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/hungrypanda: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

HungryPanda Merchant & Partner API

The regionally partitioned HTTP API behind the HungryPanda merchant back office (merchant.hungrypanda.co) and the POS/middleware partner integrations. It carries merchant onboar...

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Hungrypanda Rate Limits

0 limits

RATE LIMITS

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hungrypanda Authentication

0 schemes

SECURITY

Hungrypanda Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Hungrypanda Vulnerability Disclosure

Hackerone · contact published

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

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

Source (apis.yml)

apis.yml Raw ↑
aid: hungrypanda
name: HungryPanda
description: HungryPanda (熊猫外卖) is the largest Asian food delivery platform serving overseas Chinese communities, founded
  in Nottingham, UK in 2017 and headquartered in London. It operates a marketplace app, a rider delivery network, the Panda
  Fresh Asian grocery e-commerce platform and the VouchersPanda lifestyle-deals platform across more than 80 cities in ten
  countries (UK, France, Italy, USA, Canada, Australia, New Zealand, Japan, South Korea and Singapore). Its API surface is
  a regionally partitioned merchant/partner ordering platform used by POS and middleware integrators — Deliverect, Otter,
  Neopos, Hubster, Menusifu, Easy Cloud and Redcat — to inject HungryPanda orders into a restaurant point of sale, push order-status
  updates back, and sync menus. Integration credentials (App Key, Secret Key, ShopID) are issued by HungryPanda on a partner
  basis; there is no public developer portal, no published specification and no self-service sign-up.
url: https://raw.githubusercontent.com/api-evangelist/hungrypanda/refs/heads/main/apis.yml
image: https://www.hungrypanda.co/assets/images/logo-400.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-22'
modified: '2026-08-22'
tags:
- Company
- Food Delivery
- Delivery
- Marketplace
- Restaurants
- Grocery
- Logistics
- E-Commerce
- Merchants
- Point of Sale
apis:
- aid: hungrypanda:merchant-api
  name: HungryPanda Merchant & Partner API
  description: The regionally partitioned HTTP API behind the HungryPanda merchant back office (merchant.hungrypanda.co) and
    the POS/middleware partner integrations. It carries merchant onboarding and authentication, shop/ERP administration, menu
    synchronisation, order injection and order-status callbacks. Every request is authenticated; an unauthenticated call to
    any path returns HTTP 200 with the JSON envelope {"code":40001}. No public specification, developer portal or self-service
    sign-up exists — App Key, Secret Key and ShopID are issued by HungryPanda to approved merchants and POS partners.
  humanURL: https://www.hungrypanda.co/merchants/
  baseURL: https://api-uk-f2e.hungrypanda.co
  tags:
  - Food Delivery
  - Orders
  - Menus
  - Merchants
  - Point of Sale
  properties:
  - type: Authentication
    url: authentication/hungrypanda-authentication.yml
  - type: ErrorCatalog
    url: errors/hungrypanda-problem-types.yml
  - type: Conventions
    url: conventions/hungrypanda-conventions.yml
  - type: Lifecycle
    url: lifecycle/hungrypanda-lifecycle.yml
  x-evidence:
    discovery: Regional API hosts read verbatim from the first-party merchant back-office bundle https://merchant.hungrypanda.co/bundle_8782eba0181f95878b4f.js
      (API_PROXY / GATEWAY config map), then probed live.
    probed: '2026-08-22'
    regional_bases:
    - https://api-uk-f2e.hungrypanda.co
    - https://api-usa-f2e.hungrypanda.co
    - https://api-eur-f2e.hungrypanda.co
    - https://api-ca-f2e.hungrypanda.co
    - https://api-aus-f2e.hungrypanda.co
    - https://api-nzd-f2e.hungrypanda.co
    - https://api-jp-f2e.hungrypanda.co
    - https://api-kr-f2e.hungrypanda.co
    - https://api-sg-f2e.hungrypanda.co
    gateway_hosts:
    - https://uk-gateway.hungrypanda.co
    - https://usa-gateway.hungrypanda.co
    - https://fr-gateway.hungrypanda.co
    - https://ca-gateway.hungrypanda.co
    - https://aus-gateway.hungrypanda.co
    - https://nzd-gateway.hungrypanda.co
    - https://jp-gateway.hungrypanda.co
    - https://kr-gateway.hungrypanda.co
    - https://sg-gateway.hungrypanda.co
    contract: No OpenAPI, Swagger, GraphQL, AsyncAPI, gRPC or WSDL contract is published on any HungryPanda host. STEP 0b
      discovery misses recorded in well-known/hungrypanda-well-known.yml.
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/hungrypanda-domain-security.yml
- type: Website
  url: https://www.hungrypanda.co/
- type: SignUp
  url: https://www.hungrypanda.co/merchants/
- type: Support
  url: https://www.hungrypanda.co/contact/
- type: PrivacyPolicy
  url: https://www.hungrypanda.co/privacy-policy/
- type: TermsOfService
  url: https://fast-leaflet-uk.hungrypanda.co/articleRule?appTypeId=1
- type: Blog
  url: https://www.hungrypanda.co/news-center/
- type: Security
  url: https://hpsrc.hungrypanda.co/
- type: VulnerabilityDisclosure
  url: security/hungrypanda-vulnerability-disclosure.yml
- type: Packages
  url: packages/hungrypanda-packages.yml
- type: LLMsTxt
  url: llms/hungrypanda-llms.txt
- type: Plans
  url: plans/hungrypanda-plans-pricing.yml
- type: RateLimits
  url: rate-limits/hungrypanda-rate-limits.yml
x-enrichment:
  date: '2026-08-22'
  status: minimal
  artifacts_added: 11
  pass: local-v1
x-coverage:
  state: gated
  reason: sales-gate
  detail: HungryPanda runs a real regionally partitioned merchant/partner ordering API — its own merchant back-office bundle
    names api-{uk,usa,eur,ca,aus,nzd,jp,kr,sg}-f2e.hungrypanda.co and matching regional gateways — but the only route to it
    is the merchant application form at hungrypanda.co/merchants/, and every anonymous call to the live API host answers HTTP
    200 with {"code":40001} while no host on the estate serves an OpenAPI, GraphQL SDL, WSDL, .proto or any /.well-known/
    document.
  evidence:
  - url: https://api-uk-f2e.hungrypanda.co/api/merchant/getCaptchagImage
    status: 200
  - url: https://api-uk-f2e.hungrypanda.co/openapi.json
    status: 200
  - url: https://uk-gateway.hungrypanda.co/v3/api-docs
    status: 404
  - url: https://www.hungrypanda.co/openapi.json
    status: 404
  - url: https://www.hungrypanda.co/merchants/
    status: 200
  checked: '2026-08-22'

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/hungrypanda"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hungrypanda/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hungrypanda/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.