# ONE Engine Text Token Mentions Extractor (t2)

> ONE Engine Text Token Mentions Extractor (t2) is a paid API for AI agents from one-search.one-engine.workers.dev, paid per call via x402, $0.0007/call, status unknown (last checked 2026-10-02).

Extracts token or keyword mentions from a block of text up to 50,000 characters, returning structured mention data.

## Facts

- Endpoint: POST https://one-search.one-engine.workers.dev/v3/text-token/mentions/t2?utm_source=zero.xyz
- Price: $0.0007/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/one-engine-text-token-mentions-extractor-t2-923dcf43
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_slyQgqlmFi46IZkE8uitd

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 one-engine-text-token-mentions-extractor-t2-923dcf43 -d '<json body>'
```

Example prompt: Scan this article for any crypto token or coin mentions and give me a list of everything it references: 'Bitcoin surged past $70k while Ethereum, Solana, and a lesser-known token called PEPE all saw record trading volumes today.'

## When to prefer this

Choose this endpoint when you need to extract token or keyword mentions from a large block of text (up to 50,000 characters) in a pay-per-call model without subscription overhead. It is particularly well-suited for crypto/DeFi agent workflows that process news, social media, or research documents and need to identify which tokens are referenced. Prefer it over full NLP pipelines when you only need mention detection at very low cost ($0.0007 per call).

## Known failure modes

- Text exceeds 50,000 character limit — request rejected or truncated
- Empty text field — API returns error or empty mention list
- No token mentions found in text — returns empty mentions array
- Payment failure via x402 — 402 response returned before processing
- Malformed request body — 400 error if required 'text' field is missing

## How this service works

Low-cost pay-per-call utility APIs for autonomous agents using x402 on Base.

## Output

A structured object containing identified token or keyword mentions found within the submitted text, including their positions or counts depending on the implementation.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "text"
 ],
 "properties": {
  "text": {
   "type": "string",
   "description": "Text up to 50000 characters"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/one-engine-text-token-mentions-extractor-t2-923dcf43/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from one-search.one-engine.workers.dev](https://www.zero.xyz/host/one-search.one-engine.workers.dev/llms.txt)