# US Brand Signal Brief Composer (`zinin/us-brand-signal-brief-composer`) Actor

Compose one deterministic machine brief from 1-50 normalized US brand signal rows without network access.

- **URL**: https://apify.com/zinin/us-brand-signal-brief-composer.md
- **Developed by:** [Tim Zinin](https://apify.com/zinin) (community)
- **Categories:** MCP servers, Automation, Marketing
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Brand Signal Brief Composer

Turn a buyer-supplied snapshot of US brand signals into one deterministic,
machine-readable brief. The Actor is a bounded reducer: it does not discover,
fetch, verify, or enrich source evidence.

### Use cases

- Normalize rows from a Federal, Action, Offer, or other signal workflow before routing them to an agent.
- Produce stable severity sections for a CRM, alert, or review queue.
- Compare repeated buyer snapshots by `inputSha256`, `briefId`, and `briefSha256`.
- Pass a small inline brief through an MCP-connected workflow without a Dataset input or hidden lookup.

### Input and output

| Field | Input | Output |
| --- | --- | --- |
| `schemaVersion` | Required `"1.0"` | `schemaVersion` |
| `snapshotAt` | Buyer-supplied UTC timestamp with seconds | `snapshotAt` and `generatedAt` exactly match it |
| `title` | Printable ASCII title, 1-120 chars | `title` |
| `rows` | 1-50 unique closed rows | `projections`, four severity `sections`, `counts`, `topEventIds`, `sourceNames` |
| `eventId` | Closed ASCII identifier | Preserved in each projection |
| `severity` | `CRITICAL`, `HIGH`, `MEDIUM`, or `LOW` | Fixed section and ordering |
| `sourceName`, `summary` | Buyer-supplied printable ASCII attribution and text | Preserved as supplied; not independently verified |
| `status` | `active` or `resolved` | Preserved in each projection |
| Digests | Not supplied | `inputSha256`, `briefId`, and `briefSha256` |

One valid request produces one paid default Dataset row. The KVS key `OUTPUT`
contains the terminal receipt. `result-found` is the only custom result event;
the Actor performs one linked push and one result charge. A successful last charge
may return `eventChargeLimitReached: true`; that means the result consumed the
remaining allowance, not that delivery failed.

### Pricing

Pay-per-event pricing uses the pinned Apify SDK 3.7.2 primitive receipt. The
runtime accepts only the `apify-actor-start` and `result-found` receipt keys, checks
integer micro-USD capacity before normalization, and rejects unsafe or unexpected
pricing. The default Dataset item billing event is absent. There is no manual
charge and no retry after uncertain delivery.

| Tier | Start | Result | Discount |
| --- | ---: | ---: | ---: |
| FREE | $0.005000 | $0.010000 | 0% |
| BRONZE | $0.004750 | $0.009500 | 5% |
| SILVER | $0.004500 | $0.009000 | 10% |
| GOLD | $0.004250 | $0.008500 | 15% |
| PLATINUM | $0.004100 | $0.008200 | 18% |
| DIAMOND | $0.004000 | $0.008000 | 20% |

### Freshness and attribution

Freshness is the age of the buyer's supplied snapshot at `snapshotAt`. This Actor
does not read the current clock, browse, call a source, use a proxy, or maintain
replay state. `sourceName` and `summary` are buyer-supplied attribution fields;
they describe the input claim and are not proof that the named source was checked.
Use the upstream collector's retrieval time and evidence policy when freshness or
source verification matters.

### Limits and privacy

The Actor uses 512 MB and a 90-second timeout. Input is inline and limited to 50
rows and 128 KiB serialized JSON. It accepts no Dataset input, URL, network call,
BYOK credential, child Actor, arbitrary state, or external storage destination.

### FAQ

**Does it fetch or validate a brand signal?** No. It only validates the closed
shape and deterministically groups the rows you submit.

**What does `eventChargeLimitReached: true` mean on success?** The final allowed
result was delivered and charged. Read the counter delta and Dataset write together;
the flag alone is not a delivery error.

**Can I retry `delivery_unknown`?** Do not blindly retry. A Dataset write or charge
may have occurred; reconcile the run before submitting a new purchase.

**How fresh is the result?** Exactly as fresh as the supplied `snapshotAt`; the
Actor adds no observation time and makes no live-source claim.

**Can I pass a Dataset ID, API key, or proxy?** No. Those inputs are outside this
contract and are rejected or unavailable by design.

### Related public Store Actors

These five direct links were verified as public, live, non-deprecated zinin Store
Actors in the repository's latest anonymous read-back. They are optional workflow
neighbors, not hidden dependencies or required child calls.

| Actor | Use |
| --- | --- |
| [Intent Signal Aggregator](https://apify.com/zinin/intent-signal-aggregator) | Add hiring and news intent signals before composing a brand snapshot. |
| [Company Profile Lookup](https://apify.com/zinin/company-lookup) | Add company identity and profile context to buyer-supplied rows. |
| [Shopify Store Intelligence](https://apify.com/zinin/shopify-store-intelligence) | Supply commerce and catalog observations for a brand workflow. |
| [Funding Round Tracker](https://apify.com/zinin/funding-round-tracker) | Supply funding events that can become brand signals. |
| [Patent Filing Monitor](https://apify.com/zinin/patent-monitor) | Supply public patent signals for downstream comparison. |

Built by [zinin](https://apify.com/zinin).

# Actor input Schema

## `schemaVersion` (type: `string`):

Required closed V1 contract.

## `snapshotAt` (type: `string`):

Explicit UTC timestamp with a real Gregorian calendar date. It is also emitted as generatedAt; the Actor never reads the current clock.

## `title` (type: `string`):

Printable ASCII title bound into the brief digest.

## `rows` (type: `array`):

Exactly 1-50 closed rows. Input order is ignored; rows are sorted deterministically.

## Actor input object example

```json
{
  "schemaVersion": "1.0",
  "snapshotAt": "2026-08-05T00:00:00Z",
  "title": "Nike US signal brief",
  "rows": [
    {
      "eventId": "nike-launch-001",
      "severity": "HIGH",
      "sourceName": "Brand newsroom",
      "summary": "New running product announced",
      "status": "active"
    },
    {
      "eventId": "nike-price-001",
      "severity": "MEDIUM",
      "sourceName": "Retail monitor",
      "summary": "List price changed for a tracked SKU",
      "status": "resolved"
    },
    {
      "eventId": "nike-review-001",
      "severity": "LOW",
      "sourceName": "Retail monitor",
      "summary": "Review volume moved above the watch threshold",
      "status": "active"
    }
  ]
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

API link to OUTPUT when persisted. A persistent KVS failure is never claimed as written.

## `brief` (type: `string`):

API link to the one paid default Dataset result row.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "schemaVersion": "1.0",
    "snapshotAt": "2026-08-05T00:00:00Z",
    "title": "Nike US signal brief",
    "rows": [
        {
            "eventId": "nike-launch-001",
            "severity": "HIGH",
            "sourceName": "Brand newsroom",
            "summary": "New running product announced",
            "status": "active"
        },
        {
            "eventId": "nike-price-001",
            "severity": "MEDIUM",
            "sourceName": "Retail monitor",
            "summary": "List price changed for a tracked SKU",
            "status": "resolved"
        },
        {
            "eventId": "nike-review-001",
            "severity": "LOW",
            "sourceName": "Retail monitor",
            "summary": "Review volume moved above the watch threshold",
            "status": "active"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zinin/us-brand-signal-brief-composer").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "schemaVersion": "1.0",
    "snapshotAt": "2026-08-05T00:00:00Z",
    "title": "Nike US signal brief",
    "rows": [
        {
            "eventId": "nike-launch-001",
            "severity": "HIGH",
            "sourceName": "Brand newsroom",
            "summary": "New running product announced",
            "status": "active",
        },
        {
            "eventId": "nike-price-001",
            "severity": "MEDIUM",
            "sourceName": "Retail monitor",
            "summary": "List price changed for a tracked SKU",
            "status": "resolved",
        },
        {
            "eventId": "nike-review-001",
            "severity": "LOW",
            "sourceName": "Retail monitor",
            "summary": "Review volume moved above the watch threshold",
            "status": "active",
        },
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("zinin/us-brand-signal-brief-composer").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "schemaVersion": "1.0",
  "snapshotAt": "2026-08-05T00:00:00Z",
  "title": "Nike US signal brief",
  "rows": [
    {
      "eventId": "nike-launch-001",
      "severity": "HIGH",
      "sourceName": "Brand newsroom",
      "summary": "New running product announced",
      "status": "active"
    },
    {
      "eventId": "nike-price-001",
      "severity": "MEDIUM",
      "sourceName": "Retail monitor",
      "summary": "List price changed for a tracked SKU",
      "status": "resolved"
    },
    {
      "eventId": "nike-review-001",
      "severity": "LOW",
      "sourceName": "Retail monitor",
      "summary": "Review volume moved above the watch threshold",
      "status": "active"
    }
  ]
}' |
apify call zinin/us-brand-signal-brief-composer --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=zinin/us-brand-signal-brief-composer",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/iZdvFc2Xj6GEiIBWf/builds/jdrQQy4GiDtIaZNA2/openapi.json