Provided by PredictLeads
List the Classified News Events of One Company by Domain (PredictLeads)
List the company events PredictLeads classified out of news coverage for one company you name: the event category — expansion, partnership, launch, award, recognition, closure and more — with the headline, the article URL and the found date. Supply the domain and a row limit. It answers for the single company you name, for any of the companies PredictLeads tracks. Flat price with no plan.
Contract snapshot: 2026-09-17. Inspect in Glasser for current terms.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"domain"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1
},
"domain": {
"type": "string",
"pattern": "^(?!-)(?:[a-z0-9-]+\\.)+[a-z]{2,}$",
"maxLength": 253,
"minLength": 3
}
},
"additionalProperties": false
}{
"limit": 10,
"domain": "stripe.com"
}This Endpoint publishes no output schema. You get the Provider's own response body, unchanged — we do not warrant a shape we cannot guarantee.
How to run it
Two fields identify it: the Provider and the endpoint key. The key looks like a path because it usually mirrors the Provider's own, but it is an opaque identifier — not a URL you can open. The same provider:endpoint pair is what your Policy lists.
Once: paste this into your agent's chat. The Skill installs the CLI and logs in by itself. For an agent that cannot use a shell, connect it over MCP instead.
set up https://glasser.ai/SKILL.mdThen ask for this Endpoint:
Run the PredictLeads Endpoint /companies/{company_id_or_domain}/news_events on Glasser with input {"limit":10,"domain":"stripe.com"}glasser run -p predictleads -e '/companies/{company_id_or_domain}/news_events' -i '{"limit":10,"domain":"stripe.com"}' --endpoint-version 2Pinned to version 2, the one this page shows: if a newer version is published first, the Run is refused instead of charged under new terms. Install and log in first on Get Started.
Once per Run:
IDEMPOTENCY_KEY=$(uuidgen)Run it, and copy this same block to send it again:
curl -X POST https://api.glasser.ai/v1/runs \
-H "Authorization: Bearer gl_..." \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
-H "Content-Type: application/json" \
-d '{"provider":"predictleads","endpoint":"/companies/{company_id_or_domain}/news_events","input":{"limit":10,"domain":"stripe.com"},"endpoint_version":2}'Reuse the same Idempotency-Key to send it again: the second send is a read of the first Run. A new key is a new Run and a new Charge. Pinned to version 2 for the same reason as the CLI.
What each outcome charges
| No result | The Provider answered: nothing matched. | $0.04 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The deadline won. | $0.00 |
| Internal failure | Our defect. | $0.00 |