Pick the interface that matches the semantics and trust boundary your project actually needs.
Public API & SDKs
Use the unauthenticated public platform for canonical building and place intelligence, deterministic routing, and route-aware gap planning across supported universities. It never exposes a student’s timetable, account, friends, private sync state, or precise live location.
Gapwise Data
Use canonical campus data artifacts when you need GeoJSON, building/entrance records, routing graph inputs, provenance, audits, checksums, or your own derivation pipeline across supported universities and campuses. Raw files are distributed from a first-party Gapwise domain.
Gapwise AI & MCP
Connect a compatible remote MCP client to stateless public campus intelligence or explicitly delegated private Gapwise context and bounded actions. Private access is OAuth-protected, permissioned, minimized, revision-aware, and revocable.
Deterministic by design
Routing and gap calculations use explicit campus data and deterministic rules, not generated guesses.
Privacy-first
Public campus APIs and raw public data require no timetable or account. Private AI access is a separate, explicit delegation boundary rather than an extension of the public API.
Uncertainty is explicit
Missing or unverified campus facts stay unknown instead of silently becoming confident answers.
One source-of-truth hierarchy
Data owns campus facts, core owns deterministic behavior and API contracts, Docs explains released semantics, AI delegates private context, and Status observes the public surfaces.
| Surface | Canonical URL | Use it for |
|---|---|---|
| Developer hub | https://gapwise.ca/developers |
Choosing the right integration |
| Documentation | https://docs.gapwise.ca |
Human-readable contracts, guides, architecture, and security |
| Public API | https://api.gapwise.ca/v1 |
Stable deterministic campus intelligence |
| OpenAPI | https://api.gapwise.ca/openapi.json |
Machine-readable API contract |
| CLI | https://docs.gapwise.ca/cli/ |
Campus discovery and university integration tooling |
| Gapwise Data | https://data.gapwise.ca |
Canonical raw campus data, schemas, provenance, and downloads |
| Raw dataset manifest | https://data.gapwise.ca/datasets/utm/latest/manifest.json |
Integrity-checkable raw artifact discovery |
| AI / MCP | https://ai.gapwise.ca/api/mcp |
Permissioned assistant integration |
| Status | https://status.gapwise.ca |
Service health and incidents |
The canonical public API exposes versioned buildings and places across 13 supported Canadian universities (and 15 campus models), deterministic building-to-building routing, and route-aware assessment of an explicitly supplied free interval.
https://api.gapwise.ca/v1https://api.gapwise.ca/openapi.jsonhttps://gapwise.ca/developershttps://github.com/GapwiseHQ/gapwisenpm install @gapwise/sdk@0.1.2jsr:@gapwise/sdk@0.1.2@gapwisehq/sdk (historical 0.1.1 under @gapwise-for-uoft/sdk)python -m pip install gapwise==0.1.1Successful responses use { data, meta }; errors use a nested structured error envelope with a request ID. Both official SDK implementations target the same v1 contract. @gapwise/sdk@0.1.2 is published on npm and JSR, the same JavaScript SDK is mirrored publicly on GitHub Packages as @gapwisehq/sdk (historical 0.1.1 under @gapwise-for-uoft/sdk), and gapwise==0.1.1 is published on PyPI through Trusted Publishing and has been independently clean-installed against the production API. The GitHub Packages mirror uses the organization-scoped package name required by GitHub and does not replace the canonical @gapwise/sdk identity.
Gapwise Data is the canonical repository for public campus facts and geometry across 13 supported universities (15 campus models). It owns university- and campus-scoped building identity, footprints, and metadata. Its production distribution includes reviewed entrances, routing graph inputs, provenance, evidence state, uncertainty, and generated data audits, with specialized raw artifacts for campuses such as UTM.
Raw artifacts are published under:
https://data.gapwise.ca/datasets/utm/latest/Gapwise web/API builds do not live-fetch the Data website. They pin a validated snapshot so a Data-site or GitHub outage cannot break routing for students. See Gapwise Data and Distribution and versioning.
Gapwise AI is a separate provider-neutral remote MCP service. The client supplies the model and reasoning layer; Gapwise supplies deterministic public-campus tools plus explicitly delegated private tools and bounded mutation semantics.
https://ai.gapwise.ca/api/mcphttps://ai.gapwise.ca/.well-known/oauth-protected-resourcehttps://ai.gapwise.cahttps://github.com/GapwiseHQ/aiThe live release surface exposes 30 tools total:
Public campus tools do not authenticate or expose a student’s private timetable, friends, precise location, or sync state. Private tools require the production Gapwise OAuth/delegation boundary. Academic meetings remain read-only and cannot be created, edited, or deleted by an AI client.
Broad named-client compatibility is still a release gate. These docs do not claim ChatGPT, Claude, or another named client as fully verified until the production OAuth/read/write/revoke matrices are complete. See Client compatibility.
Gapwise is an independent student-built project and is not affiliated with, endorsed by, or an official service of any supported university unless explicitly stated otherwise.