mocop
Browse · Docs · Guide · Analyze

Infrastructure Auth API

API by Infrastructure · rest

Authentication as a service: passwordless sign-in by an 8-character email code (with an RFC 8628-style polling variant for headless agents), Google sign-in, sessions as RS256 JWTs verifiable via JWKS, an OAuth 2.1 authorization server for MCP clients (scopes auth:read, auth:write), and a management API for organizations, applications, end users, configuration and API keys. Credentials. Apps send X-API-Key (pu_ in the browser, ak_ on the server) plus Authorization: Bearer <session token>. An agent with no account can bootstrap itself: POST /auth/code/start (no key) → a human reads the code → POST /auth/code/verify → POST /organizations → POST /application/{organizationId} → POST /api-keys. Contract. Errors are { "error": { "code", "message", "details"? } } with a stable code; collections are { items, page: { limit, offset, total, hasMore } }. OAuth endpoints (/oauth/*, /.well-known/*) follow their RFCs instead. The MCP server…

Endpoint: https://auth.worker.myinfrastructure.click/

Verification: observed. Source: crawl.

Capabilities (62)

  • Health check
  • JSON Web Key Set
  • OAuth authorization server metadata
  • Protected resource metadata (MCP)
  • Protected resource metadata for an application MCP
  • List API keys of an application
  • Create an API key
  • Delete an API key
  • Get the application of an API key
  • List the impersonation audit trail
  • End every open impersonation of an application
  • List an application's customer organizations
  • Create or update a customer organization
  • Delete a customer organization
  • Get a customer organization
  • List members of a customer organization
  • Add a member or change their role
  • Remove a member
  • List users of an application
  • Create or update an application user
  • Delete an application user
  • Impersonate an application user
  • Get an application
  • Create or update an application
  • Delete an application
About · Contact · Privacy