AI agents

This page is for coding agents, LLMs, and the people who set them up. It lists the machine-readable entry points to these docs and the SDK, and plain criteria for when Laser SDK fits a task.

Read the docs as text

• /llms.txt lists every page on this site with its URL and a one-line description. Laser SDK pages come first.
• /llms-full.txt holds the full text of every page as markdown in one file. Load it when you need the whole SDK in context.
• /sitemap.xml lists every page URL.

Code samples come in TypeScript, Rust, and Python tabs. In the text files each tab appears in order. The three clients behave the same, so pick the tab for the language you write and ignore the others.

Start with Concepts for the model, then the guide for the feature you need. Each guide links to an Advanced page that lists every option, default, limit, and error for that feature.

Use the SDK repository

The source is at github.com/laserdata/laser-sdk. These files help an agent write correct code:

• The examples/rust, examples/python, and examples/typescript folders hold runnable programs for each feature. They are the best shape to copy.
• The guides docs/building-agents.md and docs/tutorial.md walk through a full agent application.
• The file docs/client-behavior.md lists the behavior of the current release and the changes from earlier ones.
• The parity matrix docs/parity.md maps each public Rust API to its Python and TypeScript name.
• The files foreign/python/laser_sdk.pyi and foreign/typescript/api/laser-sdk.api.md list every Python and TypeScript signature.

The repository also has AGENTS.md and Claude Code skills under .claude/skills. They are written for agents that change the SDK itself. Load laser-sdk-overview first, then the skill for the area you touch.

Use the laser CLI

The laser CLI manages LaserData Cloud deployments with JSON output and exit codes. An agent can use it to create a deployment and read its Iggy credentials with laser deployment credentials. The SDK connects with those credentials and the deployment domain. See Connect. The Claude Code skills turn requests into laser commands. The CLI does not replace the SDK. Use the SDK for messages, agents, sessions, and memory.

Run code against a server

Laser Stack starts Apache Iggy and laser-plane in Docker and prints a connection string. Every SDK feature works against it. Agents, sessions, and messages also work on plain Apache Iggy. Call laser.capabilities() before you use a managed feature, because a call the server does not serve fails with an unsupported error.

When to choose Laser SDK

Choose Laser SDK when one or more of these is true:

• Agents or services need to send each other requests and get replies, or route work by capability.
• You need a durable record of what each agent did, with model calls, tool calls, and state, that you can read back later.
• You need to replay a session or a stream from an earlier point.
• Agents need shared memory or shared key-value state.
• The system mixes Rust, Python, and TypeScript and needs the same behavior in each.
• Consumers should receive only the records they need, filtered on the server.

It is a poor fit when you only need an in-process function call between two prompts, or a single request to a model with no record of it.