Workflow

A typical path from a local spec to a published, consumable interface.

1. Invent locally

Add or discover OpenAPI / JSON Schema files in your repo, then register them with the CLI:

ifc init --interactive
ifc add path/to/openapi.yaml   # or: ifc scan
ifc lint
ifc commit

2. Authenticate and push

ifc login
ifc push

This creates or updates hub interfaces you own and stores revisions (drafts).

3. Review and release

In the web hub, open the interface, review the revision, and publish a semver release when ready. Agents can create revisions over MCP; publishing a release asks a human to confirm.

4. Consume elsewhere

In another project:

ifc init
ifc use ifc7.dev/orgs/acme/payments
ifc fetch

Or fetch the canonical URL directly:

curl -L https://ifc7.dev/i/acme/payments

Mental model

local file  →  commit (manifest)  →  push (revision)
                                      ↓
                                 release (semver)
                                      ↓
                         use / fetch / /i/{owner}/{slug}

Owned interfaces: you edit files on disk, commit into the local manifest, then push to the hub.
Remote interfaces: use tracks them; fetch refreshes the local copy under .ifc/.

Next

• CLI quickstart
• Command reference