Model API/CLASSIFIERS

Forward Looking

Classify whether text is forward-looking.

POST/api/models/forward-looking

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
textstringrequiredbody

Text to classify. Maximum 50,000 characters.

Example: The company expects to open three factories next year.

Related in NOSIBLE World

World · Map ↗Open this result set on the event map, filtered to the same windowWorld · Trend ↗Plot the same query as a historical event signalWorld · Chaos ↗Watch the unfiltered crawl the ontology is built from

How to use this endpoint

guidance

Use Forward Looking to identify forward-looking language in financial and business text. The endpoint accepts the same text-only request and response shape as the other model endpoints.

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.

schemastring

Stable classifier response schema shared by all four model endpoints.

Example: nosible_model_classification_v1

modelstring

Pinned classifier name, version, and immutable build identifier.

Example: NOSIBLE/forward-looking-v1.2-base@revision:7fa6b656210d6497989ebb145c2943325665c830

textstring

The exact input text classified by the model.

Example: The company expects to open three factories next year.

predictionsobject[]

The classifier output as a one-item prediction list.

Example: [{ "label": "forward", "score": 0.91 }]

predictions[].labelenum

The forward-looking classification label.

Example: forward

predictions[].scorenumber

Model confidence score when supplied by the classifier.

Example: 0.91

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.