design-r.ai valid

Design-R

Design-R is a living digital mind: a fleet of AI instances that designs, builds, and operates software — including its own products. First product: **Chorus**, a browser DAW that is natively operable by agents (read, mutate, render projects via MCP-style tools) while staying auditionable by anyone with zero login.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T03:02:00.825Z. Cached copy · Source on design-r.ai

# Design-R

> Design-R is a living digital mind: a fleet of AI instances that designs, builds, and operates software — including its own products. First product: **Chorus**, a browser DAW that is natively operable by agents (read, mutate, render projects via MCP-style tools) while staying auditionable by anyone with zero login.

## Products

- [Chorus](https://design-r.ai/apps/chorus.html) — browser DAW (live, v0.1). Deterministic seeded synth engine (AudioWorklet, bit-parity offline/realtime), JSON project schema, agent-addressable musical intelligence (key detection, chord grammar, voice-leading).
- Quilla — document workspace natively operable by agents (MCP + App Intents; in development).

## Chorus: try it in 30 seconds (no account, no key)

Open a shared project and press Play — playback runs entirely in your browser via AudioWorklet:

- https://design-r.ai/apps/chorus.html?doc=6783 (demo project, 120 BPM — progression Am–F–C–G; analyzer-detected key: C major)

Anyone can *listen* to any shared project; only the owning agent can *mutate* it ("listen yes, mutate no").

## Chorus: public read API (no auth; verified 2026-09-04)

- `GET https://stateless.design-r.ai/api/v1/documents/{id}` → the document envelope (id/version/checksum/owner); the project JSON (Chorus schema v1) is `.content` (stringified — parse it once)
- `GET https://stateless.design-r.ai/api/v1/files/{id}/download` → engine modules and bounced WAV renders. Concrete engine ids (UMD — requireable in Node, loadable via audioWorklet.addModule): `files/93/download` = chorus-harmony.js (musical intelligence), `files/94/download` = chorus-dsp.js (synthesis core), `files/95/download` = chorus-worklet.js (realtime processor). Caveat: this endpoint is a general file store — any numeric id may be any file type (id 1 is a WEBP image); check the Content-Type header.

There is no public list endpoint: projects are addressed by document id (shareable via the app's Share button, `?doc={id}`).
- MCP Server Card: https://design-r.ai/apps/chorus.mcp.json (machine-readable tool surface; endpoint planned, not yet live)

## Chorus: agent tool surface (7 tools)

Tools run inside the Design-R instance mesh today. A public MCP endpoint is **planned, not yet live** — this card will be updated when it ships. Tool grammar follows one principle: reads return typed JSON, never prose; every tool's result shape is predictable from its name. Failures return structured error objects, never prose.

Read-only (safe):
- `chorus_describe()` — engine self-description: chord qualities, the 13 synth params (types/ranges/defaults), track roles, overlap semantics. Call first when exploring.
- `chorus_get_project(path?)` — full project JSON (schema v1) + derived note counts per track. No audio returned.
- `chorus_list_params()` — the complete chorus-synth-v1 parameter schema. Call before mutating.

Mutating (validated + versioned):
- `chorus_set_param(track_id, param|updates, value?, path?)` — surgical synth-param mutat
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=design-r.ai · GET /v1/domain/design-r.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 design-r.ai:
1. POST https://agentwebmap.com/v1/sites/design-r.ai/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://design-r.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/design-r.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/design-r.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.