getnoise.com valid

Noise

Noise is a creator-economy platform connecting brands with content creators for UGC (user-generated content) campaigns. Brands launch campaigns and playbooks; creators produce, post, and monetize content across social platforms.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T22:20:23.742Z. Cached copy · Source on getnoise.com

# Noise

> Noise is a creator-economy platform connecting brands with content creators for UGC (user-generated content) campaigns. Brands launch campaigns and playbooks; creators produce, post, and monetize content across social platforms.

## Brand Reporting API

The Reporting API gives brands programmatic, read-only access to their daily campaign performance — spend, views, unique creators, posts, CPM, and estimated_installs (a day-grain third-party app-install estimate, brands with linked apps only) — grouped by day, campaign, and playbook. Authenticated per organization with `x-noise-org` + `x-noise-token` headers.

- [OpenAPI spec](https://reporting.getnoise.com/openapi.yaml): Full machine-readable contract. Hand this URL to an AI assistant and it can write correct requests and generate a client.
- [Endpoints]: `GET /v1/reports/daily` (metrics + period totals), `GET /v1/campaigns`, `GET /v1/playbooks` — base URL `https://reporting.getnoise.com`.

## MCP server (AI assistants)

AI assistants can query AND manage a brand's campaigns, playbooks, and paid ads directly as MCP tools, and can explain how Noise shows up in the brand's install numbers.

- [MCP endpoint](https://reporting.getnoise.com/mcp): Streamable HTTP, OAuth 2.1 (add it as a connector in Claude or any MCP client; sign in when prompted).
- Read tools: `get_daily_report` (performance), `list_posts` (per-post drilldown), `get_campaign_details` (current budget/target/CPM/config), `get_playbook_details` (playbook content), `get_audit_log` (change history), `list_campaigns`, `list_playbooks`, `list_ads` (paid-ad placements with status, fees, spend, insights), `list_ad_destinations` (connected ad accounts' campaigns and delivering ad sets), `explain_noise_effectiveness` (how Noise shows up in installs, App Store search, Apple Search Ads, and countries, plus the brand's own signals over a window).
- Write tools: `set_campaign_status`, `update_campaign_budget`, `set_daily_target`, `update_campaign_rates`, `set_playbook_status`, `create_playbook`, `update_playbook`, `save_playbook` (full content: slides, captions, hashtags, descriptions), `generate_slide_image` (AI-generate / URL / existing), `create_ad` (run approved posts as Meta / TikTok ads: renditions, disclaimer, optional destination ad set), `publish_ad` (build the ad for a pushed creative, live unless created paused). Every write PREVIEWS by default (shows current → proposed + consequences); pass `confirm: true` to apply. Writes are guardrailed (CPM/budget caps, per-day AI image cap, per-day ad creation cap) and audited.
- Before judging whether Noise is working, assistants should call `explain_noise_effectiveness`; the server instructions say so on every session.
- Linking: after the first sign-in the assistant reports a connection code (`org_...`); a brand member pastes it in the Noise portal (Resources → Reporting API → Connect an AI assistant) to scope tools to their organization. Links are many-to-many: teammates each connect
…

Related sites

Find similar publishers by meaning →

Other listed sites in Community. See the whole category →

Machine-readable: GET /v1/resolve?q=getnoise.com · GET /v1/domain/getnoise.com · 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 getnoise.com:
1. POST https://agentwebmap.com/v1/sites/getnoise.com/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://getnoise.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/getnoise.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/getnoise.com).
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.