noisedeck.app valid

Foundry -- Agent API

Foundry is a browser-based effects editor built on the Noisemaker engine. In

For agents: Noisedeck suite of browser visual tools (Foundry, Polymorphic, Visualize, Noodles) with an agent API for controlling shaders and effects.

shader video synthesizerglsl shaderslive codingagent apinoisemaker

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T20:22:35.275Z. Cached copy · Source on noisedeck.app

# Foundry -- Agent API

> Foundry is a browser-based effects editor built on the Noisemaker engine. In
> Foundry a person writes two things: a program (Polymorphic DSL text, kept as
> the workspace file dsl.txt) and, when they want one, a custom effect of their
> own (definition.json, GLSL shaders in glsl/, WGSL shaders in wgsl/, and
> help.md) that the program calls from the `user` namespace. An agent can join
> the person's own open Foundry over Seance, the Noise Factor collaboration
> service, or drive Foundry in a browser it controls, and read, write and run
> both. This file is the contract for software agents that control Foundry.

The full contract adds a reference for every command and its arguments:
https://foundry.noisedeck.app/llms-full.txt

The DSL and the effect format are specified by the Noisemaker contract:
https://noisemaker.app/llms-full.txt. The conventions that matter most when
you write Foundry code are collected below, each with the Noisemaker source
that defines it. Foundry does not enforce them: a program or a shader that
breaks one still compiles and runs if the engine accepts it. Follow them
anyway; other apps and other people's programs rely on them.

For the roles and control paths of the other Noise Factor products,
including Timeline's project-folder CLI and Layers' separate document, start
from the platform guide at https://noisefactor.io/llms.txt.

## Connect to the person's Foundry

Use this route when you can run shell commands. It works with the Foundry the
person already has open: their program, their custom effect, their canvas.

1. Ask the person to open https://foundry.noisedeck.app, choose **connect
   agent...** at the end of the effect menu, click **Go Online**, then **Copy
   Prompt**, and paste the prompt to you. The prompt names this file and the
   session link. (Without that dialog: **live collab...**, **Take Online**, then
   send the link or the six-character code.)
2. Get the agent tool. It needs Node 22.4 or later and nothing else:
   `curl -fsSLO https://noisedeck.app/agent/seance-agent.mjs`
3. Join: `node seance-agent.mjs join <link-or-code>`. It prints the session
   name (`foundry`), the open app tabs and the session documents. A background
   process keeps the session joined between commands.

| Command | What it does |
|---|---|
| `node seance-agent.mjs commands` | Lists Foundry's commands and their arguments. |
| `node seance-agent.mjs program [--json]` | Prints the session's program text (`--json` adds its `rev`). |
| `node seance-agent.mjs validate <file>` | Checks a program (`-` reads standard input). |
| `node seance-agent.mjs set <file>` | Runs a program in the person's tab (setProgram). |
| `node seance-agent.mjs look [--size N] [--format png\|jpg] [--out FILE]` | Saves an image of the person's canvas. Its path is `result.envelope.result.image.path`; open the file with your image tool. `--size` is 768 unless given, at most 1024. |
| `node seance-agent.mjs call <command> [JSON]` | Run
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=noisedeck.app · GET /v1/domain/noisedeck.app · 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 noisedeck.app:
1. POST https://agentwebmap.com/v1/sites/noisedeck.app/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://noisedeck.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/noisedeck.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/noisedeck.app).
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.