# NexusAPI Named Entity Recognition (NER)

> NexusAPI Named Entity Recognition (NER) is a paid API for AI agents from nexus-api-virid.vercel.app, paid per call via x402, $0.110144/call, status unknown (last checked 2026-09-14).

Performs Named Entity Recognition (NER) on a text query, identifying and classifying named entities such as people, organizations, locations, and dates.

## Facts

- Endpoint: POST https://nexus-api-virid.vercel.app/api/ai/ner
- Price: $0.110144/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/nexusapi-named-entity-recognition-ner-248e6004
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iE2WW-ItGhsjkIpzOXBTu

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability nexusapi-named-entity-recognition-ner-248e6004 -d '<json body>'
```

Example prompt: Extract all named entities from this text and tell me what type each one is: 'Apple CEO Tim Cook met with Elon Musk in San Francisco on Tuesday to discuss AI regulation.'

## When to prefer this

Choose this endpoint when you need a pay-per-call, no-API-key NER service that accepts raw text and returns structured entity labels. Ideal for agents that need lightweight entity extraction without managing credentials or subscriptions. Use it when you need to identify people, organizations, locations, or dates in arbitrary text as part of a larger workflow.

## Known failure modes

- Empty or missing query field returns an error or empty entity list
- Very long text inputs may be truncated or cause timeouts
- Ambiguous entity types may be misclassified (e.g. a person name matching a place name)
- Non-English text may return poor or no results if the model is English-only
- Payment failure via x402 protocol results in 402 response and no entity data returned

## How this service works

Crypto, AI, Social Media, Finance, Weather, Tools &amp; more. Pay per call in USDC on Base. No API keys.

## Output

A structured response identifying spans of text that are named entities, along with their classified types (e.g. PERSON, ORG, LOCATION, DATE, etc.) extracted from the input text.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "query": {
   "type": "string",
   "description": "Search query or input parameter"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "API response data"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/nexusapi-named-entity-recognition-ner-248e6004/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from nexus-api-virid.vercel.app](https://www.zero.xyz/host/nexus-api-virid.vercel.app/llms.txt)