Pinata Agents gives you a hosted AI agent in its own sandboxed container. The agent has a workspace it can read and write to, a terminal it can run commands in, and connectors for the outside world — chat apps, web servers, scheduled jobs. You talk to it through the dashboard, the CLI, or whichever messaging platform you connect it to. Each agent runs on an Agent Engine —Documentation Index
Fetch the complete documentation index at: https://docs.pinata.cloud/llms.txt
Use this file to discover all available pages before exploring further.
openclaw (default) for full configurability, or hermes for an opinionated, smoother out-of-the-box experience. You pick one when you create the agent. The default OpenClaw engine is documented at openclaw.org; for the differences see Concepts → Engine.
Agents require a paid Pinata plan. Upgrade here.
Get your first agent running
It takes a couple of minutes. You’ll connect an LLM provider, create the agent, and start chatting.1. Connect an LLM provider
Your agent needs an LLM to think. Go to the Secrets Vault. At the top of that page you’ll see a row of provider cards: Anthropic, OpenAI, OpenRouter, Pinata, Venice, and Custom. Click Connect on whichever one you use, paste your API key (or run through OAuth if you’re using an OpenAI Codex subscription), and save. You can connect more than one provider — useful so you have a fallback if one is down.2. Create an agent
Head to My Agents and click Create Agent. You have two paths:- Start from a template — fastest. Templates come pre-wired with skills, settings, and a personality. Pick one from the Marketplace (others’ templates) or My Templates (your own). Add the secrets it needs, deploy.
- Build from scratch — full control. The wizard walks you through naming the agent, choosing an Agent Engine (OpenClaw or Hermes), picking a personality preset (Atlas, Nova, Sage, or custom), choosing skills, and connecting your LLM provider.
3. Start a conversation
Say hello. Ask it to write some code, summarize a webpage, or set up a workflow. It can use a terminal, edit files, search the web, and call any skills you’ve attached.
Finding your way around
The sidebar on the left is the same on every page. Top half is the workspace itself; bottom half is account and support.| Section | What’s in it |
|---|---|
| My Agents | Every agent you’ve created. Click one to expand its tabs (Chat, Channels, Files, Skills, etc.). |
| My Issues | A kanban board for assigning work to agents. Closed beta — @pinata.cloud accounts today. |
| Skills Library | Skills you’ve installed, plus a community catalog under Browse ClawHub. |
| Secrets Vault | All your encrypted credentials, in one place, shared across agents. |
| My Templates | Templates you’ve created or imported. |
| Marketplace | Published templates from Pinata and other builders, ready to deploy in one click. |
| Account | Workspaces (switch teams), Integrations (e.g. GitHub OAuth), Activity (audit log). |
| Support | Docs, the OpenAPI reference, changelog, and a way to chat with the Pinata team. |
The agent dashboard
Click any agent and you’ll see tabs across the top of the page. Each tab is a slice of how the agent works:- Chat — your conversation with the agent
- Channels — wire it up to Telegram, Slack, or Discord
- Files — workspace snapshot history, content diffs, git URL
- Skills — capabilities attached to this specific agent (pulled from your Skills Library)
- Secrets — provider connections and env vars this agent can see
- Models — which models from your providers it’s allowed to use, and which is the default
- Routes — path routes and custom domains for any web service it runs
- Tasks — cron jobs and one-off scheduled prompts
- Console — a terminal inside the container
- Logs — real-time log stream
- Danger — full configuration overview, plus restart and delete
Editing the workspace locally
Your agent’s workspace is a git repo you can clone and push to.Working from the terminal
Everything in the dashboard is in the CLI too:Going deeper
Concepts
Glossary, file layout, and how the pieces relate
Manifest reference
Every field in
manifest.json, the source of truth for an agent’s configHTTP API
Auth model and endpoint reference for building against the platform
Troubleshooting
What to do when something doesn’t work
Templates
Deploy a pre-built agent in one click
Channels
Let people talk to your agent on Telegram, Slack, or Discord
Skills
Add capabilities — IPFS storage, memory, on-chain identity, more
Routes
Expose a web app or API from inside the agent