Platform overview
IFC7 is a hub for OpenAPI and JSON Schema interfaces. You invent and evolve specs in git, publish them to the hub, and consume them from other projects — by humans in the browser, by the CLI, or by agents over MCP.
Core concepts
| Concept | Meaning |
|---|---|
| Organization | Shared ownership for a team’s interfaces |
| Interface | A named OpenAPI or JSON Schema definition with a stable URI |
| Revision | A draft snapshot of the specification |
| Release | A semver-tagged, publishable revision (v1.2.3) |
| Canonical URL | Public locator for the latest or pinned release |
Who owns what
- User-owned interfaces live under
@username - Org-owned interfaces live under an org slug (preferred for teams)
Visibility can be public or private. Private interfaces require authentication to fetch or view.
Canonical URLs
Stable locators sit outside the versioned REST API:
text
https://ifc7.dev/i/{owner}/{interface}
https://ifc7.dev/i/{owner}/{interface}/vX.Y.ZExamples:
https://ifc7.dev/i/acme/paymentshttps://ifc7.dev/i/acme/payments/v1.2.3https://ifc7.dev/i/@joesmith/my-api
| Client | Response |
|---|---|
Tools (curl, codegen) | Raw schema (JSON or YAML) |
Browser (Accept: text/html) | Interactive documentation |
Unversioned URLs resolve to the latest release if one exists, otherwise the latest revision. Pinned URLs require that release.
Surfaces
| Surface | Role |
|---|---|
| ifc7.dev | Browse, document, revise, and release in the UI |
ifc CLI | Local project workflow against the hub |
| MCP server | Agent access to the same lifecycle operations |