Burger Singh
Burger Singh is an Indian quick-service restaurant chain founded in 2014 by Kabir Jeet Singh with co-founders Nitin Rana and Rahul Seth, and operated by Tipping Mr Pink Private Limited out of Gurugram, Haryana. It sells Indian-flavoured "craft" burgers - regional recipes built on Indian spices and chutneys - alongside fries and sides, desserts and beverages, through a hybrid estate of company-owned and franchised outlets that spans high-street, food-court, express and dine-in formats across India and into the United Kingdom. The business grows primarily through franchising, and its public web surface is organised around that motion: a menu, a store locator, franchise investment brackets, property-partner and bulk-order intake, and a complaint and feedback channel. Burger Singh is a restaurant operator rather than a software vendor and publishes no developer program, no API documentation and no commercial or partner-facing API. The only machine-readable interface it exposes is the WordPress REST content API behind its corporate site at burgersinghonline.com, captured here for discovery purposes.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Burger Singh the way a machine reads it — 17 machine-readable artifacts across 6 APIs, 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 — Burger Singh scores 29.7/100 (thin), with a separate agent-readiness read of 37/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
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 Burger Singh'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/burger-singh/"
title="Burger Singh on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/burger-singh.svg"
alt="Burger Singh Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/burger-singh/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/burger-singh/"
title="Burger Singh on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/burger-singh/card.svg"
alt="Burger Singh 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 Burger Singh
Each block below is one kind of artifact we hold for Burger Singh. 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.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Burger Singh Pages API
Public, unauthenticated read access to the site pages of burgersinghonline.com - Menu, Burgers, Fries and Sides, Desserts, Beverages, Franchise, Property Partners, Bulk Order, S...
Burger Singh Media API
Public, unauthenticated read access to the media library behind burgersinghonline.com - burger and menu photography, outlet imagery, franchise collateral and press assets with t...
Burger Singh Taxonomy API
Public, unauthenticated read access to the site taxonomy - the franchise investment brackets (Less than 26 Lacs, 26 to 60 Lacs, 60 Lacs to 1 Crore), the store formats (Dine-in O...
Burger Singh Search API
Public, unauthenticated cross-content search over burgersinghonline.com, returning lightweight id / title / url / type / subtype records with an embeddable link to the full object.
Burger Singh Discovery API
Public, unauthenticated site, content-type, taxonomy, status and author metadata - the self-describing route index (200 routes across 12 namespaces) that makes the whole burgers...
Burger Singh SEO Metadata API
Public Yoast SEO head endpoint returning the rendered SEO/head metadata and its schema.org JSON-LD graph for any burgersinghonline.com URL.
Open Collections 7
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONBurger Singh Discovery API
OPEN COLLECTIONBurger Singh Media API
OPEN COLLECTIONBurger Singh Pages API
OPEN COLLECTIONBurger Singh Search API
OPEN COLLECTIONBurger Singh Metadata SEO API
OPEN COLLECTIONBurger Singh Taxonomy API
OPEN COLLECTIONScroll within the panel for all 7 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
burger-singh-mcp.yml
MCP SERVERSecurity Posture 2
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Burger Singh — 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 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 5
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/burger-singh · machine-readable index on apis.io
This is an independent, third-party profile of Burger Singh, 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.