Choose The Right Integration Surface
Lamina supports three developer entry points:
The HTTP API is the canonical contract. The CLI and MCP server are thin wrappers around that same
/v1 surface.
Install From npm
For MCP, use the hosted v2 server at
https://app.uselamina.ai/mcp/agent/v2 (OAuth), or install it from https://app.uselamina.ai/mcp/install. Use https://app.uselamina.ai/mcp/agent only for the 30-tool advanced surface. The old self-hosted @uselamina/mcp npm package is retired.Authenticate Once
lamina login opens your browser for an OAuth approval flow — pick a workspace, click Approve, and the CLI receives the token on a loopback callback.
~/.lamina/config.json (mode 0600). OAuth tokens auto-refresh near expiry — you stay logged in for up to 30 days without re-prompting.
Inspect the active identity at any time:
LAMINA_API_KEYenvironment variable- saved CLI credentials at
~/.lamina/config.json(OAuth tokens or API key)
Inspect Apps
List available apps:Upload A Local File
Pass a path; the CLI streams the bytes to Lamina’s CDN via a pre-signed URL and prints the resulting URL you can pass tolamina run --input ...:
Run An App
You can run with a JSON file:- unknown parameter names
- missing required inputs
- invalid option labels
- invalid
urlvalues
Where The SDK Fits
The shared Lamina client is published as@uselamina/sdk and powers the CLI.
If you are integrating from your own backend, use @uselamina/sdk or call the /v1 HTTP API directly.
The client wraps:
GET /v1/appsGET /v1/apps/{appId}GET /v1/apps/{appId}/workflowPOST /v1/apps/{appId}/runsGET /v1/runs/{runId}GET /v1/webhooks/signing-key
Next Steps
- Read Test Webhooks Locally to receive signed Lamina callbacks on your machine
- Read Agent Integration Patterns to run Lamina through MCP in coding agents
- Read Quick Start if you want to stay on the raw HTTP API