US Brand Signal Brief Composer
Pricing
Pay per event
US Brand Signal Brief Composer
Compose one deterministic machine brief from 1-50 normalized US brand signal rows without network access.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Tim Zinin
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
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, andbriefSha256. - 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 | Add hiring and news intent signals before composing a brand snapshot. |
| Company Profile Lookup | Add company identity and profile context to buyer-supplied rows. |
| Shopify Store Intelligence | Supply commerce and catalog observations for a brand workflow. |
| Funding Round Tracker | Supply funding events that can become brand signals. |
| Patent Filing Monitor | Supply public patent signals for downstream comparison. |
Built by zinin.
