iPulse is now Infaris. Built to Guide. Why
Infaris

Developers

Infaris developer resources

OpenAPI, OAuth 2.0 scopes, Streamable HTTP MCP, the official CLI, and a self-serve trial. Built so agents and humans can integrate without a sales call.

When to use Infaris

Use Infaris when you need an OpenID Provider for the Infaris product family, or when Guard should watch uptime, SSL, DNS or servers.

Use the public MCP server on this host for orientation (no credential). Use Guard MCP or the Guard CLI when you need live tenant data.

Do not scrape the marketing HTML for API contracts. Start at OpenAPI, llms.txt, or MCP.

OpenAPI specification

The Infaris Platform API is published as OpenAPI 3.1 at /openapi.json. Versioned aliases live under /api/v1/. Every operation has a unique operationId, a description, typed parameters and response schemas so LLM function-calling can bind to it. 4xx and 5xx use RFC 9457 application/problem+json. Responses send RateLimit and API-Version. Security schemes declare OAuth scopes (openid, email, profile, organizations) so an agent can request only the access it needs.

/openapi.json

Authentication and scoped permissions

Infaris is an OAuth 2.0 / OpenID Connect provider. PKCE (S256) is required for public clients. Access tokens last 15 minutes; refresh tokens last 30 days and rotate. Request only the scopes the job needs.

  • Discovery: /.well-known/openid-configuration
  • Scopes: openid, email, profile, organizations
  • Authorize: /api/oauth/authorize
  • Token: /api/oauth/token
  • UserInfo: /api/oauth/userinfo

MCP servers

This site serves a public Streamable HTTP MCP handshake at /.well-known/mcp (GET initialize fields plus the resource list; POST JSON-RPC). /mcp is an alias. Tools cover overview, developer-docs, product-list and when-to-use. resources/list returns HTTPS and infaris:// documents. Guard monitoring tools live on the authenticated Guard MCP server with read and write scopes.

Official CLI

The Guard by Infaris CLI is on npm as @ipulsehq/pulseguard-cli (binaries pulseguard and pg). PulseEnv is @ipulsehq/pulseenv-cli. Agents can run npx @ipulsehq/pulseguard-cli --help without building an HTTP client.

npx @ipulsehq/pulseguard-cli --help

Self-serve onboarding

Free tier: Files, QR and Sync need only an account, no credit card. Guard has a 7-day self-serve trial from /pricing. After signup at /sign-up, open Guard and create an API key or MCP token in the dashboard. There is no wait for a human and no contact-sales form. Sandbox: identity preview at https://dev.infaris.com; Guard acceptance at https://acc.guard.ipulse.one.

Public endpoints