noisemaker.app valid

Noisemaker

Noisemaker is an open source shader framework for humans and coding agents. Use it to build expressive, extensible visual tools in the browser. It supports:

For agents: Noisemaker is an open source shader framework for humans and coding agents, with a DSL, effect specs, pipeline docs and a CanvasRenderer for browser visual tool

shader frameworkwebglglsl shadersvisual effectsopen source

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T15:18:18.972Z. Cached copy · Source on noisemaker.app

# Noisemaker

Noisemaker is an open source shader framework for humans and coding agents.
Use it to build expressive, extensible visual tools in the browser.
It supports:

- WebGL2 and WebGPU.
- The high-level Polymorphic DSL.
- Declarative effect definitions.
- Portable effect packages.
- External media/audio/MIDI inputs.
- Shader bundles distributed through a CDN.

Use this file as the short public map. For a fuller agent-oriented overview, read `/llms-full.txt`.

## Primary Links

- [Homepage](https://noisemaker.app/): Product overview and demos.
- [Shader demo](https://noisemaker.app/demo/shaders/): Interactive effect browser and DSL editor.
- [Docs](https://docs.noisemaker.app/): In-house documentation root.
- [Source](https://github.com/noisefactorllc/noisemaker): Noisemaker repository.

## Core Documentation

- [Shader integration](https://docs.noisemaker.app/shaders/integration/): Embedding `CanvasRenderer` from the CDN or local bundles.
- [Shader specs](https://docs.noisemaker.app/shaders/specs/): Effect format, Polymorphic DSL, pipeline, compiler, and effect reference.
- [Pipeline spec](https://docs.noisemaker.app/shaders/pipeline/): DSL to render graph, resource allocation, and GPU dispatch.
- [Language spec](https://docs.noisemaker.app/shaders/language/): Polymorphic DSL syntax and semantics.
- [Effect definition spec](https://docs.noisemaker.app/shaders/effects/): Effect definitions, namespaces, tags, globals, textures, and passes.
- [Release process](https://docs.noisemaker.app/releases/): CDN pinning, immutable patch releases, and release channels.

## Agent Tooling

For the roles and control paths of the Noise Factor apps, including
Timeline, start from the [platform guide](https://noisefactor.io/llms.txt).

Start with the "Portable effect authoring" section of [llms-full.txt](https://noisemaker.app/llms-full.txt) for host-independent discovery, typed bindings, paired shaders, looping, rendered checks and export round trips.

The [effect manifest](https://shaders.noisedeck.app/1/effects/manifest.json) lists every effect as `namespace/name`. Each effect's `help.md` gives its parameters with their types, defaults and ranges, as plain text: `https://raw.githubusercontent.com/noisefactorllc/noisemaker/v<version>/shaders/effects/<namespace>/<name>/help.md`, where `<version>` is the `version` in https://shaders.noisedeck.app/1/deployment-meta.json, the engine that the apps run.

For app control, read [Foundry](https://foundry.noisedeck.app/llms-full.txt) or [Shade](https://shade.noisedeck.app/llms-full.txt). Their guides add shader-craft and reference-video workflows.

- [shade-mcp](https://github.com/noisefactorllc/shade-mcp): MCP server for effect search, source search, compile, render, metrics, parity, and structure checks.
- [portable](https://github.com/noisefactorllc/portable): Portable effect package format with definition JSON, help docs, GLSL, WGSL, and viewer.

## Demos

- [Noisedeck.app](https://noisedeck.app): A comprehensiv
…

Related sites

Find similar publishers by meaning →

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=noisemaker.app · GET /v1/domain/noisemaker.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 noisemaker.app:
1. POST https://agentwebmap.com/v1/sites/noisemaker.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://noisemaker.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/noisemaker.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/noisemaker.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.