Provided by PredictLeads
Get One Classified Company Event by Identifier (PredictLeads)
Get one classified company event by the PredictLeads identifier you already hold: event category, headline, article URL, found date and the company it belongs to. Supply the news event id — it takes an id and nothing else, so it neither searches events nor lists the events of companies. An unknown id returns no result. Flat price with no plan.
How to run it
Step 1Set up
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.md
Show me how to use the PredictLeads endpoint /news_events/{id} on Glasser.glasser run -p predictleads -e '/news_events/{id}' -i '{"id":"00000000-0000-4000-8000-000000000000"}' --endpoint-version 2Uses endpoint version 2. Inspect the current price before running. 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":"/news_events/{id}","input":{"id":"00000000-0000-4000-8000-000000000000"},"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. Uses endpoint version 2; inspect the current price before running.
Step 2Try a specific example task
When you need to plan which events to research, you might look for entries relevant to your topic and consider why each one fits.
Copy this prompt into your agent to find relevant events in the returned data.
Use predictleads:/news_events/{id} on Glasser.
Find events relevant to my topic in the returned data and explain why each matches.Endpoint structure
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$"
}
},
"additionalProperties": false
}{
"id": "00000000-0000-4000-8000-000000000000"
}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 pricing works
| Data returned or no match | The same price with or without matching data. | $0.04 |
|---|---|---|
| Provider error | The Provider failed to answer. | $0.00 |
| Timed out | The Run exceeded its time limit. | $0.00 |
| Internal failure | An internal error prevented completion. | $0.00 |