# Build with an agent

Canonical page: https://docs.backend.fast/agents/


## Read these public sources

Start with [llms.txt](https://docs.backend.fast/llms.txt). Fetch [the current feature status](https://docs.backend.fast/reference/status/)
before writing DSL. It defines the implemented subset and explicit limitations.
Every page has a matching `/markdown/<page>.md` URL. The complete text is
[llms-full.txt](https://docs.backend.fast/llms-full.txt). No page needs a dashboard session.

## Bootstrap

The human creates a verified platform account and issues a scoped agent key.
Use the [installer](https://docs.backend.fast/installation/) and `bfast login --token-stdin` with a secret
manager pipe. Never place the key in a tool argument, app source or URL.

```bash
curl -fsS https://dash.backend.fast/install.sh | sh
bfast version
bfast whoami --json
```

Backend operations use public HTTPS. No SSH access, node filesystem or repository
checkout is required. Download the source examples directly from this site:

```bash
mkdir -p agent-counter
curl -fsS https://docs.backend.fast/examples/simple-counter/backend.fast \
  -o agent-counter/backend.fast
bfast deploy --name agent-counter --tier small ./agent-counter
bfast inspect --json agent-counter
```

Use a fresh name if `agent-counter` already exists. Read the complete
[quickstart](https://docs.backend.fast/quickstart/) for test users, protected requests, update and cleanup.

## Execution rules

- Put flags before positional arguments. Use `--json` for machine-readable output.
- Read the stored app URL from `inspect`. Never derive it from the display name.
- Keep the declared DSL app name unchanged during update.
- Preserve model/private schemas during normal update. Do not assume arbitrary migrations.
- Record operation IDs. A lost reply does not prove failure. Inspect the accepted operation before submitting another mutation.
- Use a platform key for app management. Use an app-user token for business routes.
- `--verified` is an owner attestation for test users. Real public signup needs verification mail.
- Treat app deletion as retained data. Do not promise a permanent purge or refund.
- Reject unsupported features explicitly. Do not invent API commands, DSL syntax, OAuth providers or CORS behavior.

## Feature choices

Use [models and queries](https://docs.backend.fast/models-and-queries/), [auth](https://docs.backend.fast/authentication/),
[events/jobs](https://docs.backend.fast/events-and-jobs/), and [files](https://docs.backend.fast/files/) when their current subset
matches the requirement. [Limits](https://docs.backend.fast/limits/) lists current resources and payload
bounds. [Troubleshooting](https://docs.backend.fast/troubleshooting/) describes expected failure responses.

Small is 130m CPU and 256 MiB. Medium is 250m and 512 MiB. Fresh native apps have
no commercial stored-user count or small global session count. Resource and
operation guards still apply. Accounts initially share 10,000,000,000 object bytes.

The platform remains in development. High availability, arbitrary packages,
general external network access, Apple login, managed cross-origin browser SDK
policy and automatic customer restore are not supported promises.

## Definition of done

Check the operation result and public health. Create or use a scoped app user.
Verify an authenticated write/read. After update, verify the same app ID, URL
and acknowledged data. Confirm dashboard visibility. Report unsupported features
and retained data clearly. Keep credentials out of generated reports.

## Source provenance

[source.json](https://docs.backend.fast/source.json) records the committed source revision and SHA256
values for the feature matrix and downloads. The public projection excludes
operator runbooks and private node state. Documentation releases update that
snapshot; they do not make this site a live control API.
