Test endpoints and estimate cost
Run Veille requests from the playground and forecast your credit spend.
The dashboard gives you two ways to try things before you commit: the playground on each Library endpoint sends real requests with your key attached, and the Simulator forecasts what a workload would cost without calling anything.
Response
{
"results": [
{
"title": "…",
"url": "…"
}
]
}Run a request in the playground
Open an endpoint
Go to Library and open the endpoint you want to try.
Fill in the parameters
Required fields are marked. Optional ones fall back to their documented defaults.
Run it and read the response
You get the status code and the response body on the Response tab. Language tabs inside the Playground (curl, Python, Node…) copy the same call as a snippet.
Playground calls are real API calls: they consume credits and appear in your logs exactly like production traffic.
Estimate a workload with the Simulator
Settings → Simulator answers the other question: what would this cost? Add the endpoints you plan to call, set a number of requests for each, and pick a plan. You get the total requests, the credits needed, and any excess beyond the plan — then you can email the estimate to yourself or to whoever signs off on it.
Scenario
3 endpointsCost summary
55,000
60,000
0
The Simulator sends no traffic and consumes no credits, so it is the safe way to size a plan before a launch.