smol.ai valid

SmolForge — llms.txt

SmolForge is a Git remote host for coding agents with built-in CI/CD Actions,

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T18:51:09.634Z. Cached copy · Source on smol.ai

# SmolForge — llms.txt

> SmolForge is a Git remote host for coding agents with built-in CI/CD Actions,
> full site hosting, Identity and AI services, repository agents, and agent
> transcript capture. Transcript and skill sharing and syncing are next.
> Base URL: https://forge.smol.ai
> Source: https://forge.smol.ai/swyx/forge
> Human docs: https://forge.smol.ai/docs
> CLI contract: https://forge.smol.ai/docs/reference/cli

This is Forge's canonical agent entry point. It documents the public API,
authentication boundaries, component-scoped release authority, CLI, and
transcript setup.
Treat examples as least-privilege starting points; the server remains
authoritative for scopes, limits, account capabilities, and Alpha availability.

---

## Start here: CLI, authentication, and agent context

Install the supported CLI and authenticate the current machine. Interactive
login asks for a username or email before it asks for a password and stores the
session through the platform credential store; it never prints the credential.

```bash
npm install -g @smolai/forge
sf auth login --username <username>
sf auth status
sf llms --save llms.txt
```

Use `sf auth login --email <email>` instead when email is the intended identity.
For non-interactive automation, set exactly one of `SMOLFORGE_USERNAME` or
`SMOLFORGE_EMAIL` plus `SMOLFORGE_PASSWORD`; structured output never prompts.
Do not pass passwords or tokens as ordinary command-line arguments.

The CLI can describe its exact installed contract offline:

```bash
sf help
sf commands --json
sf schema --json
```

The Forge API session and repository Git credentials are separate. After login,
install the Forge-only, URL-scoped helper for the repository you will access.
It creates or reuses a short-lived repository credential without changing
remotes or unrelated Git helpers. Verify both states without exposing either
credential:

```bash
sf auth login
sf auth git-credential <owner>/<repo>
sf auth status <owner>/<repo>
git ls-remote origin HEAD
```

Inside a checkout with exactly one unambiguous HTTPS Forge remote,
`sf auth git-credential` and `sf auth status` may infer the repository. Pass
`owner/repo` explicitly in scripts or whenever more than one Forge remote is
…

Related sites

Explore similar publishers →

Category suggestions: other listed sites in Developer tools. These share a category. See the whole category →

Machine-readable: GET /v1/resolve?q=smol.ai · GET /v1/domain/smol.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for smol.ai:
1. POST https://agentwebmap.com/v1/sites/smol.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://smol.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/smol.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/smol.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.