SDK integration

Use Launa SDKs when you need programmatic control — CI pipelines, custom admin UIs, agent workflows, or in-process buyer logic. Control-plane SDKs talk to LAUNA_BASE_URL; buyer SDKs pay gateway hostnames with an EVM wallet.

Packages live in github.com/AxLabs/launa-sdks.

For Test mode without real funds (fork network, funded wallet, CLI --sandbox): Sandbox.

Control plane vs buyer

• Control plane — manage APIs, endpoints, domains, keys, stats (seller automation). Auth: API key or JWT.
  • Buyer — pay wrapped gateway URLs from your app, agent, or script. Auth: LAUNA_EVM_PRIVATE_KEY or browser wallet.

Buyer quick start

Example gateway URL: https://my-api.launa.io/v1/foo. Full guide: Buyer clients.

TypeScript

import { buyerClientFromEnv } from "@launa/sdk/buyer";

const client = await buyerClientFromEnv();
const { response } = await client.pay({ url: "https://my-api.launa.io/v1/foo" });

Control plane quick start

import { LaunaClient } from "@launa/sdk";

const client = new LaunaClient({
  baseUrl: process.env.LAUNA_BASE_URL!,
  apiKey: process.env.LAUNA_API_KEY!,
});
const apis = await client.apis.list();

Go: launa.NewClient. Python: LaunaClient.from_env().

Language guides

Automation tools

@launa/cli and @launa/mcp-server share the control-plane surface. Buyer: launa pay url and MCP launa_pay_url.

Discovery (gateway OpenAPI / well-known): API discovery — apis.discovery, CLI discovery urls, MCP launa_discovery_urls.

When to use SDK integration

• You embed seller or buyer logic in an existing application
  • You run infrastructure-as-code or CI that provisions APIs and endpoints
  • You build agents that both manage the platform and pay gateway URLs