Forward Looking

Run the multilingual forward-looking classifier through the NOSIBLE model gateway.

POST/api/models/forward-looking

Related NOSIBLE resources

research & data

Explore the NOSIBLE World interface, inspect the World data dictionary, and browse the classification ontologies used by World.

Authorizations

Bearer

Authorizationstringrequiredheader

Required Bearer API key. Programmatic access to the World API needs a key; browsing nosible.world in a browser does not.

Example: Bearer nos_sk_...

Body

application/json

modelstringbody

Optional upstream model name when the deployment exposes more than one model.

Example: forward-looking

messagesobject[]requiredbody

OpenAI-compatible chat messages. Put the text to classify in the user message.

Example: [{"role":"user","content":"The company expects to open three factories next year."}]

temperaturenumberbody

Optional sampling temperature supported by the upstream deployment.

Example: 0

How to use this endpoint

guidance

Use Forward Looking to identify forward-looking language in financial and business text. The gateway accepts the OpenAI-compatible chat completion body and returns the upstream response envelope unchanged.

Response body

application/json

These are the fields you can build against. Nested names use dot notation; optional sections are called out in their descriptions.

choices[].message.contentstring

The forward-looking classification returned by the upstream model.

Example: forward

modelstring

Model identifier reported by the upstream deployment.

Example: forward-looking

usageobject

Token accounting reported by the upstream deployment when available.

Example: { "prompt_tokens": 18, "completion_tokens": 1, "total_tokens": 19 }

Responses and errors

HTTP

200Request succeeded. The response body is shown in the panel on the right.

400invalid_request — The request is syntactically valid JSON but a value, date, filter, or combination of fields is invalid.

401unauthorized — The required API key or Bearer credential is missing or invalid.

422validation_error — The request shape is understood but one or more values fail validation.

429rate_limited — The request exceeded the account or public-window rate limit. Respect Retry-After when supplied.

502upstream_error — An upstream retrieval service failed while processing the request.

504upstream_timeout — An upstream retrieval service did not respond within the request timeout.