Here's How It Works
No hoops, no gatekeeping. Just a quick look at how to get started, what to expect, and a few ground rules to keep things smooth.
Getting Access
Here's what we need from you and what we check on our end. No surprises — just a straightforward process.
What to Include in Your Application
- Who you are — company details or individual developer profile
- What you're building — a brief description of your use case
- How it works — integration architecture overview
- Redirect URI(s) for authentication flows
- Static IP ranges or gateway IP(s)
- Security contact for your team
- Data handling and privacy declaration
- Environment and infrastructure setup details
- Acknowledgement of Swiggy MCP terms
- Security audit summary(Optional)
- SOC2 / ISO certification (if available)(Optional)
- Expected traffic and scaling plan(Optional)
What We Check on Our End
Security Check
We review your security setup and infrastructure to keep users safe.
Compliance Review
Quick check on data handling and privacy practices — nothing scary.
Use Case Fit
We make sure your idea is a good fit for the platform and our users.
Gradual Rollout
We validate together, ramp up access gradually, and go live when everything is solid.
Ongoing Partnership
We stay in touch — usage monitoring, support, and a direct line to the team.
The Ground Rules
Build freely within these boundaries. We keep it simple — here's what's encouraged, what's not, and what's a hard no.
What We Allow
Encouraged
Building apps, agents, or tools that make ordering, discovery, or dining better for users
AI-powered assistants and copilots that use MCP to automate commerce workflows
Creative side projects, hackathon builds, and experimental prototypes
Integrations that follow Swiggy’s security and branding guidelines
Sharing demos and walkthroughs with us — we love seeing what you build
Commercial partnerships where both sides win
Not Allowed
Restricted
Reselling or sharing your MCP access with unapproved third parties
Building aggregation layers that hide Swiggy's brand or confuse users
Misrepresenting prices, availability, or delivery times
Scraping or extracting data beyond what the APIs provide
Using the APIs for competitive intelligence or benchmarking
Bypassing rate limits, logging, or any platform safeguards
Prohibited Conduct
Zero Tolerance
Manipulating order flows, incentives, or ranking systems
Dark patterns, deceptive UX, or misattributing where data comes from
Generating fake traffic or abusing rate limits
Harvesting data beyond your agreed scope
Reverse engineering MCP internals
Circumventing whitelisting or access controls
Violating user privacy or security regulations
A Few Things to Know
The important stuff. Fair rules that keep the platform healthy for everyone.
Stay in Scope
Use the APIs for what they're built for. Want to expand into new capabilities? Let's talk.
Respect the Brand
Follow Swiggy's attribution guidelines. Users should know when they're interacting with Swiggy services.
User Data is Sacred
Transaction data from MCP stays governed by Swiggy's platform terms. Handle it responsibly.
We Keep Watch
We monitor API usage for quality and safety. Play fair and you'll never have an issue.
Legal Framework
Custom terms can be negotiated for enterprise partners. Typical turnaround: 4+ weeks.
Ready to Apply?
Pick the track that fits you. Both get full API access — the forms are just tailored to what we need from each.
Individual Developers & Teams
Solo devs, indie hackers, small teams, and startups building AI agents, side projects, or experiments on Swiggy's MCP.
Enterprise Partners
Companies integrating Swiggy's commerce APIs into their product — with dedicated support, custom onboarding, and enterprise SLAs.
Not sure which one? Email us and we'll help you figure it out.