The words we use

Organization, project, app, site, runtime, deploy, environment variable, invite. What each one means on agenthost and how they nest.

You can use agenthost without knowing any of these — your agent handles them. They're here for when you want to follow what it's doing, or when something goes wrong and you'd like to know what part of it broke.

How it nests

Organization        your account — you, and anyone you invite
 └── Project        a folder for related things ("Client work", "My side projects")
      └── App       one thing that's online, at one address

Nothing else exists. There is no environment, no cluster, no region to pick, no pipeline.

The words

Word	What it means here
Organization	Your account. Everything you make belongs to one. You can belong to several — your own and a client's, say — and each one is entirely separate. Sometimes called a customer in tool output.
Project	A folder for related apps. Every app belongs to exactly one. Making one is free and unlimited; use them however suits you.
App	One thing that is online, at one address. A landing page is an app. An API is an app. The word covers both, because from your side they behave the same.
Site	An app that is only files — no code running. Cheaper, and free in useful quantity. See Plans & what counts.
Runtime	What your app is built with: `static`, `node`, `python` or `php`. Your agent picks it from your files. See Runtimes.
Deploy	Sending a new copy of your files and having them built and run. Each deploy replaces what was there.
Environment variable	A setting or secret your app reads at run time — an API key, say. Stored apart from your code. You set them yourself at `/secrets-manager`, not through your agent, which only ever sees their names. See Environment variables.
Custom domain	Your own address (`app.mydomain.com`) instead of the free one we hand out. See Use your own domain.
Invite (to an app)	Letting a specific email address open a private app. They get in with an emailed code — no account, no password. See Make something private.
Invite (to the account)	Letting a person work on your organization — deploy, delete, invite others. A much bigger deal. See Work with teammates.
Role	What a person is allowed to do in your organization: `owner`, `admin` or `member`.
API token	A long-lived credential for an agent that can't open a browser, like CI. See Deploy from CI.
MCP	The protocol your agent speaks to agenthost. You never see it.

Two kinds of invite, and they are not the same

Inviting someone to an app lets them open it and nothing more. Inviting someone to your organization hands them control of everything in it. Your agent uses different tools for each — share_app and invite_user — and it is worth being clear which one you're asking for.

App or service?

If you read your agent's tool calls you'll see both create_app and create_service. An app is the thing that gets built and hosted. A service is the plain record underneath it — useful for modelling something we don't host yet, but it doesn't run anything on its own. In normal use you only ever want apps. See Services.

What an app's status means

Status	What's happening
`created`	The record exists; nothing has been built yet.
`provisioning`	We're building it, or it's queued to build. This is normal for a minute or so after a deploy.
`running`	The container is up. Not proof that it works — see Checking a deploy.
`stopped`	It exists but isn't serving.
`error`	Provisioning or the build failed. Ask your agent to read the logs.

Talking to your agent

What to say, and what your agent can do for you.

How-to guides

One page per task.