Address endpoints by model name
Endpoints are model names; their public data is one REST call away.
Name it the endpoint prefix/TICKER
- ScreenModel field
- Actionthe endpoint prefix/TICKER
- ResultLive version
Copy the model namepad/JPX is ready for any client
Example dataThe prefix is case-insensitive and the ticker is uppercased. An unknown or retired endpoint returns 404 model_not_found; a paused one returns 503 endpoint_paused.
List what is live
- ScreenGET /v1/models
- ActionEndpoints first
- ResultThen raw models
Open Explore and tap $JPXIts market and service open
Example dataNo key needed.
Read one endpoint
- ScreenGET /api/v1/endpoints/{ticker}
- ActionVersion, price, totals
- ResultPublic fields
Tap ServiceModel, price, files and calls
Example dataReturns the live version (route, hashes, files, params, markup), any pending version, the locked split, today and lifetime totals, and venue links.
How an endpoint call is built
- ScreenEndpoint prompt
- ActionFiles
- ResultYour messages
Tap ServiceModel, price, files and calls
Example dataThe endpoint system prompt goes first, then its files as a second system block (<file name="glossary.csv">…</file>), then your system prompt and messages. You may lower max_tokens and set temperature within 0 to 2.