# agents.md

Machine-readable quickstart for agents working with Sequenzy.

## Discovery

- Agent auth guide: https://www.sequenzy.com/auth.md
- API catalog: https://www.sequenzy.com/.well-known/api-catalog
- OpenAPI spec: https://api.sequenzy.com/openapi.yaml
- MCP server card: https://www.sequenzy.com/.well-known/mcp/server-card.json
- Agent skills: https://www.sequenzy.com/.well-known/agent-skills/index.json
- LLM facts: https://www.sequenzy.com/llms.txt

## API And MCP Access

Use https://www.sequenzy.com/auth.md for user-approved API/MCP access. It describes the `service_auth` claim flow, where the agent registers with the user's email, asks the user to approve the code in a Sequenzy-owned browser page, polls for a bearer credential, then calls the API or MCP server with `Authorization: Bearer <access_token>`.

Do not treat `auth.md` as dashboard account signup. It is for agent API/MCP credentials.

## Dashboard Signup

Normal dashboard account signup is a user-facing app flow at https://www.sequenzy.com/sign-up. It uses Sequenzy's Better Auth routes under `/api/auth/*` and creates a dashboard account.

## First Company After Dashboard Signup

When operating inside an authenticated dashboard session with tRPC access, create the first company with the direct procedure input body:

```json
{ "noWebsite": true, "name": "Prelaunch App" }
```

Do not wrap mutation input in a `json` property:

```json
{ "json": { "noWebsite": true, "name": "Prelaunch App" } }
```

After `companies.create` succeeds:

1. Call `companies.syncSession` so the current dashboard session sees the new company.
2. Verify with `companies.list`.
3. Inspect the created company with `companies.getById`.

Prefer public API or MCP workflows for durable integrations. Dashboard tRPC is for authenticated dashboard-session automation only.