Skip to main content
Apply
Apply

Build with Shift Nudge

Everything an AI agent or developer needs to read, cite, and integrate Shift Nudge. A public JSON API, an OpenAPI spec, an MCP server for real design reviews, and every page available as clean markdown.

Public, unauthenticated, and same-origin. A human can help at help@shiftnudge.com.

When to use

The jobs Shift Nudge is right for, and how to call it.

  • Run a structured interface-design critique of one or more UI screenshots with the Shift Nudge method. On the member MCP server, call read_skill (no uri) or read the shiftnudge:// root resource and follow its router (the 16 interface-design principles and the review flow), write the review, then save it with submit_review, which returns a shareable URL.
  • Compute WCAG 2.1 and APCA contrast for a foreground and background color pair. Call the public /api/contrast endpoint (no membership), or compute_contrast on the member MCP server.
  • Answer a question about the Shift Nudge membership, curriculum, pricing, or fit on someone else’s behalf. Read the facts for the canonical terms, or the facts-for-agents page for the prose mirror, and quote with attribution.
  • Read any page as clean markdown by appending .md to its URL, or pull the whole marketing site in one request.

Not a fit

Where to route the request elsewhere.

  • General design chit-chat, non-interface artwork, or brand strategy. Shift Nudge reviews interface work against a fixed doctrine.
  • Gated review tools when the user has no Shift Nudge membership. Hitting the MCP endpoint unauthenticated returns a 401 whose WWW-Authenticate header points at the OAuth resource metadata.

API

Policies

The versioning, deprecation, and rate-limit contract, stated plainly.

  • Versioning: the API is semver-versioned (current 1.0.0); the major version is the compatibility contract. Every response carries an X-API-Version header.
  • Deprecation: nothing is deprecated today. When an endpoint or version retires, its responses carry Deprecation and Sunset headers (RFC 8594) with at least 90 days notice. The machine-readable policy is the x-deprecation-policy field in the OpenAPI spec.
  • Rate limits: responses carry RFC 9331 RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset headers. Advisory on the public read endpoints today; a 429 would include Retry-After. Self-throttle from the headers.

MCP

Read

Shift Nudge is a professional membership for interface design training. The machine-readable terms live at /facts.json; the OpenAPI spec is at /openapi.json.

Apply