Indian Institute of Technology Bombay
The Indian Institute of Technology Bombay (IIT Bombay), founded in 1958 and located in Powai, Mumbai, is one of India's premier engineering and research institutions, ranked #97 in the QS World University Rankings 2025. Its public developer footprint is largely student- and community-driven rather than a central institutional API program: the Students' Gymkhana operates an OAuth 2.0 "Profiles" identity API, the Institute Technical Council runs an ITC Single Sign-On service, and the Central Library exposes an OAI-PMH 2.0 interface over its DSpace institutional repository. No unified central developer portal was found; access to several APIs is gated to IIT Bombay infrastructure.
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 Indian Institute of Technology Bombay the way a machine reads it — 8 machine-readable artifacts across 3 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 — Indian Institute of Technology Bombay scores 32.4/100 (thin), with a separate agent-readiness read of 24/100 (agent aware). 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-07-27 · rubric v0.5
How we profile Indian Institute of Technology Bombay
Each block below is one kind of artifact we hold for Indian Institute of Technology Bombay. 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 3
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.
Gymkhana Profiles OAuth API
An OAuth 2.0 (RFC 6749) identity and profile API operated by the IIT Bombay Students' Gymkhana. It exposes authorization, token, and token-revocation endpoints plus a user resou...
ITC Single Sign-On API
A session-based Single Sign-On service maintained by the Institute Technical Council (ITC) for authenticating IIT Bombay users in student and club projects. A redirect-based sso...
DSpace Institutional Repository OAI-PMH
The IIT Bombay Central Library institutional repository is built on DSpace and exposes an OAI-PMH 2.0 metadata harvesting interface over its theses, journal articles, and confer...
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.
Iit Bombay Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Iit Bombay Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Iit Bombay Context
JSON-LDSecurity 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 Indian Institute of Technology Bombay — 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.
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/iit-bombay · machine-readable index on apis.io