Agentic Portal

Named Entity Recognition

documents
Serving

Rule-based named-entity recognition for English text, from patterns and word lists rather than a trained model: persons, organisations, places, dates, money, percentages, emails, URLs and products, with character offsets. Best on clean, well-capitalised text; it misses names off its lists. POST /v1/ner with {text}. Pay per request in USDC; no account, no API key.

Endpoint
POST https://agent.pocket.network/v1/named-entity-recognition/v1/ner
Price per call
$0.005 USD
Networks payable on
Base (eip155:8453), Tempo (eip155:4217)
Protocol
rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

A real, working call — the request the service card verifies against.

curl -X POST https://agent.pocket.network/v1/named-entity-recognition/v1/ner \
  -H 'content-type: application/json' \
  -d '{"text":"Ada Lovelace met Alan Turing in London on 12 May 1843 for 500 pounds."}'
Example response

The response this call returned, captured 2026-10-05 11:03:58 UTC.

{
  "portal": {
    "provenance": "third-party-supplier",
    "serviceId": "named-entity-recognition",
    "schemaCheck": "unchecked"
  },
  "data": {
    "entities": [
      {
        "text": "Ada Lovelace",
        "label": "PERSON",
        "start": 0,
        "end": 12
      },
      {
        "text": "Alan Turing",
        "label": "PERSON",
        "start": 17,
        "end": 28
      },
      {
        "text": "London",
        "label": "LOC",
        "start": 32,
        "end": 38
      }
    ],
    "count": 5,
    "model": "rules-ner-v3",
    "deterministic": true,
    "service": "named-entity-recognition"
  }
}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Named Entity Recognition accepts, and whether each reads or writes.
MethodEffect
GET /v1/healthread
GET /v1/versionread
POST /v1/nerread

Schemas

Published by the service itself. The example above is generated from these.

Request schema
{
  "type": "object",
  "description": "The body of POST /v1/ner.",
  "properties": {
    "text": {
      "type": "string",
      "maxLength": 100000,
      "description": "English text to tag."
    }
  },
  "required": [
    "text"
  ]
}
Response schema
{
  "type": "object",
  "description": "For POST /v1/ner, a JSON object with entities (text, label, start, end), count, model and deterministic. Labels are PERSON, ORG, LOC, DATE, MONEY, PERCENT, EMAIL, URL and PRODUCT. A bad request answers 400 with an `error` string. Properties are pinned from live paid responses; nothing is required, because every route's 2xx response is validated against this one schema.",
  "properties": {
    "entities": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "text": {
            "type": "string"
          },
          "label": {
            "type": "string"
          },
          "start": {
            "type": "number"
          },
          "end": {
            "type": "number"
          }
        }
      }
    },
    "count": {
      "type": "number"
    },
    "model": {
      "type": "string"
    },
    "deterministic": {
      "type": "boolean"
    },
    "service": {
      "type": "string"
    }
  }
}