Looks up one person by hem or email and returns their high and medium intent topics that carry a 14-day trend. Low topics never carry a trend, so they are never returned. If both hem and email are sent and the hem is valid, the hem is used. An email is hashed to a hem, so matched_on says which identifier matched.

matched means at least one trend topic came back after topic_ids and min_score were applied. A person who has opted out looks exactly like a person we do not hold, and so does a malformed identifier: matched: false, topics: [].

Authentication. API keys only. A dashboard session or any other caller gets 403. Name the project with the X-Project-Id header or a ?project_id= query parameter.

Billing. One Predictive Signals unit when at least one topic is returned, counted after filtering. A person with no trend topic, or whose trend topics were all removed by topic_ids or min_score, costs nothing. An identical repeat on the same data day (as_of) is billed once. Set dry_run: true to get records_to_charge back with no topics and no charge.

Test API keys get a fixed sample person (a high topic with a rising trend and a medium topic that is new) through the same filters. Responses carry X-Delivr-Mode: test and are never billed. A hem of 64 zeros returns matched: false.