Model API/TAGGERS

Ticker Tagger

Map text to listed-company tickers with CompanyV5 metadata and supporting evidence.

POST/api/models/tickers

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 tag. Maximum 50,000 characters. Uses the release's knowledge snapshot; this text-only endpoint does not apply a historical document date.

Example: NVIDIA Corporation reported strong earnings from GPU sales.

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 Ticker Tagger to map news text to listed companies with the same text-only request and model response envelope as the other model endpoints. Labels are ticker symbols; predictions retain CompanyV5 metadata and evidence. v2.0-preview pins the verified engine revision and shipped bundle. The default knowledge snapshot is used; historical listing membership is not inferred. An empty predictions array is a successful no-match result.

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 response schema shared with the other text model endpoints.

Example: nosible_model_classification_v1

modelstring

Pinned v2.0-preview ticker engine revision. The release uses bundle 12281f4cd630b7d2.

Example: NOSIBLE/ticker-tagger-v2.0-preview@revision:7c07d504ecbb5a0a40d17091b29f3d7a74e389ad

textstring

The exact input text.

Example: NVIDIA Corporation reported strong earnings from GPU sales.

predictionsobject[]

Ranked ticker matches. Empty when no listed company is identified.

Example: [{ label, score, companyv5_id, name, why }]

predictions[].labelstring

Ticker symbol with the engine's exchange suffix. Preserve it exactly.

Example: NVDA.US

predictions[].scorenumber

Ticker relevance score from 0 to 1; not a calibrated probability.

Example: 0.97

predictions[].companyv5_idstring | null

Stable CompanyV5 company identifier, when available.

Example: c5-1b5479ea345b

predictions[].namestring | null

Company display name.

Example: NVIDIA Corporation

predictions[].websitestring | null

Company website.

Example: https://nvidia.com

predictions[].wiki_qidstring | null

Wikidata identifier.

Example: Q182477

predictions[].isinstring | null

International Securities Identification Number.

Example: US67066G1040

predictions[].leistring | null

Legal Entity Identifier, when available.

Example: null

predictions[].figistring | null

Financial Instrument Global Identifier, when available.

Example: null

predictions[].sectorstring | null

Company sector.

Example: Information Technology

predictions[].industrystring | null

Company industry.

Example: Semiconductors & Semiconductor Equipment

predictions[].country_isostring | null

Company country code, when available.

Example: US

predictions[].exchangestring | null

Listing exchange.

Example: NASDAQ

predictions[].micstring | null

Market Identifier Code, when available.

Example: XNAS

predictions[].whyobject[]

Supporting text mentions and graph connections, strongest first.

Example: [{ entity, score, chain }]

predictions[].why[].entitystring

Matched entity surface or graph entity name.

Example: NVIDIA

predictions[].why[].scorenumber

Evidence relevance score.

Example: 0.97

predictions[].why[].chainobject[]

Relationship steps connecting the mentioned entity to the company. Empty for a direct match.

Example: [{ subject, predicate, object, known_as_of }]

predictions[].why[].chain[].known_as_ofdate | null

Earliest known relationship date when available. The shipped bundle lacks per-step dates; a link-level date may be used.

Example: null

Responses and errors

HTTP
200Request succeeded. The response body is shown in the panel on the right.
400invalid_json — The request body is not valid JSON.
401api_key_required / invalid_api_key — A valid NOSIBLE bearer API key is required.
422validation_error — Supply only text: a nonempty string of at most 50,000 characters.
429rate_limited / model_rate_limited — Caller or upstream rate limit exceeded. Respect Retry-After when present.
503model_not_configured — The ticker service is not configured for this deployment.
503api_key_auth_not_configured / api_key_auth_unavailable / api_key_metering_unavailable — Authentication or quota metering is temporarily unavailable. Retry after the indicated delay.
502model_invalid_response — The ticker service returned a malformed response. This is distinct from a successful empty predictions array.
502model_upstream_error / model_upstream_unreachable — The ticker service rejected the request or could not be reached.
504model_upstream_timeout — The ticker service did not respond before the request deadline.