# Judt

> Judt hosts Apps and sites for your agent. An App is a full-stack web app that runs on the workerd runtime, with a database, storage, schedules, queues, workflows, and Durable Objects built in. Agents create, edit, preview, and publish Apps through the Judt HTTP API, MCP server, or CLI.

Each App has a private sandbox, where an agent edits and runs its source, and a production deployment on its own address at judt.dev. A person owns each App through their organization.

## What you can do

With access to Judt, you can:

- Create Apps and sites, and edit their files in a private sandbox.
- Run commands in the sandbox, and preview the App.
- Publish an App to its own address at judt.dev.
- See an App's deployments and logs.
- Manage an App's Secrets.

You can do all of this through the HTTP API, the MCP server, or the CLI, with the same access.

## Ways to get access

You can get access without an API key. Your person approves it on Judt's site.

| What the agent has | Way to get access | What the agent gets | What the person does |
|---|---|---|---|
| MCP client with OAuth | Add `https://api.staging.judt.ai/mcp` as a server, with no `Authorization` header. The client does the sign-in. | Scoped token, kept by the client | Signs in and approves |
| A shell | The Judt CLI: `judt auth login --device`. | Scoped token, saved and refreshed by the CLI | Opens a link and approves |
| HTTP requests only | [Registration with an email address](https://staging.judt.ai/auth.md#registration-with-an-email-address). | Scoped token, stored and renewed by the agent | Opens a link, types a code, and approves |
| Only a browser | The form at https://staging.judt.ai/signup, or the WebMCP tool `sign_up`. | The full session of the person, in that browser only | Follows the emailed link, or gives the agent the emailed code |

The order of the rows is Judt's order of preference. The first row that an agent's tools allow leaves that agent the least to do.

The first three rows give a token for one organization, with the scopes that the person allows. The person can disconnect it at https://staging.judt.ai/connections. The person does not need an account first: the sign-in page of these rows also makes one.

This command installs the CLI, whose source is at https://github.com/judt-ai/cli:

```sh
curl -fsSL https://staging.judt.ai/install | sh
```

`judt auth login --device` prints a link and a code to stderr at once, then waits until the person approves, so it can run in the background.

A person can also make an API key at https://staging.judt.ai/api-keys for scripts and CI. Personal Agents that use the Personal Agent Protocol start at https://staging.judt.ai/.well-known/poppy.json.

[auth.md](https://staging.judt.ai/auth.md) describes these ways, the registration, and how tokens work.

### WebMCP

In a browser with WebMCP, the site registers tools on `document.modelContext`. On https://staging.judt.ai and its log-in and sign-up pages: `sign_up`, `log_in`, `verify_code` (signs in this browser with the code from the email) and `send_message` (contacts the Judt team). In the console (https://staging.judt.ai/apps), signed in: the MCP server's tools, except `create_app_token`, run as the signed-in person.

## Pages

The pages of the site. Each page also has a Markdown copy, at its Markdown link or at the URL of the page with `Accept: text/markdown`.

- [Home](https://staging.judt.ai/) ([Markdown](https://staging.judt.ai/index.md)): What Judt is and who it is for: one session of an agent building an App, example Apps, the services every App has by name, and the ways teams fit Judt into their product.
- [How it works](https://staging.judt.ai/product) ([Markdown](https://staging.judt.ai/product.md)): How an agent builds, publishes and runs an App on Judt: sessions call by call, the layers every App comes with, the API it uses, how to connect (API, MCP, CLI), the templates it starts from, and agents that build other agents.
- [Pricing](https://staging.judt.ai/pricing) ([Markdown](https://staging.judt.ai/pricing.md)): Early access plans. Building and going live are free during the beta.
- [Contact](https://staging.judt.ai/contact) ([Markdown](https://staging.judt.ai/contact.md)): What to expect in the beta, and how to send the Judt team feedback, bug reports, and questions.
- [Privacy Policy](https://staging.judt.ai/privacy) ([Markdown](https://staging.judt.ai/privacy.md)): What Judt collects, how it’s used and shared, how long it’s kept, and your rights over it.
- [Terms of Service](https://staging.judt.ai/terms) ([Markdown](https://staging.judt.ai/terms.md)): The agreement for using Judt: your Apps and content, acceptable use, the beta, liability, and how disputes and changes work.

## Docs

- [Judt documentation](https://docs.judt.ai/llms.txt): The index of the docs for agents: managing Apps, building Apps, and the API reference.

## API and MCP

- [OpenAPI description](https://api.staging.judt.ai/api/openapi.json): Every endpoint of the HTTP API at https://api.staging.judt.ai/api.
- [MCP server](https://api.staging.judt.ai/mcp): Streamable HTTP. Its tools mirror the HTTP API.
- [MCP Server Card](https://api.staging.judt.ai/mcp/server-card): The MCP server's name, tools, and authorization.
- [Judt CLI](https://github.com/judt-ai/cli): Each command is one call to the HTTP API.

## Additional resources

- [API catalog](https://api.staging.judt.ai/.well-known/api-catalog): The API and the MCP server, as an RFC 9727 linkset.
- [Agentic Resource Discovery](https://staging.judt.ai/.well-known/ard.json): Judt's ARD manifest.
- [Authorization server metadata](https://staging.judt.ai/.well-known/oauth-authorization-server): The OAuth endpoints, as RFC 8414 metadata.