US Brand Signal Batch Splitter
Pricing
Pay per event
US Brand Signal Batch Splitter
Split already-normalized US brand signal rows into stable groups by one submitted grouping mode without network access or inference.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Tim Zinin
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
20 hours ago
Last modified
Categories
Share
Split a submitted batch of normalized US brand signal rows into stable machine-readable groups. Choose brand, eventType, severity, or analysisStatus; receive exact IDs, counts, and SHA-256 digests. No browsing, enrichment, inference, or child Actor calls.
Input and output
Submit 1-100 unique closed rows with signalId, brandName, eventType, severity, and analysisStatus, plus exactly one groupingMode. Rows are already normalized buyer input. The Actor sorts rows, group keys, and IDs with stable ASCII ordering. The report contains one group per distinct selected value and no hidden claims about the underlying signals.
Pricing
Pay-per-event pricing charges one apify-actor-start on start and at most one result-found after one confirmed Dataset row. Invalid input, unsafe pricing, and buyer-cap failures produce no result event. Six PPE tiers are configured:
| Tier | Discount | Start | Result |
|---|---|---|---|
| FREE | 0% | $0.005000 | $0.010000 |
| BRONZE | 5% | $0.004750 | $0.009500 |
| SILVER | 10% | $0.004500 | $0.009000 |
| GOLD | 15% | $0.004250 | $0.008500 |
| PLATINUM | 18% | $0.004100 | $0.008200 |
| DIAMOND | 20% | $0.004000 | $0.008000 |
Freshness
This is a closed inline transformation. It has no source freshness, scheduled refresh, network request, runtime clock, Dataset input, or persistent state. Re-run it when the buyer has a new normalized batch.
Limits and privacy
The public input maximum is 100 rows and 64 KiB serialized input. Output is compact and runtime-capped below 48 KiB; every terminal receipt is strictly below 64 KiB. Runtime defaults are 512 MB and 90 seconds with LIMITED_PERMISSIONS and Standby disabled. No URL, proxy, BYOK key, secret, LLM, child Actor, queue, cron, or remote write is used.
FAQ
Does this verify a signal or brand identity?
No. It groups only the exact submitted values and attributes no truth to them.
Can I send a Dataset ID or URL?
No. The contract is intentionally inline and closed.
Does input order affect the result?
No. Canonical row, group, ID, and digest ordering is deterministic.
Why are counts and digests trustworthy?
The runtime recomputes every derived field from the canonical request. Standalone schemas reject unknown fields, invalid ranges, duplicate group IDs, and malformed digest strings; adversarial tests cover forged counts, groups, and digests.
Related public Actors
The following five public Store links are the verified HTTP-200 related-Actor links retained for this local build:
| Actor | Use it for |
|---|---|
| US Brand Action Queue | Turn submitted signal rows into an ordered action queue. |
| US Brand Offer Evidence Normalizer | Normalize offer observations before downstream grouping. |
| US Brand Federal Award Snapshot | Collect federal-award evidence upstream of a signal workflow. |
| Competitor Change Rollup | Consolidate competitor changes before splitting work. |
| Trademark Multiregistry | Add trademark evidence to a buyer-owned signal batch. |
This local build does not contact those links or any remote service.
![Google News Scraper [only $0.7/1K] avatar](https://images.apifyusercontent.com/Twu1TG04ITI_hwjby-GKjS3ch9YgJ3AaSAGKR67WRFo/rs:fill:76:76/cb:1/aHR0cHM6Ly9hcGlmeS1pbWFnZS11cGxvYWRzLXByb2QuczMudXMtZWFzdC0xLmFtYXpvbmF3cy5jb20vUmVkNnNHSEFOa0x6b3NzdkUtYWN0b3ItemVOd3Z2dk5VNnpWMWFra1MtMTBnTFVnUzdoSS1nb29nbGVfbmV3c19zY3JhcGVyX2Zhc3QucG5n.webp){kind=avatar}
