Docs

Run an AI agent in a Workspace.

Start with the first guide: it takes you from one free click to a real task, terminal access, and billing only when you need it. For connecting your own MCP client, see the MCP guide; for plans and credits, see pricing.

Quickstart: start here

Try it free, give the agent a real first task, connect your terminal, and add credits only when you outgrow the free allowance.

plori CLI

Install the CLI, complete browser login, run an agent, attach to a live session from the terminal, use JSON output in scripts, and keep API-key auth for CI.

Workspaces

Send a task to a Workspace, run several agents at once and merge their changes, read saved versions of the files, and see what is kept between runs.

Disk and files

How a Workspace's files and the account disk work: the disk pool, the files panel, what persists between runs, and buying more space.

Publish a site

Publish static files or run a scale-to-zero service at your-name.plori.site. Ready-card and Files paths, private-by-default visibility, updates, and runtime credits.

Agent memory

plori agents keep notes about you and your projects. How memory works, private vs account scope, and how to manage it.

Scheduled runs

Ask an agent to do something later. How schedule_run works from chat and MCP, and how the result comes back to you.

Background tasks

How a long command becomes a background job, how long it runs, and where its output goes.

Workflows

Automations your plori agent builds in chat: schedule, webhook, and manual triggers, safe test runs, credentials, per-run pricing, and plan limits.

Functions

Call an agent from your app's backend: write a typed, versioned function.yaml, deploy it with a test gate, call it over HTTP, and read its typed items and files.

What a credit buys

What a plori credit actually buys: measured run costs from production, what never draws credits, how to see each run's cost, and why billing is credits instead of hours.

Bring your own model key

Connect your own model provider key (OpenRouter one-click, or a pasted key) so model usage bills to your provider account instead of credits.

REST API reference

The documented api.plori.ai/v1 surface: Workspaces and their files, agents and runs, schedules, credits, and the public rate cards. OpenAPI 3.1 spec included.

Every page here is also available as plain Markdown: request it with an Accept: text/markdown header. Agents can start from llms.txt.